Differentiate nuclear technologies by size and reactor type
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
No files, tests, or entry points are named. Start by inspecting how the repository currently represents nuclear technology and existing versus buildable capacity, then review the data conventions for costs, lifetimes, construction times, and operational parameters. Done means the proposed size and reactor-type distinctions are represented consistently for both capacity categories with validated assumptions.
Written by the indexing model from the issue text.
Description
I'd like to suggest the representation of nuclear power technologies by differentiating them by size (large reactors vs small modular reactors) and by reactor type (PWR, HTGR, etc.), and applying this distinction to both existing and buildable capacity.
Right now, nuclear is modeled as a single generic technology, but there are major differences between different technologies.
Each class has distinct:
- Capital cost (CAPEX);
- O&M cost structure;
- Construction time and modularity;
- Ramp rates and flexibility;
- Applicability (grid baseload vs remote/off-grid, industrial heat, etc.).
A first-level split could distinguish:
- nuclear_large
- nuclear_smr
A second-level refinement could add specific reactor types: - nuclear_smr_pwr
- nuclear_smr_htgr
This would better reflect current technology trends and allow more detailed modeling of future scenarios – especially given the increasing focus on SMRs in Europe, USA and beyond.
- Dominant language
- Python
- Stars
- 130
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
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.
More from PyPSA/technology-data
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
PyPSA/technology-data#271 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
PyPSA/technology-data#284 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 68/100
PyPSA/technology-data#283 ·
-
feature
Difficulty 4/5 3-5 days Newbie friendliness 38/100
PyPSA/technology-data#282 · 4 comments ·
-
bug
Difficulty 5/5 Over a week Newbie friendliness 25/100
PyPSA/technology-data#281 ·
All issues in PyPSA/technology-data
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
canonical/paas-charm#368 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
tech debt
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
StevenBlack/hosts#3256 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
qualcomm/qai-appbuilder#275 ·