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/requirements/linear-static-mitc4-shell.md
+2 -2
View File
@@ -201,8 +201,8 @@ workspace, so no exact filename, schema, units, generator, step/frame or row inv
asserted here. The bundle shall remain read-only when it becomes observable.
- **FESA-REQ-LSMITC4-065** — Reference Model shall inventory `reference/shell/` without creating, renaming, rewriting or repairing files and shall classify a missing/unobservable candidate as `needs-reference-artifacts` rather than fabricate its content.
- **FESA-REQ-LSMITC4-066** — A usable new reference bundle shall contain `model.inp`, `metadata.json` and `<model-id>_displacements.csv`, or shall receive an explicitly approved legacy-alias contract that records its exact existing filenames without rename.
- **FESA-REQ-LSMITC4-067** — Reference metadata shall record Abaqus generator/version, creation provenance, source element type, model/step/frame identity, user unit system, global coordinate convention, section/material/thickness data, CSV schema and tolerance policy.
- **FESA-REQ-LSMITC4-066** — A usable new reference bundle shall contain `model.inp` and `<model-id>_displacements.csv`, or shall receive an explicitly approved legacy-alias contract that records its exact existing filenames without rename; `metadata.json` is optional and its absence shall not make the bundle unusable.
- **FESA-REQ-LSMITC4-067** — The approved Reference Model Contract shall record Abaqus generator/version, creation provenance, source element type, model/step/frame identity, user unit system, global coordinate convention, section/material/thickness data, CSV schema and tolerance policy; if `metadata.json` exists, it shall be inventoried read-only and checked against that contract and the stored artifacts.
- **FESA-REQ-LSMITC4-068** — Artifact validation shall confirm an approved single `*STEP, *STATIC` model, expected `S4` or `S4R` source type, supported keyword subset, unique finite displacement rows and exact source-node/component identity before comparison.
- **FESA-REQ-LSMITC4-069** — End-to-end mapping evidence shall cover at least one `S4` input and at least one `S4R` input; the declared `reference/shell/` S4R model may satisfy only the S4R side after inventory validation, so separate S4 evidence remains required.
- **FESA-REQ-LSMITC4-070** — Reference verification shall compare FESA HDF5 global nodal displacement rows directly against Abaqus displacement CSV rows by model, step/frame, source node and component identity; a FESA-generated CSV view shall not become the authoritative comparison source.