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

modify docu

Browse Source
This commit is contained in:
김경종
2026-06-11 17:18:03 +09:00
parent c4f8f95d4b
commit 742f311be1
66 changed files with 3354 additions and 375 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/skills/fesa-reference-models/SKILL.md
+11 -10
View File
@@ -1,6 +1,6 @@
---
name: fesa-reference-models
description: Use when designing FESA reference model portfolios, Abaqus input artifact bundles, metadata provenance, required reference CSV artifacts, coverage matrices, and implementation-planning handoffs.
description: Use when designing FESA reference model portfolios, Abaqus input artifact bundles, metadata provenance, required reference HDF5 artifacts, deterministic CSV views, coverage matrices, and implementation-planning handoffs.
---
# FESA Reference Models
@@ -26,10 +26,11 @@ Read these first:
2. Build a model inventory: smoke, analytical, patch test, benchmark, regression, and negative/invalid-input models.
3. For each model, record `model_id`, purpose, verified requirements, analysis type, element type, material, boundary conditions, loads, expected quantities, tolerance, source, and status.
4. Define `references/<feature-id>/<model-id>/` artifact bundle requirements.
5. Require `model.inp`, `metadata.json`, `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv`, and `README.md` unless explicitly not applicable.
6. Define optional `strains.csv` and `energy_or_residual.csv` only when upstream acceptance criteria require them.
7. Define metadata provenance, units, coordinate system, output requests, artifact status, and limitations.
8. Build a Coverage Matrix mapping requirement id, model id, compared quantity, artifact file, tolerance, verification method, and status.
5. Require `model.inp`, `metadata.json`, `reference.h5`, deterministic CSV views under `csv/`, and `README.md` unless explicitly not applicable.
6. Define required CSV views `csv/displacements.csv`, `csv/reactions.csv`, `csv/element_forces.csv`, and `csv/stresses.csv` only as deterministic views of `reference.h5`.
7. Define optional `csv/strains.csv` and `csv/energy_or_residual.csv` only when upstream acceptance criteria require them.
8. Define metadata provenance, units, coordinate system, output requests, artifact status, and limitations.
9. Build a Coverage Matrix mapping requirement id, model id, compared quantity, authoritative HDF5 dataset, CSV view file, tolerance, verification method, and status.
## Output Contract
@@ -42,7 +43,7 @@ Produce or revise `docs/reference-models/<feature-id>-reference-models.md` with:
- Abaqus Input Requirements
- Artifact Bundle Contract
- Metadata JSON Contract
- Reference CSV Requirements
- Reference HDF5 and CSV View Requirements
- Coverage Matrix
- Artifact Acceptance Checklist
- Open Issues and Downstream Handoff
@@ -53,7 +54,7 @@ Produce or revise `docs/reference-models/<feature-id>-reference-models.md` with:
- Do not implement parsers.
- Do not design C++ APIs or file ownership.
- Do not run Abaqus, Nastran, or any reference solver.
- Do not generate reference CSVs.
- Do not generate reference HDF5 files or deterministic CSV views.
- Do not compare solver results.
- Do not approve release readiness.
@@ -61,9 +62,9 @@ Produce or revise `docs/reference-models/<feature-id>-reference-models.md` with:
- Every `must` requirement maps to at least one model and compared quantity.
- `model.inp` stays within the supported Abaqus keyword subset or records an open issue.
- `metadata.json` includes provenance, Abaqus version/source, units, coordinate system, tolerance, and CSV schema version.
- Missing required CSVs keep the model at `needs-reference-artifacts`.
- `metadata.json` includes provenance, Abaqus version/source, units, coordinate system, tolerance, HDF5 schema version, and CSV view schema version.
- Missing `reference.h5` or required deterministic CSV views keep the model at `needs-reference-artifacts`.
## Handoff
Send model order and tests that should fail first to Implementation Planning Agent. Send schema, matching, output location, and tolerance mapping to Reference Verification Agent. Send physical expectations to Physics Evaluation Agent.
Send model order and tests that should fail first to Implementation Planning Agent. Send HDF5 dataset paths, deterministic CSV view schemas, matching, output location, and tolerance mapping to Reference Verification Agent. Send physical expectations to Physics Evaluation Agent.