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

docs: use fixed MITC4 reference tolerance

Browse Source
This commit is contained in:
KOKO\Mimi
2026-08-13 10:06:45 +09:00
parent 8994ce93f8
commit f1be807e40
14 changed files with 110 additions and 80 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/reference-models/linear-static-mitc4-shell-reference-models.md
+9 -9
View File
@@ -80,26 +80,26 @@ zero-clamped and mismatched rows are not omitted, averaged, or synthesized.
## 5. Tolerance and decision rule
For each case and component `c` independently, using only finite Abaqus rows:
For every matched row:
```text
reference_scale_c = max(abs(abaqus_value_i))
tolerance_c = 1e-9 + 1e-6 * reference_scale_c
tolerance = 1.0e-5
absolute_error_i = abs(fesa_value_i - abaqus_value_i)
```
The `1e-9` floor is expressed in the model's user-consistent length unit for
`U1/U2/U3` and is dimensionless for `UR1/UR2/UR3`. A zero reference scale leaves only
the absolute floor; no alternate denominator is introduced.
The fixed `1.0e-5` value is expressed in the model's user-consistent length unit for
`U1/U2/U3` and is dimensionless for `UR1/UR2/UR3`. Neither a component reference scale
nor a row-specific denominator changes the value. Reference scale may be reported as
non-decision diagnostic information. The separate B33 mixed tolerance is unchanged.
- Every matched `U1/U2/U3` row must satisfy `absolute_error_i <= tolerance_c`.
- Every matched `U1/U2/U3` row must satisfy `absolute_error_i <= tolerance`.
Any U exceedance fails that case and the feature reference comparison.
- `UR1/UR2/UR3` uses the same formula. Every exceedance produces a deterministic
- `UR1/UR2/UR3` uses the same fixed value. Every exceedance produces a deterministic
warning containing the case, source row, component, error, and tolerance, but does
not change pass/fail.
The comparison report records every U/UR row decision, maximum absolute error,
component-scale normalized error, RMS error, vector-norm error, worst source
fixed-tolerance-normalized error, RMS error, vector-norm error, worst source
row/component, and every UR warning.
## 6. Coverage and handoff