Concept reference

Verification & Calibration

Solution verification, mesh convergence, sensitivity / UQ, and the disjointness invariant between calibration and validation.

1 min read

Solution verification

ADR 0020 freezes a SolutionVerificationRecord with gate, acceptance, and pass contracts. Verification is numerical — does the discretization converge? — separate from validation against physical reality.

Mesh convergence

ADR 0021 enforces the MeshConvergenceSeries: three monotonically refined meshes with matching QoI definitions. The platform computes GCI / Richardson extrapolation automatically; a single-mesh "converged" claim cannot publish.

Calibration ≠ validation

ADR 0022's disjointness invariant: data points used for calibration cannot also appear in validation. The ValidationCalibrationRecord tracks both sets; overlap is a typed verdict-invalidation, not a soft warning.

Sensitivity and UQ

ADR 0023 produces a SensitivityUQRecord with explicit applicability ranges. Whether you run Monte Carlo, polynomial chaos, or a deterministic perturbation sweep, the record carries the inputs, the sampling design, the QoI distributions, and the gate that says "this result is supported only inside this range."

Iteration studies

ADR 0024 covers design exploration — geometric sweeps, parametric optimization. The IterationStudyRecord carries acceptance/invalidation rules so a downstream report cannot cherry-pick an outlier without flagging the rest of the design space.

Was this page helpful?

Edit this page on GitHub

Search docs

Find pages across the SimPilot docs.