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

Update/add/refactor Unit Commitment Constraints #665

Closed
ulfmueller opened this issue Sep 21, 2023 · 3 comments
Closed

Update/add/refactor Unit Commitment Constraints #665

ulfmueller opened this issue Sep 21, 2023 · 3 comments
Assignees

Comments

@ulfmueller
Copy link
Member

ulfmueller commented Sep 21, 2023

in particular for our market simulation check and adjust UC constraints.
One possible 'easy to access' source at pypsa-eur
Another source at flexABLE based on Künzel

I think it makes sense to wait for #663 and then use the optimize() function instead of lopf() in order to get the complete picture of all UC constraints.

@ulfmueller ulfmueller self-assigned this Sep 21, 2023
@ulfmueller
Copy link
Member Author

ulfmueller commented Dec 1, 2023

First running example is implemented here.
But many details remain to be done:

  • integrate pypsa-eur data, addressing this dirty line
  • inlcude OCGT (and in general links) into the unit commitment (see here
  • address seasonal storage behavior considering the interface between pre market model and UC market model (somewhere here. How to do might be found in the master thesis by @KathiEsterl concerning snapshot clustering or NEP insights (or further literature research).

@ClaraBuettner
Copy link
Contributor

* [ ]  address seasonal storage behavior considering the interface between pre market model and UC market model ([somewhere here](https://github.com/openego/eTraGo/blob/features/market-simulation/etrago/execute/market_optimization.py#L170-L172). How to do might be found in the master thesis by @KathiEsterl concerning snapshot clustering or NEP insights (or further literature research).

Do you already have a concept for this? I mean sth. like which storages should be affected by this and which data is exchanged? I could implement it (and also think about the questions I had, I just wanted to know if there is already sth. there)

ClaraBuettner added a commit that referenced this issue Feb 12, 2024
…et-market-optimization

Features/#665 interface pre market market optimization
@ClaraBuettner
Copy link
Contributor

All the mentioned points are already included. There might be additional changes and updates in the future, but I will close this issue for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants