You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes (for y not in COMMIT) vCAP is in MW and sometime it's in "number of plants". This leads to needed to repeatedly test whether vCAP is in COMMIT in order to correctly set constraints, expressions etc. It also means repeatedly conditionally multiplying by Cap_Size in order to get a quantity in units of MW.
Note that some variable (currently vCAP) does need to be (conditionally) an integer if we want to have integer capacity expansion.
What I might recommend is something like
always have vCAP be in "number of plants" and create a new expression eCAP (or eNewCap) which is always vCAP * Cap_Size, so that it's always in units of MW. For comparison, currently, eTotalCap is always in MW.
optionally also create eCOMMIT/START/SHUT which are vCOMMIT/START/SHUT * Cap_Size.
This would make many expressions and constraints easier to read, and eliminate if statements, at the cost of G (for eCAP) or 3 G T (for the commitment states) new expression terms.
The text was updated successfully, but these errors were encountered:
cfe316
changed the title
Internal issue: vCAP's units depend on whether a unit is in COMMIT
Suggestion to change: vCAP's units depend on whether a unit is in COMMIT
Sep 10, 2023
cfe316
changed the title
Suggestion to change: vCAP's units depend on whether a unit is in COMMIT
(Internal development) Pain point: vCAP has units which are resource-dependent.
Sep 10, 2023
Sometimes (for y not in
COMMIT
)vCAP
is in MW and sometime it's in "number of plants". This leads to needed to repeatedly test whether vCAP is in COMMIT in order to correctly set constraints, expressions etc. It also means repeatedly conditionally multiplying by Cap_Size in order to get a quantity in units of MW.Note that some variable (currently vCAP) does need to be (conditionally) an integer if we want to have integer capacity expansion.
What I might recommend is something like
eCAP
(oreNewCap
) which is alwaysvCAP * Cap_Size
, so that it's always in units of MW. For comparison, currently, eTotalCap is always in MW.eCOMMIT/START/SHUT
which arevCOMMIT/START/SHUT * Cap_Size
.This would make many expressions and constraints easier to read, and eliminate
if
statements, at the cost of G (for eCAP) or 3 G T (for the commitment states) new expression terms.The text was updated successfully, but these errors were encountered: