Change default value of allow_startup_shutdown param to 1 #1072
Conversation
This file contains 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
Setting this parameter to 0, which is also its default value, could result in an infeasibility since max_shutdown_power_constraint_rule (which only allows Provide_Power_Shutdown_MW = 0) is incompatible with ramp_during_shutdown_constraint_rule (which enforces the Shutdown_Ramp_Rate_MW_Per_Tmp).
|
@sriharid, the default value of this param is 0 by design. The goal was to ask the user to explicitly enable the startup/shutdown trajectory functionality when they have inputs for it. The relevant constraints need to be turned off when inputs are not present to avoid "phantom" generation. Please just set the param to 1 when using the functionality. |
|
Understood @anamileva, I am closing this PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Setting this parameter to 0, which is also its default value, could result in an infeasibility since max_shutdown_power_constraint_rule (which only allows Provide_Power_Shutdown_MW = 0) is incompatible with ramp_during_shutdown_constraint_rule (which enforces the Shutdown_Ramp_Rate_MW_Per_Tmp).
Fixes #1071