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

create units_started_up and units_shut_down variables for ramping cases #1033

Merged
merged 1 commit into from
Jun 10, 2024

Conversation

nnhjy
Copy link
Collaborator

@nnhjy nnhjy commented Jun 10, 2024

In cases where the user uses the "ramp_up/down_limit" (e.g., issue #1029 ), the ramp_up or ramp_down constraint needs, respectively, the units_started_up or units_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

  • Documentation is up-to-date
  • Unit tests have been added/updated accordingly
  • Code has been formatted according to SpineOpt's style
  • Unit tests pass

@nnhjy nnhjy merged commit 3649028 into master Jun 10, 2024
5 checks passed
@nnhjy nnhjy deleted the ramping-needs-switch branch June 10, 2024 14:05
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

Successfully merging this pull request may close these issues.

None yet

1 participant