Ensure Constraint of Solar and Solar-hsat with Post Discretization #1342
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.
Bugfix
Changes proposed in this Pull Request
When the post discretization is enabled, the function
add_solar_potential_constraints
is called multiple times.The first time, the optimal capacity of generators with carrier
solar-hsat
is zero. However, the second time, the optimal capacity can be greater than zero which would then overly reduce the potential.Since the
p_nom
is set in the next planning horizon in the ruleadd_brownfield
switching fromp_nom_opt
top_nom
is the correct way to formulate the boundary condition.Checklist
not applicable
envs/environment.yaml
.not applicable
config/config.default.yaml
.not applicable
doc/configtables/*.csv
.not applicable
doc/data_sources.rst
.not applicable
doc/release_notes.rst
is added.not applicable