feat: store aggregate power schedule, too, for each site#168
Open
feat: store aggregate power schedule, too, for each site#168
Conversation
Signed-off-by: F.N. Claessen <felix@seita.nl>
…schedule-per-site
…, for the purpose of peak pricing Signed-off-by: F.N. Claessen <claessen@seita.nl>
Signed-off-by: F.N. Claessen <claessen@seita.nl>
Contributor
|
FlexMeasures/flexmeasures#1736 will be part of v0.31! |
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
2 participants
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.
This relies on FlexMeasures/flexmeasures#1736, which I'm not sure will be part of release v0.31, though. Without this PR, the HEMS/CEMS script just doesn't show any aggregate power schedules for the sites. Not critical, but nice for demos.