Skip to content
Sign in
Validation — how the results on this site are checked

Validation

Whether a calculator can be trusted is decided by what stands behind its answer, not by the answer itself. These reports work each calculation by hand from a published definition and set the result against what the tool returns, with every step shown.

What a report contains

Each report states what it covers, derives the expected values from primary sources, names the acceptance criterion, shows the working in full, and ends with what the exercise does not establish. The expected values are held apart from the calculation engine and are written from the sources rather than computed from the tool's own constants, because a tool compared against itself will always agree.

Coverage is counted rather than asserted. A report states how many of the things the tool offers it has actually derived, the build compares that count against the tool, and a mismatch fails the build. Adding a capability without validating it is therefore not possible.

Reports

7 of 7 calculators has a published report. The rest are listed so that the gap is visible; the work is proceeding one tool at a time and this page is the record of where it has reached.

Scope of the exercise

Validating a conversion is a different task from validating a physical model. The unit converter rests entirely on definitions, so its report can be complete: there is a finite list of units and every one of them is derived. The calculators that use nuclear data and physical models cannot be complete in that sense, and their reports will have to say what was compared, against which published values, and how far apart the two were. Where a figure on this site is a computed derivation rather than a copied table value, the derivation is described on the methods page.

None of this makes RadCalc a substitute for an accredited calibration or test, and the disclaimer says so in the terms that matter.