test: onboard quad02 reaction reference

This commit is contained in:
NINI
2026-05-05 23:56:27 +09:00
parent 9741671f70
commit c47557885d
15 changed files with 597 additions and 24 deletions
+3 -1
View File
@@ -72,13 +72,15 @@ If a lower-precedence document needs to override a higher-precedence decision, u
- Require singular system diagnostics.
- Defer mesh quality diagnostics.
- Validate against stored reference artifacts under `../references/`; do not require Abaqus execution.
- Treat Abaqus `*.inp` files plus `*_displacements.csv` result files as the initial accepted reference artifact contract.
- Treat Abaqus `*.inp` files plus `*_displacements.csv` result files as the initial accepted displacement reference artifact contract.
- Treat Abaqus `*_reactionforces.csv` or `*_reactions.csv` files as reaction reference artifacts only after their RF/RM column mapping, tolerance, and pass/fail status are documented.
## Implementation Readiness Checklist
Before creating Phase 1 implementation steps:
- Use `../references/` as the accepted reference artifact folder.
- Use Abaqus `.inp` files plus solved `*_displacements.csv` files as the first automated displacement reference format.
- Use Abaqus RF/RM CSV files such as `*_reactionforces.csv` as the first reaction reference format when provided, but do not hide a node-wise RF mismatch by relaxing tolerances.
- Keep a compatibility note when a stored Abaqus reference input contains features outside the current Phase 1 parser subset.
- Use the current `MITC4_FORMULATION.md` as the Phase 1 MITC4 gate before implementing or reviewing element stiffness.
- Treat `U` and `RF` as the mandatory Phase 1 outputs; `S`, `E`, and `SF` require a later recovery-location decision.