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.

Sign up for GitHub

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

Jump to bottom

VRE_STOR units use wrong derating factor when writing capacity value? #584

Closed
cfe316 opened this issue Nov 22, 2023 · 3 comments
Closed

VRE_STOR units use wrong derating factor when writing capacity value? #584

cfe316 opened this issue Nov 22, 2023 · 3 comments
Assignees
@lbonaldo
Labels
bug Something isn't working question Further information is requested

Comments

@cfe316
Copy link
Collaborator

cfe316 commented Nov 22, 2023 •
edited
Loading

write_reserve_margin_revenue uses CapResVreStor_$res,
but
write_capacity_value only uses CapRes_$i. Which of these should be used when computing capacity value, reserve margin revenue, etc for VRE_STOR resources?
@aneeshamanocha @gmantegna .
@cfe316 cfe316 added bug Something isn't working question Further information is requested labels Nov 22, 2023
@lbonaldo lbonaldo self-assigned this Jan 8, 2024
@JesseJenkins
Copy link
Collaborator

I assume this is CapResVreStor_$res as it is the newer one, but @aneeshamanocha please confirm.

@aneeshamanocha
Copy link
Contributor

Confirming that it should be CapVreStor_$res.

lbonaldo added a commit to lbonaldo/GenX that referenced this issue Jan 31, 2024
@lbonaldo
Fix GenXProject#584: derating factor for VRE_STOR in write_capacity_v…
dc7faea 
…alue
@lbonaldo lbonaldo mentioned this issue Jan 31, 2024
Merged
lbonaldo added a commit that referenced this issue Feb 1, 2024
@lbonaldo
Fix #584: derating factor for VRE_STOR in write_capacity_value (#618)
929839b
@lbonaldo
Copy link
Collaborator

lbonaldo commented Feb 1, 2024

Thank you @aneeshamanocha. Fixed in #618.

@lbonaldo lbonaldo closed this as completed Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lbonaldo lbonaldo

Labels
bug Something isn't working question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@cfe316 @JesseJenkins @aneeshamanocha @lbonaldo