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 tutorial for modelling dynamic network capacity contracts #999

Open
Flix6x opened this issue Mar 4, 2024 · 1 comment
Open

Create tutorial for modelling dynamic network capacity contracts #999

Flix6x opened this issue Mar 4, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation Scheduling

Comments

@Flix6x
Copy link
Contributor

Flix6x commented Mar 4, 2024

Since #985 it is possible to set up dynamic site capacities for the storage scheduler to be taking into account. This would be worth expanding our collection of example tutorials.

For example, with a site consumption capacity that is reduced in the evening (e.g. for public charging), and/or a site production capacity that is reduced in the afternoon (e.g. for solar parks). This could be a simple time-of-use sensor.

It's also possible to set up more dynamic site capacities whose sensor values are set by (or collected from) the distribution system operator, or a balance responsible party, but that's probably beyond the scope of a simple tutorial.

@Flix6x Flix6x added documentation Improvements or additions to documentation Scheduling labels Mar 4, 2024
@nhoening
Copy link
Contributor

nhoening commented Mar 4, 2024

Good idea. We can also add this to the tutorial which introduces an example with grid constraints.

I believe the number of tutorials should not become too high.

Btw, that tutorial should show the grid constraint in the plots, even more important when it is dynamic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation Scheduling
Projects
None yet
Development

No branches or pull requests

2 participants