-
Notifications
You must be signed in to change notification settings - Fork 3
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
Missing functionality in unit commitment #23
Comments
@sstroemer The old form with GenAboveMinLoad_MW:
So here you need to calculate the incremental_efficiency. Which is a little complicated to explain. With a change form GenAboveMinLoad_MW -> Units_At_Full_Load (see below), the calculation of the input and output flows is much more easy to understand. There is no need to calculate incremental efficiencies anymore: The new formulation for unit type „u“, which may have mutliple identical units installed, and has multiple inputs and putputs: NEW
There is no need to calculate incremental efficiencies anymore and easy to understand. |
Note: The "mention" above from issue "# 25" is not intentional and just GitHub messing with the auto-mention ... |
The current UC formulation is missing a few points that should be properly integrated:
unit.is_on_before
into account, but does not allow choosing that)A lot of that is actually due to the current/old issues with representative Snapshots. Since they conflict with various things, and complicate a lot of different formulations, we discussed removing them on multiple occasions (and switching to a different formulation, e.g., Kotzur et al.). Therefore, this might be best done as part of a larger rework to prevent future mess/dept in the whole UC implementation.
The text was updated successfully, but these errors were encountered: