Fix negative maximum contingency in spinning reserves#149
Open
cclyfblink wants to merge 1 commit intoswitch-model:masterfrom
Open
Fix negative maximum contingency in spinning reserves#149cclyfblink wants to merge 1 commit intoswitch-model:masterfrom
cclyfblink wants to merge 1 commit intoswitch-model:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Constrains
MaximumContingencyto be non-negative in the spinning reserves module.When no unit or project contingencies are enabled,
Spinning_Reserve_Contingenciesis empty, butMaximumContingencyis still included inSpinning_Reserve_Up_Requirements. Without a lower bound, solvers can assign a negative value toMaximumContingency, which can offset other positive upward reserve requirements.Tested with
conda run -n switch-env python run_tests.py.