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

STOR_ASYMMETRIC resources without REG have no limit on vCHARGE if Reserves=1 and other STOR_ASYM_REG resources exist #564

Closed
cfe316 opened this issue Oct 13, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@cfe316
Copy link
Collaborator

cfe316 commented Oct 13, 2023

There's a logical error in the construction of STOR_ASYMMETRIC resources which don't have REG.

  • storage_asymmetric_reserves! sets the upper limit on vCHARGE for these kinds of resources. It should be less than eTotalCapCharge.

The construction of the sets:

STOR_ASYMMETRIC = inputs["STOR_ASYMMETRIC"]

STOR_ASYM_REG = intersect(STOR_ASYMMETRIC, inputs["REG"]) # Set of asymmetric storage resources with REG reserves
STOR_ASYM_NO_REG = setdiff(STOR_ASYMMETRIC, STOR_ASYM_REG) # Set of asymmetric storage resources without REG reserves

The existing logic:

if !isempty(STOR_ASYM_REG)
    @constraints(STOR_ASYM_REG)
else
    @constraints(STOR_ASYM_NO_REG)
end

However, there can be some resources in each of these two sets. The correct logic should be (as in other similar functions)

if !isempty(STOR_ASYM_REG)
    @constraints(STOR_ASYM_REG)
end
if !isempty(STOR_ASYM_NO_REG)
    @constraints(STOR_ASYM_NO_REG)
end
@cfe316 cfe316 added the bug Something isn't working label Oct 13, 2023
@cfe316 cfe316 changed the title STOR_ASYMMETRIC resources without REG have no limit on vCHARGE if Reserves=1 STOR_ASYMMETRIC resources without REG have no limit on vCHARGE if Reserves=1 and other STOR_ASYM_REG resources exist Oct 13, 2023
@cfe316
Copy link
Collaborator Author

cfe316 commented Oct 13, 2023

This would be fixed by #562 .

@cfe316
Copy link
Collaborator Author

cfe316 commented Nov 18, 2023

The fix for this has been merged to develop.

@cfe316 cfe316 closed this as completed Nov 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant