FlexMeasures / flexmeasures-client / 41873862762

96%

push

github

fix(FRBC): ask for a schedule in the power values the actuator can run at (#248)

* fix(FRBC): ask for a schedule in the power values the actuator can run at

An S2 actuator states, per operation mode and per element of it, the power
ranges it can run in. A heater that is either off or at 883.7 W has no power
value in between, and a heat pump has no negative one at all. The flex model
said none of that, so the scheduler planned the whole range as if it were
continuous, and a resource manager had to round a fractional power into a
full-on block, overshooting the capacity its site is held to. A consumption-only
actuator was worse off: with no production capacity stated, its storage could be
planned as if it were a battery feeding the grid.

So the widest range the actuator states becomes a consumption-capacity and a
production-capacity, each non-negative, and the distinct ranges become the
operation-modes bands, where there is more than one of them. A single band is
the capacity range itself and is left out. S2's one signed range maps onto
FlexMeasures' two directions by sign, so a band spanning zero becomes both,
each starting at zero.

The bands are asked for only of a server at v1.0.0 or newer, which is the
release that added the field. A flex model naming a field the server does not
know is refused outright, which would leave the resource manager with no
schedule at all, so an older server is asked without the bands and told so in
the log.

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

* fix(FRBC): ask for one band too, where it says more than the capacities do

The bands were left out wherever there was only one of them, on the reasoning
that a single band is the capacity range itself. That holds only for a band that
runs through zero. An actuator that runs at 200 W or not at all declares one
band from 200 W upwards, and... (continued)

2 of 2 new or added lines in 1 file covered. (100.0%)

997 of 1042 relevant lines covered (95.68%)

9.57 hits per line