Correlated inputs in uncertainty evaluation
Root-sum-of-squares assumes independence. When two inputs move together, such as the same reference used twice, the combination needs a correlation term.
The familiar u_c² = Σ(c_i u_i)² holds only for uncorrelated inputs. When inputs share a source of variation, cross terms appear. Ignoring them can understate the uncertainty (positive correlation) or overstate it (negative correlation, as in a difference measurement with a common reference).
Where it shows up in temperature work
- Mapping studies: all loggers calibrated against the same reference share its error; the uncertainty of a difference between two loggers is smaller than naïve combination suggests, while the uncertainty of their common offset is not.
- Uncertainty of a mean of many sensors: the reference's contribution does not shrink with √n.
- Two measurements made with the same instrument minutes apart: drift and environment are largely common.
The GUM gives the full expression with covariance terms; in practice, identify shared sources and treat them separately from the independent ones.
The mapping case, worked
Twelve loggers are calibrated against the same reference thermometer, which carries U = 0.04 °C. Each logger has its own repeatability and resolution contributing u = 0.03 °C independently. Two questions get different answers, and the difference is entirely correlation.
| Question | How the reference behaves | Result |
|---|---|---|
| Is the coldest logger below 2.0 °C? | The shared reference error shifts every logger the same way; it does not cancel | u includes the full 0.02 °C reference term plus 0.03 °C own: u ≈ 0.036 °C |
| Is the gradient between the hottest and coldest position really 3 °C? | The shared error cancels in the difference | Only the independent terms remain: u ≈ 0.042 °C from the two loggers, reference contributes nothing |
Combining naïvely would get the second row wrong by including the reference twice, once for each logger, when its error is common to both and subtracts out. This is the useful direction of correlation: a shared reference makes differences between sensors better known than their absolute values, which is precisely what a mapping study is measuring.
When it works against you
The dangerous direction is a shared source appearing in several terms of a sum. If the same reference certificate is used to correct both the bath temperature and the unit under test in a model where the two add rather than subtract, the errors reinforce and the naïve root-sum-of-squares understates the uncertainty. Positive correlation between terms that add always understates; ignoring it produces a confident, too-small number.
Practical handling
- Identify shared sources first: one reference used twice, one readout, one ambient condition affecting several components, one certificate applied to several instruments.
- Where a shared source cancels — a difference between two things measured against it — drop it from the combination and say so in the budget.
- Where it reinforces, either add the covariance term from the GUM expression, or take the simple conservative route and add the correlated contributions linearly before combining the rest in quadrature.
- Restructure the model where you can. Writing the measurand as a difference rather than as two separate absolute values often makes the correlation disappear into the algebra instead of needing a covariance term.
- Monte Carlo handles correlation naturally: draw one value for the shared input per trial and use it everywhere it appears. That is often easier than the analytical covariance treatment.
The rule of thumb: if two inputs share a physical cause, they are correlated, and the question is only whether it matters. If they share a certificate, they certainly do.
Frequently asked questions
- Do I always need to compute covariances?
- No. Restructure the model so shared components appear once, then combine the rest as independent. That handles most practical cases.
References
- [1]JCGM 100:2008 — Guide to the expression of uncertainty in measurement (GUM)
General technical guidance written against the cited sources. It is not regulatory or legal advice and does not replace the applicable standard, guideline or a qualified reviewer's judgement.
Have a question on this topic?
Ask ValiTrac AI and see the evidence and calculation behind the answer.
Ask ValiTrac AIFree calculator: Uncertainty budget
Combine Type A and Type B components per the GUM: divisors by distribution, sensitivity coefficients, u_c, effective degrees of freedom and U at k = 2.
Open the calculatorMetrology on ValiTrac
Measurement science, traceability, uncertainty and technical evidence.
Ask a metrology questionRelated articles
Building an uncertainty budget step by step
Write the model, list the inputs, evaluate each as a standard uncertainty, apply sensitivity coefficients, combine in quadrature, expand with k. One table.
Sensitivity coefficients: how input uncertainties reach the result
A sensitivity coefficient converts an input's uncertainty into its effect on the result. For a direct temperature comparison it is 1; elsewhere, derive it.