create units_started_up and units_shut_down variables for ramping cases #1033
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.
In cases where the user uses the "ramp_up/down_limit" (e.g., issue #1029 ), the
ramp_up
orramp_down
constraint needs, respectively, theunits_started_up
orunits_shut_down
variables. Otherwise, the model may become infeasible. However, the variables are not always activated in such cases unless the user specifies the dedicated parameters.Checklist before merging