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

docs: align FESA agents with minimal reference cases

Browse Source
This commit is contained in:
KOKO\Mimi
2026-08-12 03:31:08 +09:00
parent 5c08f1cf83
commit 188bf31e44
27 changed files with 438 additions and 593 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/skills/fesa-io-contract/SKILL.md
+7 -4
View File
@@ -26,8 +26,10 @@ Read these first:
4. Define supported keywords such as `*NODE`, `*ELEMENT`, `*MATERIAL`, `*ELASTIC`, `*BOUNDARY`, `*CLOAD`, `*STEP`, `*OUTPUT`, `*NODE OUTPUT`, and `*ELEMENT OUTPUT` only when required.
5. Define Internal Model Contract at a semantic level without C++ APIs.
6. Define Output HDF5 Schema for authoritative solver output `results.h5`.
7. Define FESA HDF5 to Reference CSV Comparison Schema for normalized rows matched against Abaqus CSV files under `reference/<model-id>/`.
8. Define units, coordinate system, component naming, output location, step/frame identity, and ID matching rules.
7. Define only the FESA HDF5 projection and minimum source-ID/component mapping needed for
feature-declared blocking or warning-only CSV quantities.
8. Define solver HDF5 units, coordinates, component names, locations, and step/frame identity.
Do not require duplicated CSV metadata or a CSV schema version for a single-step final-frame case.
9. Define validation rules and open issues.
## Output Contract
@@ -40,7 +42,7 @@ Produce or revise `docs/io-definitions/<feature-id>-io.md` with:
- History Data Mapping
- Internal Model Contract
- Output HDF5 Schema
- FESA HDF5 to Reference CSV Comparison Schema
- FESA HDF5 to Reference CSV Comparison Mapping
- Validation Rules
- Downstream Handoff
@@ -57,7 +59,8 @@ Produce or revise `docs/io-definitions/<feature-id>-io.md` with:
- Every supported keyword has a documented purpose, required data, and unsupported-case behavior.
- HDF5 schema is the authoritative solver output contract and must carry schema version, step/frame identity, units, coordinate system, output location, and component naming.
- Reference CSV comparison row schema must define stable row ordering, ID fields, and component ordering for matching against Abaqus reference CSV.
- Reference comparison must define exact existing CSV paths, source-ID and component columns,
deterministic matching, and missing/extra/duplicate/nonfinite prechecks. Never match by row order alone.
- Unsupported Abaqus input is explicit: unsupported, ignored-with-warning, or requires user decision.
- The I/O contract is compatible with requirements, formulation, and reference comparison needs.