FlexMeasures / flexmeasures / 29433030556

82%

main: 82%

Build Type

Pull #2322

github

Committed by Flix6x

Commit Message

Fix: couple stock constraints for multi-device batteries whose SoC comes from a sensor

In multi-device (list) flex-model mode, soc-at-start is not resolved during
deserialization (unlike single-sensor mode's ensure_soc_at_start()). A battery
whose only SoC input is a state-of-charge sensor (no explicit soc-at-start) - the
production shape of a battery under an apartment - therefore had soc_at_start=None,
so the scheduler applied no stock constraints and the device could discharge far
more energy than its store held.

Resolve a stock's soc-at-start from its (deserialized) state-of-charge sensor or
time series in _prepare()'s per-stock loop, on the stock-owning entry only, so
shared-stock device entries are unaffected. Resolution is defensive: if no recent
SoC value exists, the stock simply keeps no stock constraints (as before) instead
of failing the schedule.

Signed-off-by: F.N. Claessen <felix@seita.nl>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LQFkeGxDwErydUV5ZmHmki

Pull Request Pull Request #2322: Fix: couple stock constraints for multi-device batteries whose SoC comes from a sensor

Coverage Stats

11 of 14 new or added lines in 1 file covered. (78.57%)

30 existing lines in 1 file now uncovered.

14682 of 18009 relevant lines covered (81.53%)

0.82 hits per line