Systems Code / Fusion Core
PROCESS.
Self-consistent fusion power-plant systems sizing and optimization.
Question, model and applicability
See function and workflow mapping; scope-specific question requires curation.
- Physics / modeled scope
- Plant Systems
- Model evidence and limits
- Primary project documentation or research description. Current repository says pure Python and v3 undergoing restructuring without backward compatibility. Reduced models do not replace detailed component analysis.
- Conceptual reactor families
- Tokamak · Stellarator
- Components
- Whole plant
- Inputs
- Design constraints; engineering and physics assumptions
- Expected output types — no results supplied
- Plant parameters; constraint margins; cost and power estimates
- Applicability basis
- Editorial question/component mapping; not a validated design-specific capability claim
Access and setup
- Access route
- Open Source
- License summary
- MIT
- Administrative access assessment
- low administrative barrier; build effort separate
- Programming effort assessment
- moderate
- Hardware assessment
- Not assessed; consult upstream requirements.
- Implementation and interface languages
- Python;older releases Fortran
- Language evidence
- Primary description; unconfirmed implementation explicitly labeled
- Repository primary language — metadata classification
- Python
Implementation, bindings and interface languages are retained as described in the source. A separate interface-language claim is not inferred from repository statistics. Access descriptions do not grant a license or entitlement.
Check upstream license / distribution termsEvidence, integration and stewardship
- Upstream steward / project attribution
- UK Atomic Energy Authority
- Training, examples and support
- Installation, usage, examples, publications and tracked regression tests.
- Reference evidence
- Published/documented reference only; no benchmark reproduced here.
- Neighboring tools
- Not independently recorded.
- Coupling evidence
- Candidate partners only; use workflow edge status for documented versus proposed connections.
- Maintenance evidence
- Repository metadata checked; pushed_at is any-branch activity, not support, correctness or release certification.
- Observed release tag
- v3.4.2
- Observed release date (UTC)
- 2026-08-14T15:21:13Z
- Repository push activity (UTC)
- 2026-09-08T15:43:56Z
- Repository archived
- No
- Release caveat
- GitHub latest stable release endpoint; may be a suite tag or older than active development.
Software tests, numerical verification, experimental validation and uncertainty analysis are different evidence types. No case was executed or independently reproduced for this catalog.
Provisional editorial readiness
86.25 / 100 in the Plant Design Screening cohort. This is a snapshot before geometry, model, hardware and access filtering; it is not a universal ranking or scientific accuracy score.
| Dimension | Assessment / 4 | Weight |
|---|---|---|
| Documentation | 4 | 25% |
| References | 3 | 25% |
| Access | 4 | 20% |
| Integration | 3 | 15% |
| Stewardship | 3 | 15% |
Documentation and examples; tracked tests and regression cases; public source; Python workflow with version changes; recent release
Read the rating anchors and eligibility rules →Provenance and corrections
- Aliases
- Not independently recorded.
- Normalization notes
- Current project describes a Python implementation and ongoing restructuring; historical Fortran labels can mislead.
- Source-row references
- Not independently recorded.
- ukaea.github.io · source reference
- github.com · source reference
- api.github.com · source reference
- github.com · source reference
A source link shows where the record came from. It does not mean every linked page was deeply reviewed or that current access is guaranteed. Public attribution does not imply endorsement or a relationship with Morton.
For a correction, include this record ID (process), the field to change and a public primary source through the existing contact page.