FlexMeasures / flexmeasures / 31130498864

84%

main: 84%

Build Type

push

github

Committed by BelhsanHmida

Commit Message

feat: support a `default` fallback on sensor references

A sensor reference on any flex-model or flex-context field may now carry a
`default` quantity, e.g. {"sensor": 50, "default": "0 kWh"}. It fills the
time slots for which the referenced sensor holds no value, and is settable
from the flex-model UI.

This is the uncontroversial half of #2267, split out on Felix's suggestion
so it can land while the SoC constraint hardness question is settled across
the whole flex-model (see #2395). The canonical soc-min/soc-max work stays
on feat/dynamic-soc-bounds-defaults.

Note that a default fills *every* slot the sensor leaves empty, so a sensor
recording only occasional setpoints becomes densely constrained; the field
documentation says so.

Also omit `default` from serialized sensor references when it is unset,
rather than emitting `default: None`, which is not valid input on the way
back in and broke the forecaster config round-trips.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Coverage Stats

30 of 42 new or added lines in 2 files covered. (71.43%)

67 existing lines in 2 files now uncovered.

17131 of 20449 relevant lines covered (83.77%)

0.84 hits per line