Closed lbonaldo closed 2 months ago
The current multi-stage implementation utilizes the RET_CAP
set to create variables for keeping track of retired capacity across all stages. If there is a change in this set between two stages, this function will throw an exception if a key is not found between the current and previous stages.
Description
The current implementation of multi-stage optimization doesn't allow a resource to switch from
can_retire = 0
tocan_retire = 1
between stages. This PR adds a validation check on thecan_retire
flag and throws an error if necessary.What type of PR is this? (check all applicable)
Checklist
How this can be tested
By running the multi-stage example with
can_retire = 0
for some resources instage = 1
, and then switching tocan_retire = 1
instage = 2
.Post-approval checklist for GenX core developers
After the PR is approved