feat: allow setting a power sensor in the flex-model of an asset when patching#2190
Draft
Flix6x wants to merge 12 commits into
Draft
feat: allow setting a power sensor in the flex-model of an asset when patching#2190Flix6x wants to merge 12 commits into
Flix6x wants to merge 12 commits into
Conversation
… patching Signed-off-by: F.N. Claessen <claessen@seita.nl>
4 tasks
Signed-off-by: F.N. Claessen <claessen@seita.nl>
… DBStorageFlexModelSchema Signed-off-by: F.N. Claessen <claessen@seita.nl>
Signed-off-by: F.N. Claessen <claessen@seita.nl>
Signed-off-by: F.N. Claessen <claessen@seita.nl>
Signed-off-by: F.N. Claessen <claessen@seita.nl>
Signed-off-by: F.N. Claessen <claessen@seita.nl>
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
…ut sensors Context: - StorageScheduler now supports writing schedules to consumption and production sensors Change: - test_battery_solver_multi_commitment: add consumption and production output sensors to the battery, include them in the flex-model, and verify unit conversion (MW → kW) and the split logic (all-positive schedule → consumption all positive, production all zero) - test_trigger_schedule_uses_state_of_charge_sensor_for_soc_at_start: add production output sensor and verify 96 beliefs are stored after scheduling - test_add_storage_schedule_uses_state_of_charge_sensor_for_soc_at_start: add consumption output sensor and verify 48 beliefs are stored after scheduling
… changelog entry Context: - StorageScheduler now writes schedules to consumption/production sensors Change: - Expand CONSUMPTION and PRODUCTION metadata descriptions with the split logic (only consumption, only production, or both defined) and clarify that the sign convention is encoded in the key name (no consumption_is_positive attribute needed) - Add changelog entry in v0.33.0 New features section (PR number TBD)
Signed-off-by: F.N. Claessen <claessen@seita.nl>
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
documentation/changelog.rstLook & Feel
...
How to test
...
Further Improvements
...
Related Items
...
Sign-off