Integrated Suite / Fusion Core
TRANSP.
Interpretive and predictive tokamak transport analysis.
Question, model and applicability
See function and workflow mapping; scope-specific question requires curation.
- Physics / modeled scope
- Integrated Plasma
- Model evidence and limits
- Primary project documentation or research description. Individual component codes and data access may have separate conditions. Requires expert preparation of profiles and diagnostic inputs.
- Conceptual reactor families
- Tokamak
- Components
- Core plasma · Heating System
- Inputs
- Equilibrium; profiles; diagnostic and actuator histories
- Expected output types — no results supplied
- Power balance; transport coefficients; fast-ion and profile evolution
- Applicability basis
- Editorial question/component mapping; not a validated design-specific capability claim
Access and setup
- Access route
- Application Required
- License summary
- Not independently classified; review upstream license
- Administrative access assessment
- moderate_to_high; application required
- Programming effort assessment
- high
- Hardware assessment
- Not assessed; consult upstream requirements.
- Implementation and interface languages
- Fortran;support interfaces
- Language evidence
- Primary description; unconfirmed implementation explicitly labeled
- Repository primary language — metadata classification
- Not independently recorded.
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
- Princeton Plasma Physics Laboratory; TRANSP collaboration
- Training, examples and support
- Documentation and institutional user support.
- Reference evidence
- No specific reference case audited in this review.
- Neighboring tools
- TORIC; NUBEAM; OMFIT
- Coupling evidence
- Candidate partners only; use workflow edge status for documented versus proposed connections.
- Maintenance evidence
- No live repository activity audit; see dated primary source and evidence limits.
- Observed release tag
- Not independently recorded.
- Observed release date (UTC)
- Not independently recorded.
- Repository push activity (UTC)
- Not independently recorded.
- Repository archived
- Unknown
- Release caveat
- No current release confirmed; blank does not mean no release exists.
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
Not rated yet — the available evidence has not been reviewed in enough detail.
Not enough comparable reviewed evidence to assign a rating; unknown is not zero.
Read the rating anchors and eligibility rules →Provenance and corrections
- Aliases
- Not independently recorded.
- Normalization notes
- Not independently recorded.
- Source-row references
- Codes!137
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 (transp), the field to change and a public primary source through the existing contact page.