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

Documentation improvements #1178

Open
Regis-Delubac opened this issue Mar 4, 2025 · 0 comments
Open

Documentation improvements #1178

Regis-Delubac opened this issue Mar 4, 2025 · 0 comments

Comments

@Regis-Delubac
Copy link

In the tutorials, it is often not very clear how a feature works exactly.
I will use the reserve tutorial as a reference (https://spine-tools.github.io/SpineOpt.jl/latest/tutorial/reserves/).

Why do we use a group of nodes? (The note explains that it helps involve variables from its members.) Why don’t we just use the upward reserve node?

What does the function "is reserve node" do? You say it indicates that the node is a reserve node, but how is a reserve node different from a balance node, for example? (The second note partially helps.)

The second note says: "The value is equal to the unit capacity defined for the electricity node. However, the value can be lower if the unit cannot provide reserves with its total capacity."
This shows that the reserve node is indeed weaker than the demand node (which is a good thing), but how can we determine/understand the penalty and constraints related to not providing reserves?

I think it would be very helpful to clarify why each aspect is modeled the way it is in the tutorial so that the approach can be extended to larger models.

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

No branches or pull requests

1 participant