baram2584/FESADev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: make reference metadata optional

Browse Source
This commit is contained in:
KOKO\Mimi
2026-08-12 02:22:01 +09:00
parent f28dbd7e42
commit 2bd297d84b
24 changed files with 127 additions and 95 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/io-definitions/linear-static-mitc4-shell-io.md
+10 -9
View File
@@ -460,7 +460,7 @@ solver output nor a reference artifact.
### 7.1 S4/S4R portfolio separation
- S4 and S4R use distinct `model_id`, input, metadata, and CSV bundles.
- S4 and S4R use distinct `model_id`, input, Reference Model Contract records, and CSV bundles. An optional `metadata.json` does not define bundle identity.
- FESA maps both source types to `FESA-MITC4`, but Abaqus S4 and S4R values are not
expected to equal each other on a finite mesh.
- Reference comparison always compares one FESA run with Abaqus rows generated from
@@ -484,7 +484,7 @@ The files were introduced by source commit
zero-clamped, normalized, or repaired. A hash mismatch is
`needs-reference-artifacts`, not permission to restore or change the bundle.
The alias is `recognized-legacy-alias-needs-reference-metadata`. Before numerical
The alias is `recognized-legacy-alias-needs-reference-contract`. Before numerical
comparison, the Reference Model contract must supply or approve externally:
- generation owner/date and exact provenance;
@@ -495,8 +495,8 @@ comparison, the Reference Model contract must supply or approve externally:
- CSV schema version and tolerance policy.
CSV lacks explicit step/frame/unit/coordinate columns. They map to
`(Step-1,frame 0)`, global Cartesian, and documented units if and only if approved
metadata confirms that exact interpretation. Absence or conflict is a
`(Step-1,frame 0)`, global Cartesian, and documented units if and only if the approved
Reference Model Contract confirms that exact interpretation. Missing contract data or a conflict is a
schema/provenance failure; I/O Definition does not infer values.
### 7.3 Separate canonical S4R bundle
@@ -506,14 +506,15 @@ At least one S4R reference bundle is still required:
```text
reference/<s4r-model-id>/
model.inp
metadata.json
<s4r-model-id>_displacements.csv
```
`model.inp` must contain the approved subset and `TYPE=S4R`. Metadata records
generator/version/provenance, unit system, coordinate system, model/step/frame,
material/section/thickness, source element type, schema version, and tolerance
policy. Optional reaction/stress artifacts remain nonblocking evidence.
`model.inp` must contain the approved subset and `TYPE=S4R`. The approved Reference
Model Contract records generator/version/provenance, unit system, coordinate system,
model/step/frame, material/section/thickness, source element type, schema version, and
tolerance policy. `metadata.json` is optional; if present, it is read-only supplementary
evidence and every overlapping field is checked against the contract and stored artifacts.
Optional reaction/stress artifacts remain nonblocking evidence.
`<s4r-model-id>` is a Reference Model-owned schema variable, not an unresolved
filename placeholder in this I/O contract.