SWBPIPE · The open manual
Part VI · VerificationVI–E4

Part VI

Verification

E. Algorithm and software checks  ·  Packaging and tracing results

Can a result record identify each number, its location and its source? This case uses the solved cantilever from the model-file case. It builds a result record with the solver result vocabulary.

The case tests result packaging, with no new mechanics. Only load-vector values have source traces in this test. This test does not cover public export of the record.

This page preserves a recorded benchmark and its expected values. The dated run below is not a new run of the current product.

This benchmark builds a result record inside its test crate. The current native Rust CLI offers sparse_interactive and dense_scrutiny solve modes and an export-results command. That separate implementation does not extend the scope of this recorded test or establish current desktop report availability.

The solved cantilever enters a result record with identified values. The case tests the trace from load values to their sources. w P L THE SOLVED CANTILEVER WHOSE RESULTS ARE PACKAGED
Fig. VI–E4.—Packaging and tracing results

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.

QuantitySymbolValue
Solved model—The cantilever of the model-file case
Load case—The single load case of that model

2.Method.

No new mechanics is calculated. The ten result values come from the hand calculation for the model-file case.

The reference defines the required trace for each load-vector value. The trace starts at a load record in the model file and passes through intermediate solver input. It then reaches the nodal load contribution and the result value. Two load records with three steps each give six links per value.

3.Results.

Result values carried and record structure
QuantityExpected
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, Rz4.666667 N·m
Anchor reaction, Uy12.0 N
Anchor reaction, Rz24.0 N·m
Midspan shear4.0 N
Midspan bending moment4.0 N·m
Trace links per load-vector value6
Diagnostics in the record1, informational
Blocking findings from the result check0

The case record describes these checks:

  • 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. One trace is tested through all six links.
  • The anchor reaction force and moment match the hand values.

What it shows. Assesses how the program reads, records, and transfers a model. It does not assess mechanics.

Path exercised. Validation-local result assembly. This benchmark does not exercise public export.

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.Recorded command.

This command belongs to the linked case record and its recorded execution path. This website update did not rerun it. A historical command or result does not establish current product support.

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.

Contents · Part VI · The program: swbpipe.com · MIT licence