NINI
33 lines
1.1 KiB
Markdown
33 lines
1.1 KiB
Markdown
---
|
|
name: fesa-results-schema
|
|
description: Design or review FESA HDF5 result outputs, step/frame/field/history layout, and reference comparison mapping.
|
|
---
|
|
|
|
# FESA Results Schema
|
|
|
|
Use this skill when result storage, HDF5 groups, field/history outputs, or reference comparison paths are involved.
|
|
|
|
## Read First
|
|
|
|
- `/AGENTS.md`
|
|
- `/PROGRESS.md`
|
|
- `/PLAN.md`
|
|
- `/docs/RESULTS_SCHEMA.md`
|
|
- `/docs/VERIFICATION_PLAN.md`
|
|
- `/docs/NUMERICAL_CONVENTIONS.md`
|
|
- `/docs/MITC4_FORMULATION.md`
|
|
|
|
## Workflow
|
|
|
|
1. Preserve the step/frame/field/history model.
|
|
2. Check entity type, component order, coordinate system, precision, units metadata, and sign convention for each field.
|
|
3. Distinguish full-vector results from reduced-vector solver internals.
|
|
4. Ensure `U` and `RF` are clear for Phase 1; flag unresolved `S`, `E`, and `SF` decisions.
|
|
5. When reference comparison is involved, map `references/*_displacements.csv` to HDF5 field output `U` using the documented Abaqus column names.
|
|
6. Keep HDF5 API usage behind result writer/adapters.
|
|
|
|
## Output
|
|
|
|
- Provide docs-ready schema deltas or review findings.
|
|
- Include reference comparison implications and tests needed.
|