Demonstrated, not asserted.
Software that prints safety-critical calculations should prove itself in public. This page documents how DeepMechanix is benchmarked against ASME’s own worked examples — the method, the results, and the re-run policy.
ASME asks for proof.
“…demonstrate that the computer program has the capability of producing acceptable calculations.”
— ASME certification and accreditation requirements
When design calculations come from a computer program, ASME requires the capability to be demonstrated — not assumed. We treat that demonstration as a publishing obligation: the benchmark, the method, and the numbers belong in public, where your checker and your Authorized Inspector can verify them.
The Code's own worked examples, run straight through.
ASME PTB-4 is the Section VIII Division 1 Example Problem Manual — published problems with published answers. We run them as written.
01 / Run
Each worked example from ASME PTB-4 — the Section VIII Division 1 Example Problem Manual — is modeled in DeepMechanix exactly as stated. Same geometry, same materials, same design conditions. No tuning, no selective inputs.
02 / Publish
Results go up side by side: PTB-4's value, DeepMechanix's value, and the delta, parameter by parameter. Disagreements get published and explained, not buried.
03 / Re-run
The full suite re-runs on every release and on every Code edition update. A passing run from last year proves nothing about today's build.
Side by side, by component class.
Tables stay empty until real benchmark numbers land. We don't fabricate deltas — an empty cell is more honest than an invented one.
Shells
| PTB-4 example | Parameter | PTB-4 result | DeepMechanix | Δ |
|---|---|---|---|---|
| Results publishing in progress — request the current suite | ||||
Heads
| PTB-4 example | Parameter | PTB-4 result | DeepMechanix | Δ |
|---|---|---|---|---|
| Results publishing in progress — request the current suite | ||||
Nozzle reinforcement
| PTB-4 example | Parameter | PTB-4 result | DeepMechanix | Δ |
|---|---|---|---|---|
| Results publishing in progress — request the current suite | ||||
Flanges
| PTB-4 example | Parameter | PTB-4 result | DeepMechanix | Δ |
|---|---|---|---|---|
| Results publishing in progress — request the current suite | ||||
MDMT
| PTB-4 example | Parameter | PTB-4 result | DeepMechanix | Δ |
|---|---|---|---|---|
| Results publishing in progress — request the current suite | ||||
Describe the design method in one paragraph.
Your ASME quality control manual must describe how design calculations are performed. Adapt this language to your system.
Adaptable text — edit to match your quality system
Design calculations for pressure vessels are performed using DeepMechanix, a computer program implementing the rules of ASME BPVC Section VIII, Division 1. Calculation reports show the governing formula, the substituted design values, the computed result, and the applicable Code paragraph for each check, permitting line-by-line verification by the design checker and review by the Authorized Inspector. The program’s capability of producing acceptable calculations is demonstrated by benchmarking against the worked examples of ASME PTB-4; the benchmark suite is re-run on each program release and on each Code edition update, and current results are available from the developer.
Validation, asked directly.
01What is ASME PTB-4?
ASME PTB-4 is the Section VIII Division 1 Example Problem Manual — worked design problems published by ASME with the arithmetic shown. Because the problems and answers are public, it is the natural benchmark for Division 1 design software: anyone can re-run the examples and check our numbers.
02When will the benchmark results be published?
Component class by component class, as each section of the suite completes. Until a table has real numbers, it stays empty — we do not fabricate deltas. Email us for the current state of the suite and we will send what exists today.
03How often does the suite re-run?
On every program release and on every Code edition update. Validation is a property of a specific build, not of the product in general, so the suite runs against the build you would actually use.
04What does my Authorized Inspector actually look at?
The Inspector verifies that the required design calculations are on file and reviews the report, not the software. DeepMechanix reports cite the governing Code paragraph next to every result, and the paragraph above gives your QC manual language describing the design method.