You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently evaluating concepts to represent measured sensor data and I came across JSR-385 which seems to address most topics. Great stuff!
As mentioned in the title, I am however struggling to find how (virtual) boolean data can/should be represented (#115 (comment)). Virtual values in general seem to be undefined, but I would have gone with annotated units where possible (i.e. phone battery level = Units.PERCENT annotated with battery_level (or the like)).
Played around with the DimensionLessAbstractUnit.ONE and transforming 0 to false and 1 to true, but I wasn't able to get a working POC.
Possible virtual boolean sensors:
Presence
Motion
Dark
Daylight
...
How would one represent such values?
The text was updated successfully, but these errors were encountered:
Hi all
I am currently evaluating concepts to represent measured sensor data and I came across JSR-385 which seems to address most topics. Great stuff!
As mentioned in the title, I am however struggling to find how (virtual) boolean data can/should be represented (#115 (comment)). Virtual values in general seem to be undefined, but I would have gone with annotated units where possible (i.e. phone battery level =
Units.PERCENTannotated withbattery_level(or the like)).Played around with the
DimensionLessAbstractUnit.ONEand transforming0tofalseand1totrue, but I wasn't able to get a working POC.Possible virtual boolean sensors:
How would one represent such values?
The text was updated successfully, but these errors were encountered: