test: add feed-in cap recovery case for grid export limit#93
Merged
Conversation
Covers the German 70% feed-in rule scenario from evcc-io/evcc#23042: with a grid export cap the battery charges into the PV peak to recover energy that would otherwise be curtailed, staying feasible.
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.
pairs with evcc-io/evcc#23042
A grid feed-in cap such as the German 70% rule limits export power at the grid connection point. The inverter curtails anything above it and that energy is lost unless a battery charges at that moment. The MILP already models
p_max_expas a soft cap, so this pins the behavior with a data-driven case.test_cases/022-feed-in-cap-recovery.json: a 6 kWh PV peak against a 2 kW export cap. The optimizer charges the battery with 4 kWh into the peak, exports the capped 2 kW, and curtails nothing (grid_export_overshootall zero) while stayingOptimal.