FlexMeasures / flexmeasures-client / 41899236458
96%

DEFAULT BRANCH: main
Ran
Jobs 10
Files 6
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 95.681%. Remained the same
41899236458

push

github

web-flow 
fix(FRBC): record an actuator's power so that it means what the sensor means (#252)

* fix(FRBC): post an actuator's power in the sign the sensor records it in

S2 fixes one sign convention, where positive means consumption. FlexMeasures
leaves it to the sensor, and for a plain power sensor the default is the other
way round: a schedule saved onto such a sensor has its sign flipped on the way
in, so a plan to consume is stored negative.

Posting S2's value as it stands put the measurement and the plan in opposite
directions on one sensor. Measured against a running server, the plan to charge
at 100 W read -0.1 kW and the measurement of charging at 100 W read +0.1 kW,
which in the UI is a device doing the reverse of what it was asked, and in any
report a sign error rather than a magnitude one.

So the sensor is asked, once, which sign it records consumption in, and the
power is posted that way round. A sensor that cannot be read is posted to as S2
states it, with the reason logged, since this handler's own convention said out
loud beats no measurement at all.

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): convert an actuator's power into the unit it is posted in

S2 states a power value in watts. power_unit says what a posted value is
labelled with, and nothing converted between the two, so a deployment recording
its power sensor in kW had 883.7 W posted as 883.7 kW, and FlexMeasures stored
the thousandfold it claimed to be. The default of W needed no conversion, which
is why it took a deployment at another scale to notice.

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): let a second actuator status supersede the first, and say when one is refused

FlexMeasures keys a beli... (continued)

997 of 1042 relevant lines covered (95.68%)

9.57 hits per line

Jobs
ID Job ID Ran Files Coverage
1 ubuntu-latest - py3.11 - 41899236458.1 6
95.68
GitHub Action Run
2 macos-latest - py3.12 - 41899236458.2 6
95.68
GitHub Action Run
3 macos-latest - py3.13 - 41899236458.3 6
95.68
GitHub Action Run
4 macos-latest - py3.14 - 41899236458.4 6
95.68
GitHub Action Run
5 ubuntu-latest - py3.12 - 41899236458.5 6
95.68
GitHub Action Run
6 ubuntu-latest - py3.13 - 41899236458.6 6
95.68
GitHub Action Run
7 macos-latest - py3.10 - 41899236458.7 6
95.68
GitHub Action Run
8 macos-latest - py3.11 - 41899236458.8 6
95.68
GitHub Action Run
9 ubuntu-latest - py3.14 - 41899236458.9 6
95.68
GitHub Action Run
10 ubuntu-latest - py3.10 - 41899236458.10 6
95.68
GitHub Action Run
Source Files on build 41899236458