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
The recently created QuantityOrSensor Marshmallow class (#897) allows defining a field with a Sensor or with a quantity. This enables the use of Sensors (time-varying data) or fixed values (quantities) for the inputs of the Scheduler.
If the value is not provided, we should (and we usually do) default to a fallback attribute that lives in the sensor or asset of the target device. This fallback mechanism should be built-in in the flex-model deserialization step. This class already has the sensor as its input and can be used in the load step.
The recently created
QuantityOrSensor
Marshmallow class (#897) allows defining a field with a Sensor or with a quantity. This enables the use of Sensors (time-varying data) or fixed values (quantities) for the inputs of the Scheduler.If the value is not provided, we should (and we usually do) default to a fallback attribute that lives in the sensor or asset of the target device. This fallback mechanism should be built-in in the flex-model deserialization step. This class already has the sensor as its input and can be used in the load step.
Credits: #909 (comment)
The text was updated successfully, but these errors were encountered: