startthat.work home

TC1-28 Dimensional and unit checks

Checks that both sides of a relation have the same units and produces a unit balance in which a mismatch flags an error in the derivation.

Trace cause and test claimsEvidence: DocumentedVerification technique, runs in step 6Strongest statement: describe

What it does

Checks that both sides of a relation have the same units. Artefact: a unit balance; a mismatch indicates an error in the derivation.

When to use it

Use when a formula or calculation has been produced and you want to catch errors in its units before relying on the number.

When it does not fit

A match is read as proof; numerical factors are invisible to the check.

Result format

The result is a table with one row per relation, giving the units on each side and the unit balance for the relation. It lists any mismatch as an error in the derivation, and says where the mismatch occurs.

Requirements on the material

PropertyRequirement typeRequirement
Content typeAlways appliesrequires=text; requires=tabular
Unit of analysisAlways appliesrequires=claim
Variable typesRaises a warningprefers=interval; prefers=ratio
Appraises source credibilityApplies in some casesno

Not restricted on: Structure, Time structure, How the sample was chosen, Level of detail available, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.

Minimum materialA formula or calculation with units attached to every quantity.
Additional sources needednone
Not for (rules)none
Not for (text)Misused when a match is read as proof. Numerical factors are invisible to the check.

Choosing and ordering

Kind of techniqueVerification technique, runs in step 6
Phase tagvalidate
Other phase tagsnone
Kind of findingcontradiction
Question answeredwhat
Strongest statement it supportsdescribe
Needs as input
Makes as output
Must exist firstNone
Loop targetreturn to analyse

Library checks by stakes

Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: deterministic.

StakesCheckPerson involvedCounts as a different method
exploratoryinput validationnoneno
decision-informinginput validationnoneno
decision-informingcode execution for arithmeticnoneno
high-stakesinput validationnoneno
high-stakescode execution for arithmeticnoneno
high-stakesindependent reviewneededno

Failure modes and limits

Model suitabilitymodel plus code
Typical model failureTreats a matching unit balance as proof of correctness, or overlooks mixed units such as per cent against percentage points.
Error sourcesinput data; data transformation
Certainty limitsA match shows only that units agree. Logic errors and wrong numerical factors remain unchecked.

Evidence and tag basis

Documented. Described on an encyclopaedia page. (Wikipedia, Dimensional analysis)

Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.