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

Redundant constraints in storage_symmetric #566

Closed
cfe316 opened this issue Oct 13, 2023 · 2 comments
Closed

Redundant constraints in storage_symmetric #566

cfe316 opened this issue Oct 13, 2023 · 2 comments

Comments

@cfe316
Copy link
Collaborator

cfe316 commented Oct 13, 2023

# Maximum charging rate (including virtual charging to move energy held in reserve back to available storage) must be less than symmetric power rating
[y in STOR_SYMMETRIC, t in 1:T], EP[:vCHARGE][y,t] + EP[:vCAPRES_charge][y,t] <= EP[:eTotalCap][y]

# Max simultaneous charge and discharge cannot be greater than capacity
[y in STOR_SYMMETRIC, t in 1:T], EP[:vP][y,t]+EP[:vCHARGE][y,t]+EP[:vCAPRES_discharge][y,t]+EP[:vCAPRES_charge][y,t] <= EP[:eTotalCap][y]
  • all these quantities are positive
  • the LHS of the second constraint equals the LHS of the first constraint plus some extra terms.
  • both RHS's are the same.
    Therefore the first constraint is redundant. Not sure if we want to remove it, or keep it for future expansion/didactic reasons.
@cfe316
Copy link
Collaborator Author

cfe316 commented Oct 13, 2023

This would be addressed by #562 .

cfe316 added a commit that referenced this issue Nov 18, 2023
This fixes #573, where Reserves + Num_VRE_Bins > 1 would lead to the
VRE_NO_POWER_OUT resources being able to contribute an infinite amount
to the reserves.

This fixes #574, where VRE power output constraints were being applied
length(VRE) times to all VRE resources, when Reserves = 1.

This fixed #566, where some constraints in storage_symmetric were redundant.
---------

Co-authored-by: Luca Bonaldo <[email protected]>
@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
None yet
Projects
None yet
Development

No branches or pull requests

1 participant