Allow RPS/CES requirements to be enforced explicitly during stress periods - #177
Open
wesleyjcole wants to merge 19 commits into
Open
Allow RPS/CES requirements to be enforced explicitly during stress periods#177wesleyjcole wants to merge 19 commits into
wesleyjcole wants to merge 19 commits into
Conversation
# Conflicts: # reeds/core/setup/b_inputs.gms # reeds/core/solve/2_temporal_params.gms # reeds/resource_adequacy/stress_periods.py
github-actions
Bot
added
data_changes
model_changes
docs
postprocessing
switches
labels
aschleif
reviewed
Aug 20, 2026
| set RPSCat_i(RPSCat,i,st) "mapping between rps category and technologies for each state", | ||
| RecMap(i,RPSCat,st,ast,t) "Mapping set for technologies to RPS categories and indicates if credits can be sent from st to ast", | ||
| set RPSCat_i(RPSCat,i,st) "mapping between rps category and technologies for each state", | ||
| RecMap(i,RPSCat,st,ast,htype,t) "Mapping set for technologies to RPS categories and indicates if credits can be sent from st to ast", |
Collaborator
There was a problem hiding this comment.
Why did the htype index have to be added to RecMap?
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.
Summary
This pull request adds a new switch (
GSw_StateRPS_Stress) that allows users to enforce the RPS/CES requirements explicitly during the stress periods. Currently, the RPS/CES requirements are enforced only during the representative periods. By turning on the switch, the requirements can be enforced during all stress periods (with equal weighting) or during the peak load stress periods. Turning the switch on represents that a state would plan to be compliant with the RPS/CES requirement for planned stress conditions, not just for representative conditions.The switch is off by default, so there is no change to default model behavior.
Technical details
Implementation notes
The RPS equations now include a
htypeset, wherehtypeis "rep" or "stress" to indicate whether representative or stress periods are being used for the equation. Representative periods are weighted usinghours(h)like before, and stress periods are weighted using "1" for any stress period included and "0" for all other stress periods.A new linking set
st_szn_stresspeak(st,allszn)is included to specify which stress period is a state's peak day.Outputs are updated so that when the new switch is turned on, the marginal costs show up in the downstream cost reporting.
Switches added/removed/changed
GSw_StateRPS_Stressis new: 0=off (default, no change), 1=weight all modeled stress hours equally, 2=weight only each state's own peak-load stress period(s).Known incompatibilities
The new switch only works with the stress period representation, and the peak load version of the switch only works when peak load stress days are selected. This PR includes checks for both of those conditions so an error message will indicate if a user selected an invalid combination.
Validation, testing, and comparison report(s)
Enforcing the RPS/CES requirements in the stress periods results in more firm low-emission capacity and less gas capacity:
As expected, the states with high CES policies experience the largest changes and build more in-state resources. You can see that in the compare report deck by flipping through slides 18-20 (maps of the generation and transmission build out).
Comparison report: results-Main,CESStress1,CESStress2.pptx
I confirmed that there are no changes with main when the
GSw_StateRPS_Stressis turned off: results-Main,CESBaseline.pptxChecklist for author
Details to double-check
General information to guide review
Did you use LLM tools (chatbot or copilot) in the preparation of this PR? If so, describe how
Yes, I did the code design, and then implemented that design using Claude. I edited most of Claude's comments (still haven't figured out how to get the LLM to write comments I like). The model documentation changes did not use a LLM.