PyPSA / PyPSA/technology-data

Differentiate nuclear technologies by size and reactor type

Open
#232 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
130
Forks
59
PR merge metrics
No merged PRs in 30d

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
python
Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.