PyPSA / PyPSA/powerplantmatching
Default to global configuration?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 227
- Forks
- 74
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 4
Description
Given that PyPSA-Earth now uses powerplantmatching extensively, would it make sense to extend the configuration to global scope?
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
Start by reviewing how configuration is currently scoped in powerplantmatching and how PyPSA-Earth uses it. Clarify what “global scope” should mean and which configuration behavior is expected before identifying the affected entry points; the issue is done when the scope and resulting behavior are agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100