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.
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
| Property | Requirement type | Requirement |
|---|---|---|
| Content type | Always applies | requires=text; requires=tabular |
| Unit of analysis | Always applies | requires=claim |
| Variable types | Raises a warning | prefers=interval; prefers=ratio |
| Appraises source credibility | Applies in some cases | no |
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 material | A formula or calculation with units attached to every quantity. |
|---|---|
| Additional sources needed | none |
| 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 technique | Verification technique, runs in step 6 |
|---|---|
| Phase tag | validate |
| Other phase tags | none |
| Kind of finding | contradiction |
| Question answered | what |
| Strongest statement it supports | describe |
| Needs as input |
|
| Makes as output |
|
| Must exist first | None |
| Loop target | return 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.
| Stakes | Check | Person involved | Counts as a different method |
|---|---|---|---|
| exploratory | input validation | none | no |
| decision-informing | input validation | none | no |
| decision-informing | code execution for arithmetic | none | no |
| high-stakes | input validation | none | no |
| high-stakes | code execution for arithmetic | none | no |
| high-stakes | independent review | needed | no |
Failure modes and limits
| Model suitability | model plus code |
|---|---|
| Typical model failure | Treats a matching unit balance as proof of correctness, or overlooks mixed units such as per cent against percentage points. |
| Error sources | input data; data transformation |
| Certainty limits | A match shows only that units agree. Logic errors and wrong numerical factors remain unchecked. |
Related techniques
- pairs with TC1-27 Fermi estimation and order-of-magnitude checks (back-of-the-envelope estimate): an order-of-magnitude check catches numerical factors that a unit check cannot see
- pairs with TC1-18 Internal consistency check (term from earlier work): the consistency check covers contradictions between figures
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.