Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Internal development) Pain point: vCAP has units which are resource-dependent. #548

Open
cfe316 opened this issue Sep 10, 2023 · 0 comments

Comments

@cfe316
Copy link
Collaborator

cfe316 commented 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

  • 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.

@cfe316 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 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant