FlexMeasures / flexmeasures / 26687373065

81%

push

github

feat: allow setting a consumption/production sensor in the flex-model of an asset (#2190)

* feat: allow setting a power sensor in the flex_model of an asset when patching

Signed-off-by: F.N. Claessen <claessen@seita.nl>

* fix: fields without a data_key just use the variable name as data_key

Signed-off-by: F.N. Claessen <claessen@seita.nl>

* feat: switch to consumption and production sensor reference fields in DBStorageFlexModelSchema

Signed-off-by: F.N. Claessen <claessen@seita.nl>

* feat: add UI support for new fields

Signed-off-by: F.N. Claessen <claessen@seita.nl>

* docs: document new fields in scheduling.rst

Signed-off-by: F.N. Claessen <claessen@seita.nl>

* feat: add new fields to StorageFlexModelSchema

Signed-off-by: F.N. Claessen <claessen@seita.nl>

* chore: update openapi-specs.json

Signed-off-by: F.N. Claessen <claessen@seita.nl>

* storage: add consumption and production output sensor support
Context:
- StorageScheduler could already write state-of-charge schedules to a secondary sensor
- Users wanted the same for consumption and production power
Change:
- Add StorageScheduler._build_consumption_production_schedules() static method
- Call it in compute(), with resampling and rounding matching the soc_schedule pattern
- If only consumption sensor defined: full power profile (consumption positive, production negative)
- If only production sensor defined: full power profile inverted (production positive, consumption negative)
- If both defined: split — non-negative part to consumption sensor, sign-flipped non-positive part to production sensor
- Include results in return_multiple output as consumption_schedule / production_schedule entries
- Sign convention is encoded in the key name so no consumption_is_positive attribute is needed

* tests: expand storage scheduler tests for consumption/production output sensors
Context:
- StorageScheduler now supports writing schedules to consumption and production sensors
Change:
- test_batter... (continued)

97 of 101 new or added lines in 6 files covered. (96.04%)

12971 of 16092 relevant lines covered (80.61%)

0.81 hits per line