openScale | source weight and body metrics tracker | iOS library

The importance of features for pertinent positive is computed as the change needed to get to the Pertinent positive feature value from its median value. E.g., if the feature F1 has value 20 in its pertinent positive and the median value of f1 is 2, then the importance depends on the distance between 20 and 2 (i.e., 18). We also factor in the standard deviation to normalise the distance across different features. Hence it could happen that a feature whose value has not changed in the PP has high weight (if that value is away from its median). So the weight is a measure of how far the PP feature value is from its median.

Having said that, another way of looking at feature importance is to look at those features which have changed.

Thanks, Manish

The Particle Community had the answer for the Particle Photon and pointed me to the reference documentation. This code works:

You can use freely the internal database for monitoring of any model type with the limitations listed at: https://cloud.ibm.com/docs/services/ai-openscale?topic=ai-openscale-connect-db#cdb-lite.

In summary:

• The free database is hosted, and is not directly accessible to you.
• The database capacity is limited to 1GB.
• IBM® Watson OpenScale will have full access to your database, and thus will have full access to your data.
• The database is not GDPR-compliant. If your model processes personally-identifiable information (PII), you cannot use the free database.

I know subscribe and onComplete but it is also possible to do without these methods?

Given:

I thought doOnNext is only called once on successful notification setup!?

In your case this .doOnNext() will get called for each successful notification setup after a connection is established. If the connection will be broken by any cause the .retry() operator will resubscribe to connectionObservable which may start a new connection that would trigger a new notification setup.

Conclusion: your .doOnNext() may be called up to BT_RETRY_TIMES_ON_ERROR times for each .subscribe()

How can I repeatedly setup a notification on the same characteristic?

A notification is active as long as .setupNotification() is subscribed and there is no need to setup it again. However if one would try to subscribe again to .setupNotification() for the same characteristic both subscribers will share the same notification. In your example the notification will be active until the compositeDisposable will be disposed or the connection will break (in which case a new connection will be established up to BT_RETRY_TIMES_ON_ERROR times for each subscribe as mentioned above).

Is there a better way to create a state machine with RxAndroidBle/RxJava2? (I need to call various Bluetooth operation sequential)

RxJava2 allows for building state transformations and schedule subscribing to particular Observable in many different manners (sequential as well) e.g.

It seems that moving the test case from .../com.health.openscale/DatabaseTest.java to .../com/health/openscale/DatabaseTest.java fixed the problem.