SWBPIPE · The open manual
Part VI · VerificationVI–E25

Part VI

Verification

E. Algorithm and software checks  ·  Zero reaction means lift-off

A lift-off support is in contact at the second iteration. Trial displacement is 0.04 mm, and trial reaction is exactly 0.0 N. Does zero reaction retain contact? This case specifies the boundary behavior. It classifies one trial state without solving a frame.

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

The current product limits active-set solves to four iterations. Current mechanics combinations with nonlinear supports are withheld. These recorded transitions and free-degree residuals do not establish general equilibrium or convergence for other models.

This test classifies a supplied trial state without solving a frame. Its iteration inputs are local to that classification test and do not change the current product iteration limit.

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
Iteration—2
Maximum iterations—6
Active-set residual tolerance—0.0 (count)
Trial displacementu0.04 mm
Trial reactionR0.0 N
Prior state—active (in contact)

2.Method.

This case treats zero trial reaction as loss of contact, so the support releases. One support changes state. The active-set residual counts changed supports, so it is nonzero and the step is not yet converged.

3.Results.

Expected outcome of the step
QuantityExpected
Trial reaction0.0 N
Trial displacement0.04 mm
State after the stepinactive (lifted off)
Convergedfalse

The case record describes these checks:

  • The support’s new state is inactive, and it is the only support reported as changed.
  • The step is reported as not converged, with a warning rather than a failure.
  • Every input and expected value carries an explicit unit, and the case’s source note exists. This is a bookkeeping check, not a mechanics check.

What it shows. Compares final support states, the iteration count, and force balance. It does not compare movements or reactions with a hand calculation.

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. No numerical tolerance band applies. The tests require the exact expected support state, changed-support count and convergence flag. Nothing is compared within a margin. Long values are shown here to seven significant figures; the tests compare the full values in the record.

For the student

Exactly zero is the boundary for this sign test. The reference treats zero reaction as loss of contact. The case requires that specific choice rather than leaving the boundary undefined.

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/nonlinear/Cargo.toml fixtures_are_public_original_and_unit_aware
cargo test --manifest-path validation/benchmarks/nonlinear/Cargo.toml active_set_gap_lift_off_and_friction_outcomes_are_deterministic

Hand calculation: validation/hand_calcs/nonlinear/lift_off.md. Test record, with the recorded run of 2026-07-10: nl-lift-off-original.md.

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