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

test: onboard quad02 reaction reference

Browse Source
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
Download Patch File Download Diff File Expand all files Collapse all files
docs/RESULTS_SCHEMA.md
+32 -2
View File
@@ -298,7 +298,37 @@ Rules:
- The comparator must require FESA `U` component labels `UX`, `UY`, `UZ`, `RX`, `RY`, `RZ` with `position = NODAL`, `entity_type = node`, and `basis = GLOBAL`.
- Duplicate FESA output node ids, duplicate CSV node labels, missing FESA nodes, missing CSV columns, and nonnumeric CSV values are comparison failures.
- The comparison report may be stored under `/referenceComparison`.
- Reaction CSV, stress CSV, or section force CSV formats must be documented before automated use.
Initial accepted reaction reference naming:
```text
references/<case_name>_reactionforces.csv
references/<case_name>_reactions.csv
```
`*_reactionforces.csv` and `*_reactions.csv` map to:
```text
/results/steps/<step>/frames/<frame>/fieldOutputs/RF
```
Required CSV columns:
| CSV Column | HDF5 Field Component |
|---|---|
| `Node Label` | `entity_ids` |
| `RF-RF1` | `RFX` |
| `RF-RF2` | `RFY` |
| `RF-RF3` | `RFZ` |
| `RM-RM1` | `RMX` |
| `RM-RM2` | `RMY` |
| `RM-RM3` | `RMZ` |
Rules:
- The comparator must require FESA `RF` component labels `RFX`, `RFY`, `RFZ`, `RMX`, `RMY`, `RMZ` with `position = NODAL`, `entity_type = node`, and `basis = GLOBAL`.
- The FESA `RF` field must be the full-vector reaction field recovered as `K_full * U_full - F_full`.
- Duplicate FESA output node ids, duplicate CSV node labels, missing FESA nodes, missing CSV columns, and nonnumeric CSV values are comparison failures.
- Stress CSV or section force CSV formats must be documented before automated use.
## Naming Rules
- Use stable ASCII group and dataset names.
@@ -318,4 +348,4 @@ For large models:
- Exact mandatory stress/strain/resultant output variables in Phase 1.
- Whether result files always mirror the model or only store output entity ids.
- Whether reference comparison results are stored in solver output files or separate reports.
- Exact naming and column contracts for non-displacement Abaqus CSV reference files.
- Exact naming and column contracts for stress, strain, and section-force Abaqus CSV reference files.