Skip to content

Dimensional Analysis Table

Structured worksheet — instantiates Dimensional Consistency Check

A worksheet that lists every quantity with its units and base dimensions and tracks how they cancel through a formula, so no scale-dependent term is ever combined blindly.

Dimensional Analysis Table is the durable artifact that makes a dimensional check systematic and re-runnable: a table with one row per quantity — its symbol, its units, its reduction to base dimensions (mass, length, time, currency, count…), and any conversion applied — worked through the formula so the dimensions on the left-hand side must equal the dimensions on the right. Where a quick unit glance lives in someone's head, this puts the whole quantity structure on paper. Its defining feature is that it is a standing document: it is built once for an equation or a repeated calculation and kept, so the same check is available every time the formula is reused and the reasoning is visible to the next reader rather than re-improvised.

Example

An HVAC engineer is sizing the fan for a building's ventilation and inherits a formula for required air-mover power. She builds the table before trusting it. Each term gets a row: airflow in cubic metres per second (L³·T⁻¹), pressure rise in pascals (M·L⁻¹·T⁻²), efficiency as a pure ratio. Multiplying airflow by pressure, the length and time dimensions combine to M·L²·T⁻³ — which reduces to watts, exactly the dimension power should have. The table confirms the formula is dimensionally homogeneous before a single number is plugged in.[1]

The payoff comes a row later. A junior colleague had airflow entered in cubic feet per minute in one place and cubic metres per second in another. On the table the base dimensions still matched — both are L³·T⁻¹ — but the conversion column is empty, flagging that two different unit conventions were multiplied without reconciling. The table catches what a pure base-dimension check would miss, and because it is saved with its conversion column intact, the next engineer who reuses the formula inherits the audit rather than repeating the mistake.

How it works

  • One row per quantity. Symbol, plain-language meaning, units as written, reduction to base dimensions, and the conversion factor if any — every term named, including intermediates, so nothing enters the formula unlisted.
  • Carry dimensions through the operations. Multiply, divide, and cancel the dimensional expressions along the formula; the result's dimensions must match the quantity it claims to produce.
  • Keep the conversion column honest. Matching base dimensions is necessary but not sufficient; the table separately records that unit conventions were actually reconciled, not just dimensionally similar.
  • Retain it. The completed table is filed with the model or calculation, so the check travels with the formula.

Tuning parameters

  • Dimensional granularity — how far quantities are reduced: to named units, to SI base dimensions, or to a custom basis that includes things like currency or headcount. Finer bases catch subtler mismatches but take longer to build.
  • Intermediate coverage — whether only inputs and outputs get rows, or every intermediate expression too. Full coverage catches hidden-variable errors; input/output-only is faster.
  • Reuse scope — built for a single calculation, or as a reusable template for a family of formulas. Templating amortizes the effort across repeated use.
  • Formality — an informal scratch table versus a reviewed, version-controlled artifact attached to the model.

When it helps, and when it misleads

Its strength is systematic coverage and durability: it is the mechanism of choice when an equation is complex, reused, or handed between people, because it externalizes the whole dimensional argument where it can be reviewed and inherited rather than trusted.

Its limits are the limits of any table. It proves dimensional homogeneity, not correctness — a formula can be perfectly balanced dimensionally and still be the wrong formula, and it says nothing about whether the meaning behind matching units is the same. It also decays: kept beside a formula whose inputs later change convention, a stale table can lend false assurance. The discipline is to treat the table as a check on structure only, pair it with a meaning check for constructs that share units, and re-run it whenever the formula's inputs change.

How it implements the components

  • variable_list — the rows are the variable list: every quantity, intermediate, and denominator named so it can be checked.
  • unit_dimension_map — each row assigns the quantity its unit and base-dimension reduction; the table is the map made explicit.
  • consistency_test — carrying dimensions through the operations to a matching result is the formal test the table performs.
  • audit_trail — retained with its conversion column, the completed table is the record of what was checked and how.

It does not decide what to do when a mismatch appears beyond flagging it (the resolution belongs to Unit Conversion Workflow), nor judge whether the output magnitude is physically plausible (that is Engineering Equation Sanity Check); it establishes and records the structure.

  • Instantiates: Dimensional Consistency Check — the table is the archetype's most literal artifact, the quantity structure written down.
  • Sibling mechanisms: Unit Check · Engineering Equation Sanity Check · Cross-Scale Transfer Review · Dimensionless Ratio Construction · Finance / Accounting Unit Check · Model Input / Output Contract · Normalized Metric Design · Per-Capita or Per-Unit Conversion · Spreadsheet Unit Audit · Stock / Flow Separation Check · Unit Conversion Workflow

References

[1] The principle of dimensional homogeneity — every additive term in a physically meaningful equation must share the same dimensions — is the rule the table enforces. It is a necessary condition for a correct equation, never a sufficient one. ↩