AUTONEST VCDesign principles · Verification

No program calculates infinity

2026-09-11 · 6 min read

Computers cannot handle infinity. Integers have an end, and so do the digits after the decimal point. So every program has boundaries. There are no exceptions. The difference lies somewhere else — whether those boundaries were declared, and whether everything inside them was actually tested.

Every value that could be entered — no end to it the range we answer for all of this has been run no answer out here no answer out here either
Fix the boundary and the boundary becomes the test range

Past the boundary, a program still gives you an answer

Having boundaries is not the problem in itself. The real problem is that a program does not stop when you cross them. Enter a value outside the range and no error appears. A number simply comes out.

That number does not arrive labelled "this region was never tested". Once it is printed in the report it looks exactly like a verified value. Convincing, down to the decimals.

Anyone spots a blank. Nobody looks twice at a plausible number.

In ordinary office software this ends as an inconvenience. In pressure vessels that number becomes plate thickness, and that plate stands on site under pressure. Finding out afterwards that "it was an untested region" is far too late.


So the range was fixed first

Before any calculation starts, AUTONEST VC holds an allowed range for each input field. A value outside the range is not filtered out mid-calculation — it cannot be entered in the first place.

InputAllowed rangeWhy this range
Length / inside diameter ratio0.5 – 5Outside this, shapes that do not realistically occur in fabrication or transport
Working volume ratio50 – 80 %The band where headroom above the liquid level makes sense
Default thickness3 – 50 mmWhat can actually be obtained as stock plate
Flange thickness8 – 100 mmSame
Size optimisation span1 – 10 %The range that can be swept while holding the volume
Stock-plate matching margin1 – 200 mmA realistic allowance for snapping to plate sizes
Mode selectionFrom a fixed list onlyChosen from a list rather than typed freely

These numbers are not preferences. They are a declaration that nothing outside them was tested. And in an untested band, not answering is the right thing to do.

Fix the range and it becomes the test range

This is the heart of it. The real reason for drawing boundaries is not to restrict the user. It is that without a boundary, "we tested all of it" cannot mean anything.

If the input is infinite, verification becomes sampling. Try a few values, they work, so it is probably fine — that is the ceiling. If the input is finite the story changes. The minimum, middle and maximum of each field can actually be run, and vessel types can be crossed with calculation modes. Because there is an end, you can go to the end.

So our verification runs like this.

What giving up infinity buys — being able to say "everything we answer for has actually been run".

The product itself has a boundary too

This is not only about input values. A line is drawn around the territory the program covers as well.

AUTONEST VC covers design pressure up to 0.99 MPa. Above that is a region where the law requires output from separately designated programs. Extending the formulas would not be hard in itself, but extending them would not make our output usable there. Which means it is not ours to answer.

The code applied is the “Standard for Inspection and Inspection Exemption of Heat-Using Equipment” (unofficial English translation; MCEE Notice No. 2025-61, Korea, partially amended 18 Dec 2025) (same content as the former MOTIE notice; only the ministry name changed), and the calculation basis is printed on the output as it is — a reviewer has to be able to trace which clause of which code produced this thickness.

Inside the range too, what does not hold is said not to hold

Drawing boundaries and being honest inside them are two different things. Both are needed.


To sum up

Whether a tool can answer "how far does it go" with numbers is what separates an honest one.

If the boundary is not declaredIf the range is fixed first
Nobody knows how far it was tested.
Numbers come out beyond the range, and those numbers are indistinguishable from verified ones.
You learn there was a boundary only after something goes wrong.
The test range is settled.
The inside can be run to the end, and "all of it was checked" can be said.
Nothing is answered outside, so every number that appears is from a tested band.

"It handles anything" sounds broad, but it is closer to not saying how far you checked. We chose the other side. Keep the covered range narrow, and leave no square of it untouched.

Infinity cannot be calculated. One finite region, though, can be answered for all the way.

Check how far it goes, first.
The input ranges and the calculation basis are both printed on the output. See AUTONEST VC → What we left manual on purpose →