Part VI
Verification
E. Algorithm and software checks · Packaging and tracing results
Once the solver has an answer, can the answer be packaged so that each number says what it is, where it sits, and where it came from? This case takes the solved cantilever from the model-file case and builds a result record for it using the solver’s existing result vocabulary.
It checks software plumbing, not new mechanics. Only the load-vector values are traced to their source so far, and public export of the record is not covered.
1.Inputs.
Illustrative values, taken from no standard and chosen so the arithmetic can be followed by hand. Most do not describe a real pipe; read them in any consistent set of units.
| Quantity | Symbol | Value |
|---|---|---|
| Solved model | — | The cantilever of the model-file case |
| Load case | — | The single load case of that model |
2.Method.
No new mechanics is worked. The ten result values come from the hand calculation of the model-file case.
The reference sets out the trace each load-vector value must carry. The chain runs from a load record in the model file, through the intermediate solver input, to the solver’s nodal load contribution and on to the result value. Two load records, each with three steps, give six links per value.
3.Results.
| Quantity | Expected |
|---|---|
| Free-end displacement in Y | −0.04533333 m |
| Free-end rotation about Z | −0.01466667 rad |
| Load vector, anchored node, Uy | −6.0 N |
| Load vector, anchored node, Rz | −4.666667 N·m |
| Load vector, free node, Uy | −6.0 N |
| Load vector, free node, Rz | 4.666667 N·m |
| Anchor reaction, Uy | 12.0 N |
| Anchor reaction, Rz | 24.0 N·m |
| Midspan shear | 4.0 N |
| Midspan bending moment | 4.0 N·m |
| Trace links per load-vector value | 6 |
| Diagnostics in the record | 1, informational |
| Blocking findings from the result check | 0 |
The tests check that:
- The record holds exactly ten result values, with the expected identifiers.
- It carries one informational diagnostic, and the result checker finds no blocking problems.
- It refers to the model and load case it came from, and carries the standard review flags.
- Each of the four load-vector values carries a trace built at run time, and one of them is checked for its six links end to end.
- The anchor reaction force and moment match the hand values.
What it shows. Checks how the program reads, records and passes on a model, not the mechanics.
Path exercised. The benchmark calls the solver’s components directly: elements, loads, frame solver and stress recovery. It does not go through the program’s own model-to-solve path.
Agreement. Each computed value must match the reference within an absolute difference of 1.0 × 10−9 in the case’s own units; counts and structural outcomes must match exactly. Long values are shown here to seven significant figures; the tests compare the full values in the record.
4.Run it yourself.
cd projects/chirality-piping cargo test --manifest-path validation/benchmarks/mechanics/Cargo.toml tp_phys_015a_canonical_payload_builds_result_boundary_evidence
Hand calculation:
validation/hand_calcs/mechanics/tp_phys_015a_canonical_solve_result_envelope.md.
Test record, with the recorded run of 2026-07-10:
mech-tp-phys-015-canonical-solve-result-envelope.md.