SWBPIPE · The open manual
Part V · Validation ElsewhereV–1

Part V

Validation Elsewhere

A. Design here, validate there

SWBPIPE helps readers develop a design: route the line, arrange supports, try alternatives and understand the behavior. It does not judge code compliance or vouch for its results. When the design needs validation, it goes to the program your industry accepts. The code check is made there under your engineer’s judgment.

One seat of the accepted program can support validation of work developed by several designers. Current .mbf output is a bounded interchange smoke subset, not a complete or qualified transfer. Target version, record-family coverage and direct stable-ID carrying remain open. Other export packages also have their own bounds.

Part V · Validation ElsewhereV–2

B. The export today

File > Export MBF and File > Import MBF now provide native review, save and import for a declared subset. Export writes an SI pilot model and companion identity file after review and an explicit local-private choice. Import reads bounded SI and English forms, requires a material-provenance declaration, shows losses and assumptions, and adopts an admitted model through the normal open/unsaved-changes guard. Imported models start unsaved.

A bound import verifies the companion file against the MBF bytes and the regenerated writer output. It restores the identities the pair preserves; designated-source checks can establish the stated identity set, not equivalence of the entire model. Edited or externally rewritten files have an unbound interpretation and stricter source-dependent refusals. The writer’s subset still excludes tees, rigid-family components, nonlinear supports, hangers and other unsupported families. Combinations are omitted and disclosed; some newer combination forms block export.

Invented subset round-trip checks are implemented. Complete reference-system coverage and the required round trip through the actual desktop build remain unestablished. Target-version and record-family questions remain open. A saved or imported pair establishes no receiving-program acceptance or comparison result. Model transfer reads no solve result and has separate privacy, loss, size and memory gates. An unknown export-save outcome still blocks another export until reload or restart. See interchange scope.

1.Other exports.

Other surfaces prepare a straight-run PCF subset, native packages, CSV or JSON result exports, centerline geometry and local-detail handoffs. These packages have different input, loss and eligibility conditions. A package’s presence does not establish target compatibility or professional validation.

Current exact-route pressure-2 and pressure-source-1 results can reach desktop outputs including: result JSON, stress-neutral JSON and user rule checks. The native reader must admit the source and numerical standing. Pressure-source results with load/reference states remain ineligible; ordinary pressure-2 load/reference-state results can qualify. Eligible current results on both routes can produce local-private reports and packages. Report composition and a separately confirmed shareable-package action are implemented, with numerical-standing, privacy and size restrictions; readable solved exact-route results may render with ineligible standing stated while their package save remains refused. See report limits. Results and comparison tables also offer local-private CSV export, separate from the stress-neutral interchange file. PCF and other model-transfer packages retain their separate exact-route restrictions. MBF model export has its own admission, independent of result-output policy. Byte-exact files for other programs, including stress-neutral CSV, are withheld while session values are private. Stored or copied source-result bytes alone do not supply the required live invocation binding (Status).

The separate retained-precision successor method remains dormant and is outside the v1.0 target. Saved or copied result bytes do not supply the live native capture required by prepared successor policies. Prepared result JSON and stress-neutral policies admit a successor only with eligible standing and a live native capture. These preserved policies do not make it a current application feature. Other successor output surfaces remain refused.

2.How the export will be checked.

A complete interchange check must compare three representations: the defined problem, a model built by hand in the receiving program, and the exported model. Each feature must be identified as exact, approximate, omitted or untested. A file that opens does not establish faithful transfer. Current pilot-subset checks screen package structure and disclosed losses; they do not establish complete target execution or equivalence (Part VI).

Part V · Validation ElsewhereV–3

C. What changes when you validate

Equivalent models can give similar movements and loads in two programs, but their results need not be identical. Differences can arise from each program’s assumptions and implementation. Understanding those choices helps reconcile the results.

Compare the models before their results. Compare geometry, sizes, materials, support types and directions, and load cases, row by row.

SubjectWhat to expect
Shear deformationExact-contract straight members select Timoshenko or Euler–Bernoulli; new authoring defaults to Timoshenko. Pressure-free straights offer opt-in Timoshenko; their default and all realized arcs remain Euler–Bernoulli. Compare the selected beam theory and shear factor with the receiving model. Omitting shear flexibility can increase stiffness and loads in short, heavy legs.
BendsThe validating program takes k and the SIFs from the code you select. Enter the same values here, or expect differences at every elbow. Today the ordinary route and pressure contract 3.0.0 support explicit curved_bend_macro_element mode with entered k; legacy mechanics_geometry_only uses the chord. Supported arc maxima now carry a declared enclosure; missing bounds and incomplete coverage remain withheld (Status).
PressureThe current exact contract is v3; v2 and legacy pressure are retired. V3 admits realized bends with entered k and the bounded joint pressure law with optional elastic tie rods. Explicit regions, closure transfer, E/ν and pressure basis are required. Compare represented pressure strain and thrust effects; Bourdon opening and pressure-dependent flexibility remain excluded (Status).
Section basisThe exact route uses nominal wall for stiffness and pipe-metal mass, reduced wall for the pressure bore, and separately identified nominal and reduced stress rows. Match the intended basis in the receiving model. The pressure-free route retains one effective-wall basis (Status).
ModulusThe code range uses its required reference modulus; hot reactions use the appropriate hot material basis. Model 0.9.0 records the selected material and thermal states explicitly. Solve comparable physical and material states before comparing results. Mixed-modulus mechanics combinations are withheld.
Springs and hangersA validating program may design hangers, select them from catalogs and apply preload. Compare only after entering the same rate and cold load, and note that SWBPIPE does not yet apply the preload (Status).
Friction and nonlinear supportsFriction results depend on the solution path and on how each program treats the sustained case. Compare runs without friction first.
Code stressesThe validating program computes the sustained stress, the displacement stress range and the occasional stresses, and compares them with allowables. SWBPIPE computes none of them.

1.A reconciliation order.

  • Weight only, with every support rigid: support loads should agree closely.
  • Thermal only, without friction and with nonlinear supports held in one state: movements and anchor loads should agree within the effect of shear deformation and bend modeling.
  • Then add pressure, springs, friction and nonlinear supports one at a time. Explain each change in the difference before adding the next.

Where the programs still disagree, the model in the validating program is the design basis under your engineer’s judgment.

Contents · Part IV · Part VI · The program: swbpipe.com · MIT license