FlexMeasures / flexmeasures-client / 41935830916
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
41935830916

push

github

web-flow 
feat(FRBC): plan a schedule against what the actuator converts power at (#253)

* feat(FRBC): plan a schedule against what the actuator converts power at

An operation mode states a fill rate and a power range, and the ratio between the
two is what the actuator converts drawn power into stored energy at. For the
apartment heaters in our own smoke tests that is 3800 W of heat into the buffer
for 883.7 W of electricity: a coefficient of performance of 4.3.

Nothing said so, and a scheduler told nothing plans the storage as if an actuator
converted power one for one. A plan then expects a fill-level target to be reached
at a quarter of the power it really takes, or, the other way round for a lossy
battery, expects stored energy the actuator never delivers.

So the modes' own ratio goes out as FlexMeasures' charging-efficiency. It is read
from a sensor rather than taken in the flex model, so it is recorded first, over
exactly the window the schedule covers, and the flex model names the sensor only
where there is something on it to read: a plan that assumes a lossless actuator
beats no plan at all, as long as the log says so. The same value for the same
window is recorded once, since a belief repeating the one before it is a row for
nothing, and two of them inside a second collide on the belief's own key.

A fill rate is per second of whatever unit a fill level is recorded in, so a
kilowatt hour per second is 3.6 million watts; both sides of the ratio are taken
in watts, and an energy unit nothing converts is refused rather than wrong by a
factor of thousands. An idle mode, and one that only feeds back, state no power to
convert: the first has no efficiency and the second is a discharge, which
FlexMeasures takes separately.

Where the modes disagree, the lowest goes out, since FlexMeasures takes one
efficiency for the whole device. Converting less than the actuator really does has
a plan reach its target early, where converting more has it reach it late, a... (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.13 - 41935830916.1 6
95.68
GitHub Action Run
2 macos-latest - py3.11 - 41935830916.2 6
95.68
GitHub Action Run
3 macos-latest - py3.12 - 41935830916.3 6
95.68
GitHub Action Run
4 macos-latest - py3.13 - 41935830916.4 6
95.68
GitHub Action Run
5 ubuntu-latest - py3.11 - 41935830916.5 6
95.68
GitHub Action Run
6 ubuntu-latest - py3.14 - 41935830916.6 6
95.68
GitHub Action Run
7 macos-latest - py3.10 - 41935830916.7 6
95.68
GitHub Action Run
8 macos-latest - py3.14 - 41935830916.8 6
95.68
GitHub Action Run
9 ubuntu-latest - py3.12 - 41935830916.9 6
95.68
GitHub Action Run
10 ubuntu-latest - py3.10 - 41935830916.10 6
95.68
GitHub Action Run
Source Files on build 41935830916