Coordinate cost years
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 148
- Forks
- 55
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
Checklist
- I am running on an up-to-date
pypsa-usaenvironment. Update viaconda env update -f envs/environment.yaml
Issue exisits on what branch
Master, Develop
The Issue
Our primary data source for cost data is the NREL ATB. We supplement this with pypsa/technology-data generated for a specific investment year. These data sources are not consistent with what year their units are in.
The ATB is given in 2021 USD, while the technology-data will adjust for inflation and give it in monetary units for that year (ie. 2030 EUR). Note, we do convert to USD.
We should ensure that all costs are given in the same monetary unit years. Most data right now is coming from ATB, so its probably not a huge deal. But something to correct if we start pulling more data from technology-data.
Steps To Reproduce
No response
Expected Behavior
No response
Error Message
No response
Anything else?
No response
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 where NREL ATB and pypsa/technology-data costs enter the model, then compare their monetary-year conventions using the linked ATB and technology-data documentation. Define a single monetary base year and verify that both sources use it consistently; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100