MUST_RUN units have uncapped reserves
cfe316 opened this issue · comments
If the user enters Reg_Max > 0 or Rsv_Max > 0, these units will be part of REG or RSV, respectively. However, there are no constraints on vRSV or vREG for these units.
This is currently the case for RealSystemExample/ISONE_Trizone, which is the only example with Reserves=1.
This is no longer the case for that example, on the develop branch, as of #577.
In general we should add a check that MUST_RUN units can never contribute to reserves.
- upon loading a MUST_RUN unit, check that Reg_Max, Rsv_Max are zero, or throw an error.
This should be fixed in Main since MUST_RUN units were added to RealSystemExample with 852cf37, which is still in develop. I created a PR targeting develop to validate MUST_RUN resources and fix this bug.
Fixed in #619.