01
Parameter model
A DIPL model describes inputs, units, and constraints. It can be inspected and checked even before a code consumes it.
Model available HOW TO READ THE REGISTRY
Clear labels.
Honest evidence.
A project can have a working adapter without upstream support, or official support before scientific results have been validated. The Hub records these as separate signals so you can judge the integration for your use.
01 / INTEGRATIONHow does SNT reach the code?
02 / SUPPORTWho stands behind this work?
03 / VALIDATIONWhat has been checked?
01 / TECHNICAL PATH
Integration levels.
The level describes the current connection to a code. Moving deeper is optional; an external adapter may be the right long-term fit.
02
External adapter
SNT evaluates the model; an adapter writes the code’s familiar input files. The original solver stays unchanged.
Native files03
Code integration
A code uses evaluated SNT parameters through an API or generated static inputs as part of its own workflow.
A project choiceIntegration can change.
A native-file adapter can later give way to a direct C++ or Python connection, the experimental C binding, or generated static parameters. The registry changes its mode only when that implementation exists.
02 / MAINTAINER RELATIONSHIP
Support status.
A public evidence link is required before a listing claims maintainer review or official support.
01
Unofficial
Independent
Developed by SNT contributors or code users. The original code’s maintainers have not reviewed or endorsed this integration.
Evidence: Repository, contributor, source revision, and a clear statement of scope.02
Reviewed
Maintainer reviewed
A code maintainer has publicly reviewed the stated integration or a defined part of it. Review alone does not make it an upstream feature.
Evidence: A linked review, issue, pull request, or statement describing what was examined.03
Upstream
Official support
The code project publicly adopts or supports the integration. The record states which versions and workflows that support covers.
Evidence: An upstream release, documentation, merged change, or explicit maintainer announcement. 03 / TESTED SCOPE
Validation status.
These labels describe the strongest published check for the stated examples and pinned code revision. They do not automatically cover every parameter or future release.
Prototype
A model or adapter exists. Its behavior is still being explored and the claimed examples have not reached a stronger check.
Settings parity
For a stated set of pinned examples, generated active native settings agree with reference inputs under documented comparison rules.
Build tested
The pinned source builds with the generated configuration in a documented environment. This does not assess simulation results.
Science validated
Representative solver results meet documented scientific comparisons and acceptance criteria for a defined scope.
ADD EVIDENCE, ADVANCE A RECORD
Help make a listing stronger.
Contribute a parameter model, review native settings, run a reproducible build, or document a scientific comparison. Each result can strengthen a specific claim.