FlexMeasures / flexmeasures / 24238400989

81%

Build Type

push

github

Committed by web-flow

Commit Message

Feat/dynamic soc at start (#2026)

* Use state-of-charge to infer storage start SoC

* Add coverage for inferred storage start SoC

* Document state-of-charge as start SoC source

* style: run pre-commit

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

* fix: normalize SoC time-series values before lookup

* fix: support inherited soc-max for percent SoC lookup

* Update flexmeasures/data/schemas/scheduling/metadata.py

Co-authored-by: Felix Claessen <30658763+Flix6x@users.noreply.github.com>
Signed-off-by: Mohamed Belhsan Hmida <149331360+BelhsanHmida@users.noreply.github.com>

* Update flexmeasures/data/models/planning/storage.py

Co-authored-by: Felix Claessen <30658763+Flix6x@users.noreply.github.com>
Signed-off-by: Mohamed Belhsan Hmida <149331360+BelhsanHmida@users.noreply.github.com>

* Rename state-of-charge schema wording

* Refine soc-at-start lookup behavior

* docs: add note for  lookup radius 4 value

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

* Make soc lookup slack explicit

* fix: handle missing state-of-charge sensors

Context:
- Resolving soc-at-start from state-of-charge happens before schema deserialization.
- Missing sensor ids should raise a controlled user-facing error instead of a raw ORM lookup failure.

Change:
- Use db.session.get for the state-of-charge sensor lookup.
- Raise ValueError when the configured sensor id does not exist.
- Add a regression test covering the missing-sensor case.

* docs: refresh generated OpenAPI specs

Context:
- The OpenAPI snapshot was stale relative to the current schema metadata.
- Regenerating it is useful, but it is separate from the scheduling bug fix.

Change:
- Rebuild flexmeasures/ui/static/openapi-specs.json from the current OpenAPI generator output.

* fix: use device sensor for soc percent fallback

Context:
- State-of-charge sensors with '%' units need soc-max as capacity for conversion to MWh.
- In multi-device scheduling, the releva... (continued)

Coverage Stats

69 of 91 new or added lines in 3 files covered. (75.82%)

3 existing lines in 2 files now uncovered.

11780 of 15130 relevant lines covered (77.86%)

0.78 hits per line