You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: