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

Startup costs #9

Open
bramvdh91 opened this issue Nov 17, 2023 · 3 comments
Open

Startup costs #9

bramvdh91 opened this issue Nov 17, 2023 · 3 comments
Assignees

Comments

@bramvdh91
Copy link
Collaborator

Adding startup costs for production units in order to run unit commitment problems.
This adds integers to every time step to determine if the component is running or not, and adds startup cost to the cost objective if the component is switched on during that time step.

For now, only for problems without representative days. Adding warning if user specifies a unit commitment problem with representative days.

@bramvdh91 bramvdh91 self-assigned this Nov 17, 2023
@bramvdh91
Copy link
Collaborator Author

Added equations and documentation.
Added simple example Examples/example_startupcosts_singlenode.py, which works.

Currently working on example Examples/example_startupcosts.py. This seems to be infeasible if Qmin > 0 and ExtensivePipe is used as pipe model. The issue thus seems to be related to the combination between the pipe model with heat losses, and the binary variable to indicate if the plant is switched on.

@bramvdh91
Copy link
Collaborator Author

Examples/example_startupcosts.py only returns an infeasible problem if there is no storage, and Qmin > 0.

@bramvdh91
Copy link
Collaborator Author

Found the error in the example, it appears the pipe diameters were the limiting factor.

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

When branches are created from issues, their pull requests are automatically linked.

1 participant