Start independently
SNT contributors or code users can prepare a first parameter model and adapter without implying support from the original code maintainers.
THE SNT INITIATIVE
Shared inputs.
Independent science.
Established scientific codes have their own input formats, unit conventions, and validation rules. This initiative explores a common, optional DIPL layer that makes those interfaces easier to inspect, check, and reuse.
FIRST INTEGRATION
Fit around the code you already use.
01DIPL model
Typed values, units, constraints, and relationships.
02SNT3
Parse, evaluate, inspect, and validate the model.
03Code adapter
Apply code-specific checks and write native files.
04Existing solver
Run with its familiar parser, numerics, and workflow.
SNT3 v0.9.3 lets adapters record a resolved plan of native outputs in the DIPH5 snapshot. Projects can adopt this to make their translation decisions inspectable. An external adapter can later be replaced if the code's maintainers choose a deeper SNT3 integration. Native input files remain usable throughout.
POSSIBLE NEXT STAGE
From wrapper
to integration.
A mature collaboration can move SNT3 into the code's own input path. C++ and Python APIs expose evaluated parameters directly; the C binding is experimental. For codes that prefer compiled or prebuilt inputs, SNT3 can export validated parameters as C++, C, Fortran, Rust, Julia, JSON, or YAML. Each code chooses whether and how to make that change.
A model that can be inspected.
Viewer guide ↗The optional, read-only Parameter Viewer opens a live DIPL project or a DIPH5 snapshot and shows evaluated values, units, provenance, and recorded dependencies. Snapshots retain selected provenance, not complete source text.
START WITH A PINNED CODE
Two commands.
A traceable setup.
From an empty local workspace, snt hub fetch <project> brings in the pinned source and DIPL layer. snt hub setup <example> prepares native inputs and a DIPH5 snapshot under runs/, together with verified assets for a complete setup. A per-run --override-file tunes evaluated values. Building and running the solver remain project-specific capabilities.
WORKING TOGETHER
Clear roles.
Clear evidence.
Bring in code experts
Maintainers and domain experts check parameter meanings, generated files, supported versions, and the scope of each comparison.
Show the evidence
The registry separates maintainer support from settings checks, successful builds, and validation of scientific results.
EXPLORE & CONTRIBUTE
There is more than one way in.
Read the language, explore SNT3, or suggest an established code with a documented parameter interface.