Operational reserve constraint for sector-coupling network
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 614
- Forks
- 459
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 6
Description
Operational reserve constraint for sector-coupling network
The current constraint for operational reserve margin only works for electricity only networks. This could be extended for the sector-coupling networks or there should be at least a warning that the constraint does not work as intended with a sector-coupled network.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read scripts/solve_network.py around lines 387-454, starting with the operational reserve margin constraint and how it assumes an electricity-only network. Compare its behavior for sector-coupled networks; done means the constraint works as intended there or a warning clearly reports that it does not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100