FlexMeasures / flexmeasures / 31180608506
84%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 175
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: 83.968% (+0.005%) from 83.963%
31180608506

push

github

web-flow 
Keep explicit zero directional capacity hard under relax-constraints (#2345)

* Keep explicit zero directional capacity as a hard bound

With relax-constraints defaulting to True, an explicit
production-capacity: 0 (or consumption-capacity: 0) was turned into a
soft FlowCommitment whenever breach prices were present. The LP could
then schedule power in a physically impossible direction (e.g. produce
from a heat pump).

Treat an all-zero directional capacity as a physical impossibility:
keep the hard derivative bound and skip soft breach commitments.
Non-zero (economic) capacity limits may still be relaxed.

Fixes #2323

Signed-off-by: Sankalp Thakur <sankalphimself@gmail.com>

* test: non-zero directional capacity still softens under breach prices

Companion regression for #2323: only explicit zero stays hard; economic
non-zero production/consumption capacities must still create soft breach
commitments.

Signed-off-by: Sankalp Thakur <sankalphimself@gmail.com>

* test: cover consumption-capacity 0 schedule path for #2323

Parametrize the end-to-end schedule regression so both production and
consumption explicit zeros stay hard under directional breach prices.

Signed-off-by: Sankalp Thakur <sankalphimself@gmail.com>

* test: cross-ref #2329 EVSE discharge in zero-capacity regression

Signed-off-by: Sankalp Thakur <sankalphimself@gmail.com>

* Pin the windowed-zero contract, and write the zero rule down

The rule this PR implements is that a directional capacity of zero states a
physical property of the device when it holds for the whole scheduling window,
and a preference when it covers only part of it. That rule was emergent: nothing
stated it, and nothing stopped a later reader from "fixing" the horizon-wide test
into a per-timestep one, which would harden preferences.

So pin the preference half with a test, and state the rule where users meet the
fields. V2G-Liberty relies on the preference half to keep a charger idle during a
calendar car reserva... (continued)

17179 of 20459 relevant lines covered (83.97%)

0.84 hits per line

Jobs
ID Job ID Ran Files Coverage
1 31180608506.1 175
83.97
 GitHub Action Run
Source Files on build 31180608506