Data Standards and Schemas for Fusion Codes
Shared data schemas define a common language for plasma state so independently developed codes can exchange information without custom translation.
A common language
An ecosystem of codes can only be composed if they agree on how to represent plasma state. Data standards and schemas define that agreement: a formal, versioned description of how equilibria, profiles, geometry, and diagnostics are structured and named, so that a code from one group can consume the output of another directly. Without a shared schema, every code pairing needs bespoke translation glue that is fragile and multiplies with the number of codes.
This is the quiet infrastructure that makes integrated modeling practical rather than a permanent integration project.
Structure and physics meaning
A good schema fixes not just data types but physical meaning: units, sign conventions, coordinate definitions, and the exact averaging behind each quantity. Ambiguity in a sign convention or coordinate direction is a classic source of silent errors when coupling codes, so precise definitions are the point of the standard.
Versioning and evolution
Standards evolve as physics understanding and code needs grow. Versioning lets the schema change without breaking existing data, and clear deprecation paths let codes migrate. Long-lived provenance records depend on knowing which schema version a dataset uses.
Design relevance
The whole-device simulations behind the Hyperion breeder and the burner concepts pass data among many codes through shared schemas, which is what lets a change in one module propagate cleanly through the pipeline. Consistent, versioned data representation supports the reproducible, auditable design record kept before construction begins Q2 2027.
- Common versioned description of plasma state
- Fixes units, sign, and coordinate conventions
- Removes bespoke code-to-code translation
- Underpins integrated modeling and provenance