JSON, CSV/VTU, and selected HDF5 paths preserve different output fields and provenance contracts.
01 Model and scope
A result format is a serialization contract: it determines which fields, identities and diagnostics survive export. Reproducibility requires the result to retain enough model/source identity and solver metadata; file support alone does not imply restart support.
Route assumptions and calculation checks
- The mixed TET4/WEDGE6/HEX8 HDF5 result path is experimental-bounded; it is not general restart or parallel-HDF5 support.
- Result digests, source identity, mesh identity, and solver diagnostics should travel with displayed fields.
- A screenshot or plotted mode shape is not a reproducible numerical record by itself.
Useful foundations and prerequisites
02 Essential equations and symbols
This sheet records a scope or execution boundary. Its detailed steps explain the relevant conditions.
Definitions and conventions
- JSON / CSV / VTU / HDF5
- Output containers with different field and metadata capabilities.
- mesh identity
- Identifier or digest for the discretized model.
- source identity
- Release/commit identity for the executed code.
- restart
- A separate capability from writing result files.
03 Step by step derivation
Follow the assumptions, equations and discrete operations in order. The full explanation stays visible.
1 · Treat each format as a serialization contract
JSON, CSV/VTU, and selected HDF5 paths retain different combinations of mesh, field, metadata, and diagnostics. Export success means only that the selected writer produced a file; it does not mean every result field or material state was preserved.
2 · Carry the provenance needed to reproduce a claim
Tie displayed results to the input mesh, source release/commit, route settings, solver outcome, and evidence record. A plot or screenshot is a view of the result, not a substitute for the machine-readable values and metadata behind it.
3 · Do not infer restart from export
Restart requires a separately defined checkpoint schema that serializes all required accepted history and restores it consistently. The bounded mixed TET4/WEDGE6/HEX8 HDF5 output path is not general restart or parallel-HDF5 support; consult its exact capability and verification records.
04 Algorithm and implementation
This sheet provides explanatory references rather than an inline source excerpt. Use the labeled sources to inspect the precise boundary.
05 Verification and limitations
SCHEMA- AND ROUTE-DEPENDENT
The formulation and its explanatory checks do not by themselves establish a qualified application domain. Consult the capability matrix and the applicable recorded case.