-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue 450 api option to customize which price and power sensors to take into account for scheduling #451
Merged
Flix6x
merged 39 commits into
main
from
Issue-450_API_option_to_customize_which_price_and_power_sensors_to_take_into_account_for_scheduling
Aug 24, 2022
Merged
Conversation
This file contains 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
…sumption and feed-in Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Pull Request Test Coverage Report for Build 2920131604
💛 - Coveralls |
…include in the aggregate power flow Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
… headroom with respect to the PV system's nominal capacity Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
…flexible devices Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
…e_and_power_sensors_to_take_into_account_for_scheduling
…e_and_power_sensors_to_take_into_account_for_scheduling # Conflicts: # flexmeasures/cli/data_add.py # flexmeasures/data/services/scheduling.py
nhoening
requested changes
Jul 30, 2022
…uling Signed-off-by: F.N. Claessen <felix@seita.nl>
…heduling Signed-off-by: F.N. Claessen <felix@seita.nl>
…fined in the conftest) are measurements rather than forecasts Signed-off-by: F.N. Claessen <felix@seita.nl>
…casts to be present Signed-off-by: F.N. Claessen <felix@seita.nl>
…one instead of UTC Signed-off-by: F.N. Claessen <felix@seita.nl>
…one instead of UTC Signed-off-by: F.N. Claessen <felix@seita.nl>
…in the Europe/Amsterdam timezone instead of UTC Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
…consumption of the devices, instead of being applied to the consumption of the single flexible device under consideration. Likewise for production. Signed-off-by: F.N. Claessen <felix@seita.nl>
nhoening
requested changes
Aug 23, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like it.
I don't think I have big requests, should be possible to bring into 0.11. Well, you decide.
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
I still have to open up some new issues corresponding to open discussions in this PR, but would you now approve this PR code-wise? |
This was referenced Aug 24, 2022
nhoening
approved these changes
Aug 24, 2022
Flix6x
deleted the
Issue-450_API_option_to_customize_which_price_and_power_sensors_to_take_into_account_for_scheduling
branch
August 24, 2022 15:44
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR introduces three optional fields to the
sensors/(id)/schedules/trigger
endpoint to allow further customization of optimization context:consumption-price-sensor
: prices upward deviations from previous zero-consumption commitmentsfeed-in-price-sensor
production-price-sensor
: prices downward deviations from previous zero-consumption commitmentsinflexible-device-sensors
: their power forecasts are included in the aggregate loadI included an automated test for the battery solver within the optimization context of a building in which solar PV is present, which limits the battery's headroom to discharge.
Another automated test I envision is still missing, for a setting in which the feed-in price is significantly lower than the consumption price, which motivates maximizing self-consumption.
Closes #450 (which contains our initial discussion).
Next steps are: