-
Notifications
You must be signed in to change notification settings - Fork 126
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
[Question]: What should Cap_Size be set to for generators? #800
Comments
@lbonaldo or @sambuddhac ☝️ ? |
Hi Nick, For almost anything* it doesn't matter, you can leave it as 1 or set it to a 'realistic' value like 100 (for 100 MW), if it's a typical power plant or something. Most of the time* it's only used for internal scaling of variables; the result should cancel out. If you want to prove it to yourself, try two different values and see where it makes a difference. It's supposed to represent the capacity of a single 'plant unit' of the resource under consideration. Where it does matter I will describe below:
Fair!
Megawatts.
It's required to sensibly use
No. It can interact with Existing_Cap_MW (and the minimum and maximum capacity fields) if you're using integer unit commitment. For example if you set Min_Cap_MW==Max_Cap_MW then it had better be an integer multiple of Cap_Size or the problem will be infeasible. |
Thanks, @NLaws, and sorry about that. Based on your feedback, we've added |
Question
Cap_Size
is used in many places in the source code, and it appears to default to1
, but the documentation only mentions it in relation to maintenance and fuel. It seems likeCap_Size
should be documented in the inputs section. What are its units? When should it be specified? Should it be equal to theExisting_Cap_MW
in general?Additional context
No response
The text was updated successfully, but these errors were encountered: