EnergySystemsModellingLab / EnergySystemsModellingLab/MUSE_OS
Existing capacity not registered if zero capacity in the starting year
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 29
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
The modeler may want to specify capacity addition in a future year (e.g. if they know a power plant is going to be built in the future). This can be done through the ExistingCapacity.csv file, however anything put in this file will only be registered if there is nonzero capacity in the starting year. If this isn't the case, the asset won't be registered and any additional capacity put in future years won't be applied.
I think maybe a current workaround is to put a small capacity in the starting year (e.g. 0.1), (although I'm not sure whether that actually works), but it would be good to get this working without having to do that
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 tracing how ExistingCapacity.csv is read and how assets are registered when starting-year capacity is zero. Reproduce the case with future capacity only, then verify that the asset is registered and the future addition is applied without adding a workaround capacity in the starting year.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100