<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Precision Archives - SignificantFiguresCalculator</title>
	<atom:link href="https://significantfigurescalculator.com/category/precision/feed/" rel="self" type="application/rss+xml" />
	<link>https://significantfigurescalculator.com/category/precision/</link>
	<description>Every digit, justified.</description>
	<lastBuildDate>Fri, 14 Aug 2026 03:24:12 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.4</generator>

<image>
	<url>https://significantfigurescalculator.com/wp-content/uploads/2026/08/cropped-dd6d33a5-a65a-4d8d-b33e-8b6f5639fddd-150x150.png</url>
	<title>Precision Archives - SignificantFiguresCalculator</title>
	<link>https://significantfigurescalculator.com/category/precision/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Error Propagation: How Uncertainty Moves Through a Calculation</title>
		<link>https://significantfigurescalculator.com/precision/error-propagation-uncertainty-calculation/</link>
					<comments>https://significantfigurescalculator.com/precision/error-propagation-uncertainty-calculation/#respond</comments>
		
		<dc:creator><![CDATA[Tommy C. Moran]]></dc:creator>
		<pubDate>Tue, 11 Aug 2026 00:22:43 +0000</pubDate>
				<category><![CDATA[Error Propagation]]></category>
		<category><![CDATA[Precision]]></category>
		<category><![CDATA[GUM]]></category>
		<category><![CDATA[metrology]]></category>
		<category><![CDATA[significant figures]]></category>
		<category><![CDATA[uncertainty]]></category>
		<guid isPermaLink="false">http://significantfigurescalculator.test/2026/08/11/error-propagation-uncertainty-calculation/</guid>

					<description><![CDATA[<p>Learn the rules for propagating uncertainty through addition, subtraction, multiplication, division, and powers, with worked examples, common pitfalls, and standards citations from GUM, ISO, and ASTM.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/error-propagation-uncertainty-calculation/">Error Propagation: How Uncertainty Moves Through a Calculation</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><strong>Error propagation is how the uncertainty in your measured inputs combines into the uncertainty of a calculated result — and there are two genuinely different, both legitimate, ways to combine them.</strong> The simple method (taught in most intro classes) adds uncertainties directly: absolute uncertainties for addition/subtraction, relative (percentage) uncertainties for multiplication/division. The rigorous method — the one the international measurement standard actually specifies — combines them in <em>quadrature</em> (square root of the sum of squares) instead of simple addition, and it always gives a smaller, more realistic number. Neither is wrong; they answer slightly different questions.</p>
<p>This page picks up directly where <a href="https://significantfigurescalculator.com/category/precision/accuracy-vs-precision/">Accuracy, Precision, and Uncertainty</a> left off. That page established that <em>random</em> error is what uncertainty describes, and that it behaves statistically rather than as a fixed offset. This page is about what happens when you calculate with several such uncertain values at once — add them, multiply them, raise them to a power — and need to know how uncertain the <em>result</em> is. It also closes a loop that&#8217;s been open since <a href="https://significantfigurescalculator.com/significant-figures/">our sig figs guide</a>: the addition and multiplication rules taught there (match decimal places; match sig fig count) are not arbitrary. They&#8217;re a simplified, digit-counting shortcut for exactly the calculation this page does properly, with real numbers. Example 4 below shows the two converging.</p>
<blockquote><p>&nbsp;</p></blockquote>
<h2 id="two-methods-not-one">Two Methods, Not One</h2>
<p><strong>The simple (worst-case) method.</strong></p>
<ul>
<li>Addition and subtraction: <strong>add the absolute uncertainties.</strong> If y = x₁ + x₂ (or x₁ − x₂), then u(y) = u(x₁) + u(x₂).</li>
<li>Multiplication and division: <strong>add the relative (percentage) uncertainties.</strong> If y = x₁ × x₂ (or x₁ ÷ x₂), then u(y)/y = u(x₁)/x₁ + u(x₂)/x₂.</li>
</ul>
<p>This method assumes the worst case: every input error pointed in the least favorable direction at once. It&#8217;s easy to compute by hand, which is why it&#8217;s what most intro science courses teach — but it&#8217;s deliberately pessimistic.</p>
<p><strong>The quadrature method (the GUM&#8217;s actual method).</strong></p>
<ul>
<li>Addition and subtraction: <strong>combine absolute uncertainties in quadrature.</strong> u(y) = √[u(x₁)² + u(x₂)²].</li>
<li>Multiplication and division: <strong>combine relative uncertainties in quadrature.</strong> u(y)/y = √[(u(x₁)/x₁)² + (u(x₂)/x₂)²].</li>
</ul>
<p>This is what the international measurement standard — the GUM (JCGM 100:2008) — actually specifies, under the name <strong>the law of propagation of uncertainty</strong>. It reflects a real statistical fact: if two error sources are genuinely independent, it&#8217;s very unlikely both land at their worst possible value on the same measurement, so the realistic combined uncertainty is smaller than the simple sum.</p>
<p><strong>Quadrature is always smaller than or equal to simple addition.</strong> For any two non-negative numbers a and b, √(a² + b²) ≤ a + b, with equality only when one of them is zero. This isn&#8217;t a coincidence specific to uncertainty — it&#8217;s the same geometric fact that makes the diagonal of a rectangle shorter than the sum of its two sides. Every example below demonstrates it numerically.</p>
<p><strong>Powers.</strong> If y = xⁿ, the relative uncertainty scales directly with the power: u(y)/y = |n| · u(x)/x. Squaring a value with 2% relative uncertainty gives a result with 4% relative uncertainty; cubing it gives 6%.</p>
<p><strong>Where this formula actually comes from.</strong> The GUM derives both versions from one general formula, for y = f(x₁, x₂, …, xₙ) with independent inputs: uc²(y) = Σᵢ (∂f/∂xᵢ)² · u²(xᵢ) — the sum of each input&#8217;s uncertainty, weighted by how sensitively the result responds to that input. This is a <strong>first-order Taylor series approximation</strong> of the function f, which is why it works cleanly for the simple operations covered here but can break down for strongly nonlinear functions or unusually large uncertainties — in those harder cases, the GUM&#8217;s own supplementary guide (JCGM 101:2008) recommends a Monte Carlo simulation instead of the direct formula.</p>
<p><strong>When inputs aren&#8217;t independent.</strong> Everything above assumes the input uncertainties come from unrelated sources. If two measurements share a common cause of error — the same miscalibrated instrument used for both, for instance — the quadrature formula on its own will <em>underestimate</em> the true combined uncertainty, and a covariance term (GUM Section 5.2) has to be added. This is a real caveat, not a footnote: shared error sources are common in practice, and this is exactly the setting where naive quadrature gives a falsely reassuring answer.</p>
<p><strong>The connection back to significant figures.</strong> <a href="https://significantfigurescalculator.com/significant-figures/">Our sig figs guide</a> rounds a sum to the fewest decimal places among its terms, and a product to the fewest significant figures. That&#8217;s precisely a crude, discrete version of the simple method above — &#8220;the least precise input limits the result&#8221; — without ever calculating an actual numeric uncertainty. Example 4 makes this explicit.</p>
<hr />
<h2 id="worked-examples">Worked Examples</h2>
<h3 id="example-1-addition-simple-vs-quadrature">Example 1 — Addition: simple vs. quadrature</h3>
<p><strong>Values:</strong> x₁ = 12.5 ± 0.3, x₂ = 8.2 ± 0.2. Sum = 20.7.</p>
<p><em>Simple method:</em> u(sum) = 0.3 + 0.2 = <strong>0.5</strong> → 20.7 ± 0.5</p>
<p><em>Quadrature method:</em> u(sum) = √(0.3² + 0.2²) = √(0.09 + 0.04) = √0.13 ≈ <strong>0.36</strong> → 20.7 ± 0.36</p>
<p>The quadrature uncertainty is about 28% smaller — a real, meaningful difference, not rounding noise.</p>
<h3 id="example-2-multiplication-simple-vs-quadrature">Example 2 — Multiplication: simple vs. quadrature</h3>
<p><strong>Values:</strong> x₁ = 5.0 ± 0.2 (4% relative), x₂ = 3.0 ± 0.1 (3.33% relative). Product = 15.0.</p>
<p><em>Simple method:</em> relative u = 4% + 3.33% = 7.33% → absolute u = 15.0 × 0.0733 ≈ <strong>1.10</strong> → 15.0 ± 1.10</p>
<p><em>Quadrature method:</em> relative u = √(4%² + 3.33%²) = √(0.16% + 0.111%)&#8230; expressed as decimals: √(0.04² + 0.0333²) = √(0.0016 + 0.00111) ≈ 0.0521 (5.21%) → absolute u = 15.0 × 0.0521 ≈ <strong>0.78</strong> → 15.0 ± 0.78</p>
<p>Again quadrature comes in noticeably tighter — roughly 29% smaller than the simple estimate.</p>
<p><strong>Division works identically</strong> — it&#8217;s the same relative-uncertainty rule, just with the values divided instead of multiplied. For x₁ = 20.0 ± 0.4 (2% relative) divided by x₂ = 4.0 ± 0.2 (5% relative), quotient = 5.0:</p>
<p><em>Simple method:</em> relative u = 2% + 5% = 7% → absolute u = 5.0 × 0.07 = <strong>0.35</strong> → 5.0 ± 0.35</p>
<p><em>Quadrature method:</em> relative u = √(2%² + 5%²) = √29% ≈ 5.39% → absolute u = 5.0 × 0.0539 ≈ <strong>0.27</strong> → 5.0 ± 0.27</p>
<h3 id="example-3-powers">Example 3 — Powers</h3>
<p><strong>Value:</strong> x = 4.0 ± 0.1 (2.5% relative uncertainty). Calculate y = x².</p>
<p>Relative uncertainty of y: |2| × 2.5% = 5%. With y = 16.0, absolute uncertainty = 16.0 × 0.05 = <strong>0.8</strong>.</p>
<p><strong>Answer: y = 16.0 ± 0.8.</strong> Squaring doesn&#8217;t just square the value — it doubles the <em>relative</em> uncertainty.</p>
<h3 id="example-4-where-sig-figs-and-real-propagation-meet">Example 4 — Where sig figs and real propagation meet</h3>
<p><strong>Values, using only the implied precision of the written digits:</strong> 12.5 (written to 1 decimal place, implying roughly ±0.05) and 8.2 (also 1 decimal place, ±0.05).</p>
<p><em>Simple method:</em> u(sum) = 0.05 + 0.05 = 0.10 → sum is trustworthy to about ±0.1 <em>Quadrature method:</em> u(sum) = √(0.05² + 0.05²) = √0.005 ≈ 0.07 → sum is trustworthy to about ±0.07</p>
<p>Both land in the same place: <strong>trust the first decimal place of the sum, not the second.</strong> Compare that to the sig-fig addition rule from <a href="https://significantfigurescalculator.com/significant-figures/">our sig figs guide</a>: round the sum to the fewest decimal places among the inputs — here, 1 decimal place either way. The sig-fig rule and the numeric propagation agree, because the sig-fig rule is a shortcut for exactly this reasoning. It just skips calculating an actual uncertainty value and jumps straight to &#8220;keep this many digits.&#8221; (This &#8220;implied uncertainty from the last written digit&#8221; is itself a rough convention, not a substitute for a real stated uncertainty — see <a href="https://significantfigurescalculator.com/category/precision/accuracy-vs-precision/">our earlier gotcha on this</a> — but it&#8217;s precisely the assumption sig fig rules are quietly built on.)</p>
<h3 id="example-5-propagating-through-a-real-calculation">Example 5 — Propagating through a real calculation</h3>
<p><strong>Scenario:</strong> the area of a rectangle, with length L = 5.20 ± 0.05 cm and width W = 3.10 ± 0.04 cm. Area = L × W = 16.12 cm².</p>
<p>Relative uncertainties: u(L)/L = 0.05/5.20 ≈ 0.962%, u(W)/W = 0.04/3.10 ≈ 1.29%.</p>
<p><em>Simple method:</em> relative u = 0.962% + 1.29% = 2.25% → absolute u = 16.12 × 0.0225 ≈ <strong>0.36</strong> → Area = 16.12 ± 0.36 cm²</p>
<p><em>Quadrature method:</em> relative u = √(0.962%² + 1.29%²) ≈ 1.61% → absolute u = 16.12 × 0.0161 ≈ <strong>0.26</strong> → Area = 16.12 ± 0.26 cm²</p>
<p>This is what &#8220;uncertainty moves through a calculation&#8221; actually looks like end to end: two independently measured lengths, each with its own uncertainty, combining into one uncertainty on the derived area — smaller under quadrature, larger under the worst-case method, both defensible depending on what the number needs to guarantee.</p>
<hr />
<h2 id="where-this-still-trips-people-up">Where This Still Trips People Up</h2>
<ul>
<li><strong>Uncertainties add for subtraction too.</strong> It&#8217;s tempting to think subtracting two values should partly cancel their uncertainties, since the central values are being subtracted. They don&#8217;t. u(x₁ − x₂) = u(x₁) + u(x₂) under the simple method, exactly like addition — the <em>values</em> subtract, but the <em>uncertainties</em> never do.</li>
<li><strong>Quadrature assumes independence.</strong> If two uncertainties share a root cause (the same uncalibrated instrument, the same flawed technique), quadrature alone understates the real combined uncertainty — see the correlated-inputs note above.</li>
<li><strong>This is a linear approximation.</strong> Both methods rest on a first-order Taylor expansion. For strongly nonlinear functions, or uncertainties that are large relative to the measured value, the approximation itself can break down, and a full propagation (Monte Carlo, per JCGM 101:2008) may be needed.</li>
<li><strong>&#8220;Just use the biggest uncertainty&#8221; isn&#8217;t propagation.</strong> Every genuine source of uncertainty contributes some real variance to the result, even the smaller ones — ignoring all but the largest source underestimates the true combined uncertainty, sometimes substantially, as Examples 1 and 2 show.</li>
<li><strong>Powers use the relative uncertainty, not the absolute one.</strong> A common error is applying u(y) = n · u(x) directly to absolute uncertainties; the power multiplies the <em>relative</em> uncertainty, and you convert back to an absolute value afterward — see Example 3.</li>
</ul>
<hr />
<h2 id="which-method-different-contexts-actually-use">Which Method Different Contexts Actually Use</h2>
<p>&nbsp;</p>
<table>
<thead>
<tr>
<th>Context</th>
<th>Method typically used</th>
<th>Why</th>
</tr>
</thead>
<tbody>
<tr>
<td>Intro chemistry/physics coursework</td>
<td>Simple (worst-case) addition</td>
<td>Easier to compute by hand; deliberately conservative</td>
</tr>
<tr>
<td>Professional metrology, GUM-compliant labs</td>
<td>Quadrature — the GUM&#8217;s law of propagation of uncertainty</td>
<td>Reflects the actual statistical behavior of independent random errors</td>
</tr>
<tr>
<td>Engineering tolerance stacking (worst-case design)</td>
<td>Simple method, deliberately, even by professionals</td>
<td>A guaranteed bound matters more than a realistic average when parts must physically fit together</td>
</tr>
<tr>
<td>Scientific measurement reporting</td>
<td>Quadrature</td>
<td>Matches what a stated uncertainty is supposed to represent: a realistic confidence interval, not an absolute worst case</td>
</tr>
</tbody>
</table>
<p>Neither method is the &#8220;correct&#8221; one in general — they answer different questions. The simple method answers &#8220;what&#8217;s the largest this error could plausibly be if everything went wrong at once?&#8221; Quadrature answers &#8220;what&#8217;s the realistic, statistically expected uncertainty, assuming independent random errors?&#8221;</p>
<hr />
<h2 id="where-the-method-comes-from">Where the Method Comes From</h2>
<p>The quadrature approach isn&#8217;t a house convention — it&#8217;s the GUM&#8217;s (JCGM 100:2008) defined law of propagation of uncertainty, laid out in its Section 5, and it&#8217;s what <a href="https://significantfigurescalculator.com/category/precision/accuracy-vs-precision/">our accuracy/precision pillar</a> refers to as the formal companion to the VIM&#8217;s definitions. For the harder case of strongly nonlinear models or non-Gaussian input distributions, the GUM&#8217;s supplementary guide, JCGM 101:2008, describes a Monte Carlo alternative — propagating full probability distributions through the calculation by simulation rather than relying on the first-order approximation used here. That level of rigor is outside the scope of a sig figs calculator, but it&#8217;s worth knowing the name if a calculation ever demands it.</p>
<hr />
<h2 id="common-mistakes">Common Mistakes</h2>
<ol>
<li><strong>Adding absolute uncertainties for a multiplication problem</strong>, or relative uncertainties for an addition problem — these are reversed, exactly like the sig-fig arithmetic rules they mirror.</li>
<li><strong>Assuming subtraction cancels uncertainty.</strong> It doesn&#8217;t — see the gotcha above.</li>
<li><strong>Reporting the simple (worst-case) result as if it were a realistic statistical uncertainty</strong>, when quadrature is what scientific reporting convention actually expects.</li>
<li><strong>Ignoring correlation between input uncertainties</strong> that share a common source.</li>
<li><strong>Applying u(y) = n·u(x) to absolute uncertainty for a power calculation</strong>, instead of applying the multiplier to the relative uncertainty first — see Example 3.</li>
<li><strong>Treating the biggest single uncertainty as the whole answer</strong>, discarding every other real contributing source.</li>
</ol>
<hr />
<h2 id="practice-problems">Practice Problems</h2>
<p><strong>Concept: Simple method — addition</strong></p>
<p><strong>Q1.</strong> Using the simple method, x₁ = 5.0 ± 0.2 and x₂ = 3.0 ± 0.1 are added. What&#8217;s the propagated uncertainty? A) 0.1 B) 0.2 C) 0.3 D) 0.22 <strong>Answer: C) 0.3</strong> (0.2 + 0.1).</p>
<p><strong>Q2.</strong> Using the simple method, what&#8217;s the propagated uncertainty when <em>subtracting</em> x₂ from x₁ (same values as Q1)? A) 0.1 B) 0.2 C) 0.3 D) 0 <strong>Answer: C) 0.3</strong> — uncertainties add regardless of whether the operation is addition or subtraction.</p>
<p><strong>Concept: Quadrature — addition</strong></p>
<p><strong>Q3.</strong> Using quadrature, x₁ = 5.0 ± 0.2 and x₂ = 3.0 ± 0.1 are added. What&#8217;s the propagated uncertainty (2 sig figs)? A) 0.30 B) 0.22 C) 0.15 D) 0.10 <strong>Answer: B) 0.22</strong> (√(0.2² + 0.1²) = √0.05 ≈ 0.22).</p>
<p><strong>Q4.</strong> Why is the quadrature result in Q3 smaller than the simple result in Q1? A) It&#8217;s a rounding error B) Quadrature accounts for the statistical unlikelihood of both errors being at their worst simultaneously C) Quadrature only works for multiplication D) They should be identical <strong>Answer: B.</strong></p>
<p><strong>Concept: Relative uncertainty and multiplication</strong></p>
<p><strong>Q5.</strong> x = 5.0 ± 0.2. What is its relative uncertainty? A) 0.2% B) 2% C) 4% D) 20% <strong>Answer: C) 4%</strong> (0.2/5.0).</p>
<p><strong>Q6.</strong> Using the simple method, x₁ has 4% relative uncertainty and x₂ has 3% relative uncertainty. What&#8217;s the propagated relative uncertainty of x₁ × x₂? A) 1% B) 5% C) 7% D) 12% <strong>Answer: C) 7%</strong> (4% + 3%).</p>
<p><strong>Concept: Quadrature and multiplication</strong></p>
<p><strong>Q7.</strong> Using quadrature, x₁ has 4% relative uncertainty and x₂ has 3% relative uncertainty. What&#8217;s the propagated relative uncertainty? A) 3% B) 5% C) 7% D) 12% <strong>Answer: B) 5%</strong> (√(4² + 3²) = √25 = 5 — the same 3-4-5 relationship as a right triangle).</p>
<p><strong>Q8.</strong> Why does multiplication propagate through relative uncertainties rather than absolute ones? A) It&#8217;s an arbitrary convention B) A product&#8217;s sensitivity to each factor scales with the size of the other factor, which normalizes naturally into a percentage C) Absolute uncertainty doesn&#8217;t apply to multiplication D) There&#8217;s no real difference <strong>Answer: B.</strong></p>
<p><strong>Concept: Powers</strong></p>
<p><strong>Q9.</strong> x = 4.0 ± 0.1 (2.5% relative uncertainty). What is the relative uncertainty of y = x³? A) 2.5% B) 5% C) 7.5% D) 25% <strong>Answer: C) 7.5%</strong> (3 × 2.5%).</p>
<p><strong>Q10.</strong> Using Q9, with x = 4.0 so y = x³ = 64.0, what is the absolute uncertainty of y? A) 0.1 B) 1.6 C) 4.8 D) 16 <strong>Answer: C) 4.8</strong> (64.0 × 0.075).</p>
<hr />
<h2 id="simple-vs-quadrature-same-inputs">Simple vs. Quadrature, Same Inputs</h2>
<p><strong>Addition: 12.5 ± 0.3 + 8.2 ± 0.2 = 20.7 ± ?</strong></p>
<ul>
<li>Simple method → ± 0.50 (wider bar)</li>
<li>Quadrature method → ± 0.36 (narrower bar)</li>
</ul>
<p><strong>Multiplication: 5.0 ± 0.2 × 3.0 ± 0.1 = 15.0 ± ?</strong></p>
<ul>
<li>Simple method → ± 1.10 (wider bar)</li>
<li>Quadrature method → ± 0.78 (narrower bar)</li>
</ul>
<p>&nbsp;</p>
<h2 id="quick-reference">Quick Reference</h2>
<p>&nbsp;</p>
<table>
<thead>
<tr>
<th>Operation</th>
<th>Simple (worst-case)</th>
<th>Quadrature (GUM)</th>
</tr>
</thead>
<tbody>
<tr>
<td>Addition / subtraction</td>
<td>u(y) = u(x₁) + u(x₂)</td>
<td>u(y) = √[u(x₁)² + u(x₂)²]</td>
</tr>
<tr>
<td>Multiplication / division</td>
<td>u(y)/y = u(x₁)/x₁ + u(x₂)/x₂</td>
<td>u(y)/y = √[(u(x₁)/x₁)² + (u(x₂)/x₂)²]</td>
</tr>
<tr>
<td>Power, y = xⁿ</td>
<td>u(y)/y = n · u(x)/x</td>
<td><em>(same — powers don&#8217;t have a separate quadrature form)</em></td>
</tr>
</tbody>
</table>
<p><strong>Rule of thumb:</strong> quadrature ≤ simple, always. Use simple for a guaranteed worst-case bound; use quadrature for a realistic statistical estimate.</p>
<hr />
<h2 id="continue-learning">Continue Learning</h2>
<p><strong>Related fundamentals:</strong></p>
<ul>
<li>Accuracy, Precision, and Uncertainty: What Each One Actually Measures</li>
<li><a href="https://significantfigurescalculator.com/significant-figures/">Significant Figures: The Complete Guide</a></li>
</ul>
<p><strong>Go deeper on one topic at a time:</strong></p>
<ul>
<li>Absolute Error vs. Relative Error vs. Percent Error</li>
<li>What Measurement Uncertainty Actually Is</li>
<li>How to Read Uncertainty From a Ruler, Burette, or Digital Meter</li>
<li>How Many Sig Figs Should an Uncertainty Have?</li>
<li>Reporting Mean and Standard Deviation With Correct Precision</li>
<li>Why Significant Figures Are a Simplification of Real Uncertainty</li>
</ul>
<p><strong>Tools:</strong></p>
<ul>
<li>Error Propagation Calculator</li>
<li>Absolute &amp; Relative Uncertainty Calculator</li>
</ul>
<hr />
<p>&nbsp;</p>
<h2 id="sources-and-further-reading">Sources and Further Reading</h2>
<ul>
<li>JCGM 100:2008, <em>Evaluation of Measurement Data — Guide to the Expression of Uncertainty in Measurement (GUM)</em>, Section 5 — the primary source for the law of propagation of uncertainty and the general combined-uncertainty formula used throughout this page. (<a href="https://www.bipm.org/documents/20126/2071204/JCGM_100_2008_E.pdf">bipm.org</a>)</li>
<li>GUM Section 5, <em>Determining Combined Standard Uncertainty</em> (ISO-hosted full text) — confirms the formula&#8217;s basis in a first-order Taylor series approximation, cited above for the method&#8217;s known limits with nonlinear functions. (<a href="https://www.iso.org/sites/JCGM/GUM/JCGM100/C045315e-html/C045315e_FILES/MAIN_C045315e/05_e.html">iso.org</a>)</li>
<li>NIST Technical Note 1297, <em>Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results</em> — reused from our <a href="https://significantfigurescalculator.com/precision/accuracy-vs-precision/">accuracy/precision pillar</a>, NIST&#8217;s own implementation guide of the same GUM methodology applied here. (<a href="https://emtoolbox.nist.gov/publications/nisttechnicalnote1297s.pdf">emtoolbox.nist.gov</a>)</li>
</ul>
<hr />
<h2 id="review-and-methodology">Review and Methodology</h2>
<p><strong>Methodology:</strong> All formulas are cross-checked directly against the GUM (JCGM 100:2008) text, not a secondary paraphrase. Every worked example was independently recomputed during drafting. Calculator results referenced on this page use an arbitrary-precision decimal engine, not native floating-point math, validated against the site&#8217;s versioned regression fixture set.</p>
<hr />
<h2 id="changelog">Changelog</h2>
<p><strong>v1.0</strong> — Initial draft completed, 2026-08-10.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/error-propagation-uncertainty-calculation/">Error Propagation: How Uncertainty Moves Through a Calculation</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://significantfigurescalculator.com/precision/error-propagation-uncertainty-calculation/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Accuracy, Precision, and Uncertainty: What Each One Actually Measures</title>
		<link>https://significantfigurescalculator.com/precision/accuracy-precision-uncertainty/</link>
					<comments>https://significantfigurescalculator.com/precision/accuracy-precision-uncertainty/#respond</comments>
		
		<dc:creator><![CDATA[Tommy C. Moran]]></dc:creator>
		<pubDate>Tue, 11 Aug 2026 00:21:51 +0000</pubDate>
				<category><![CDATA[Accuracy vs Precision]]></category>
		<category><![CDATA[Precision]]></category>
		<category><![CDATA[metrology]]></category>
		<category><![CDATA[precision]]></category>
		<category><![CDATA[significant figures]]></category>
		<category><![CDATA[uncertainty]]></category>
		<guid isPermaLink="false">http://significantfigurescalculator.test/2026/08/11/accuracy-precision-uncertainty/</guid>

					<description><![CDATA[<p>Understand the distinct meanings of accuracy, precision, and uncertainty in measurement, with standards-based definitions, worked examples, and common pitfalls.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/accuracy-precision-uncertainty/">Accuracy, Precision, and Uncertainty: What Each One Actually Measures</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><strong>Accuracy is how close a measurement is to the true value. Precision is how close repeated measurements are to each other — regardless of whether they&#8217;re anywhere near the truth. Uncertainty is a calculated, honest range around a reported value, stating how far off it might plausibly be.</strong> These are three different properties, a measurement can have any combination of them, and significant figures only ever gesture vaguely at one — precision. A number with a lot of digits can still be flatly wrong.</p>
<p>This is the concept that everything else in this silo builds on — <a href="https://significantfigurescalculator.com/precision/error-propagation/">Error Propagation</a> is about calculating with these ideas, this page is about actually understanding them first. It matters more than it looks: &#8220;precision&#8221; and &#8220;accuracy&#8221; get used interchangeably in casual speech, but they describe genuinely different failure modes with genuinely different fixes. A miscalibrated instrument can produce beautifully consistent, high-sig-fig, completely wrong numbers all day long. Knowing which problem you actually have determines whether the fix is &#8220;calibrate the equipment&#8221; or &#8220;take more measurements&#8221; — and those are not interchangeable solutions.</p>
<blockquote><p>&nbsp;</p></blockquote>
<h2 id="three-different-properties">Three Different Properties</h2>
<p><strong>Accuracy: closeness to the true value.</strong> If the true length of an object is 10.00 cm and your measurement reads 10.01 cm, that&#8217;s accurate — it&#8217;s close to reality. Accuracy is about correctness relative to something external and (ideally) known.</p>
<p><strong>Precision: closeness of repeated measurements to each other.</strong> If you measure the same object five times and get 10.01, 10.02, 10.01, 10.00, 10.01 cm, that&#8217;s precise — the numbers agree with each other tightly, regardless of whether they&#8217;re actually close to the object&#8217;s true length. Precision is entirely internal to the measurement process; it says nothing on its own about correctness.</p>
<p><strong>These are independent.</strong> A measurement process can be accurate without being precise (scattered, but centered on the truth), precise without being accurate (tightly clustered, but centered on the wrong value), both, or neither. See Example 1.</p>
<p><strong>Uncertainty: a calculated, honest range of doubt.</strong> Where accuracy and precision describe qualities of a measurement process, uncertainty is a specific number attached to a specific result — typically written as a value ± a range, ideally with a stated confidence level. It answers &#8220;how far off might this reported number plausibly be?&#8221; It is not the same thing as &#8220;how many significant figures I happened to write down&#8221; — sig figs are a rough, informal stand-in for precision; a real uncertainty is a deliberately calculated quantity. See Example 4.</p>
<p><strong>What actually causes each problem: systematic vs. random error.</strong> This is the part most classroom treatments skip, and it&#8217;s the part that determines what you actually do about a bad measurement.</p>
<ul>
<li><strong>Systematic error</strong> is a consistent bias in one direction — a scale that was never zeroed, a ruler with a worn end, a flawed procedure applied the same way every time. It damages <em>trueness</em> (and therefore accuracy), and critically, <strong>it does not average out.</strong> Every single reading is wrong in the same direction by roughly the same amount, no matter how many times you repeat the measurement.</li>
<li><strong>Random error</strong> is unpredictable scatter — estimating between the smallest marked lines on a ruler, small environmental fluctuations, ordinary human variability in reading an instrument. It damages <em>precision</em>, and it <strong>does</strong> average out: because random errors are roughly as likely to be too high as too low, taking the mean of many repeated readings makes the average more reliable even though any single reading might still be off.</li>
</ul>
<p>This is the single most useful practical takeaway on this page: <strong>taking more measurements and averaging them fixes a precision problem. It does nothing for an accuracy problem.</strong> If your instrument is miscalibrated, averaging a thousand readings from it just gives you an extremely precise, extremely wrong number.</p>
<p><strong>A formal refinement, for anyone working to a real standard.</strong> The classroom version above treats accuracy and precision as two independent axes — which is the right mental model for everyday use. Formal metrology, however, defines &#8220;accuracy&#8221; more narrowly: the international vocabulary of metrology (the VIM, jointly maintained by the BIPM, ISO, and six other international bodies) treats accuracy as the <em>combination</em> of trueness and precision, not a separate third thing. In this stricter usage, a measurement process that&#8217;s true on average but wildly scattered isn&#8217;t fully &#8220;accurate&#8221; even though a lucky individual reading might land near the truth — it has good trueness and poor precision, and &#8220;accuracy&#8221; requires both. This distinction rarely matters for classroom work, but it matters in exactly the industrial and lab-conformance contexts where this site&#8217;s <a href="https://significantfigurescalculator.com/rounding/astm-e29/">ASTM E29 guide</a> also applies.</p>
<hr />
<h2 id="worked-examples">Worked Examples</h2>
<h3 id="example-1-all-four-combinations">Example 1 — All four combinations</h3>
<p><strong>True value: 10.00 cm.</strong> Four sets of four repeated measurements:</p>
<table>
<thead>
<tr>
<th>Set</th>
<th>Measurements</th>
<th>Mean</th>
<th>Accurate?</th>
<th>Precise?</th>
</tr>
</thead>
<tbody>
<tr>
<td>A</td>
<td>9.98, 10.01, 9.99, 10.02</td>
<td>10.00</td>
<td>Yes</td>
<td>Yes — tight cluster</td>
</tr>
<tr>
<td>B</td>
<td>12.50, 12.51, 12.49, 12.50</td>
<td>12.50</td>
<td>No — off by 2.50 cm</td>
<td>Yes — tight cluster</td>
</tr>
<tr>
<td>C</td>
<td>9.20, 10.65, 9.85, 10.30</td>
<td>10.00</td>
<td>Yes, on average</td>
<td>No — wide scatter</td>
</tr>
<tr>
<td>D</td>
<td>13.50, 9.50, 12.50, 10.50</td>
<td>11.50</td>
<td>No — off by 1.50 cm</td>
<td>No — wide scatter</td>
</tr>
</tbody>
</table>
<p>Set B is the dangerous one: every reading agrees with every other reading almost exactly, which <em>feels</em> trustworthy, and every single one of them is wrong.</p>
<h3 id="example-2-a-closer-look-at-precise-but-wrong">Example 2 — A closer look at &#8220;precise but wrong&#8221;</h3>
<p><strong>Set B from Example 1:</strong> 12.50, 12.51, 12.49, 12.50 cm, against a true value of 10.00 cm.</p>
<p>The spread here is tiny — deviations from the mean of 0, +0.01, −0.01, and 0 cm give a sample standard deviation of roughly <strong>0.008 cm</strong>, well under a hundredth of a centimeter. By any statistical measure, this is an excellent, highly precise data set. It is also wrong by 2.50 cm, a 25% error relative to the true value. Writing &#8220;12.50 cm&#8221; — three significant figures, looking every bit as authoritative as Set A&#8217;s correct answer — communicates nothing about this 2.50 cm gap. Sig figs describe precision. They cannot, on their own, tell you whether the instrument was ever calibrated correctly.</p>
<h3 id="example-3-calculating-percent-error">Example 3 — Calculating percent error</h3>
<p><strong>Calculation:</strong> measured value 24.7 g, true/accepted value 25.0 g</p>
<p>Percent error = |measured − true| / true × 100% = |24.7 − 25.0| / 25.0 × 100% = 0.3 / 25.0 × 100%</p>
<p><strong>Answer: 1.2%.</strong> This is the standard way accuracy actually gets quantified and reported — a single number describing how far off a result is, as a proportion of the accepted value.</p>
<h3 id="example-4-reporting-a-value-with-its-uncertainty">Example 4 — Reporting a value with its uncertainty</h3>
<p><strong>Raw data:</strong> a calculated value of 12.7346 cm with a calculated uncertainty of 0.0623 cm</p>
<p>Standard metrology guidance (the GUM, JCGM 100:2008, §7.2.6) is to round the <em>uncertainty</em> first — typically to 1 or 2 significant figures — and then match the reported value&#8217;s decimal places to it, not the other way around.</p>
<p>Round 0.0623 to 2 significant figures → <strong>0.062</strong> (3 decimal places). Round 12.7346 to the same 3 decimal places → <strong>12.735</strong>.</p>
<p><strong>Answer: 12.735 ± 0.062 cm.</strong> Reporting more decimal places on the value than the uncertainty justifies — say, 12.7346 ± 0.062 — implies a false precision the data doesn&#8217;t actually support.</p>
<h3 id="example-5-why-averaging-doesnt-fix-everything">Example 5 — Why averaging doesn&#8217;t fix everything</h3>
<p><strong>Scenario:</strong> a student measures a table&#8217;s length five times with a metal ruler whose zero mark is worn down by 0.5 cm (unknown to the student): 152.3, 152.4, 152.2, 152.3, 152.5 cm.</p>
<p>The small differences between these five readings — 152.2 up to 152.5 cm — are <strong>random error</strong>: ordinary variation in how precisely a ruler can be read by eye. The consistent 0.5 cm the entire set is offset from the table&#8217;s true length is <strong>systematic error</strong>, caused by the worn zero mark, and it affects every single reading the same way.</p>
<p>Averaging the five readings gives a mean of <strong>152.34 cm</strong> — a more reliable, more precise central estimate than any single reading, because averaging cancels out random scatter. It does nothing about the 0.5 cm systematic offset. That error is baked into every measurement this ruler will ever produce, no matter how many times the table gets measured with it.</p>
<hr />
<h2 id="where-this-still-trips-people-up">Where This Still Trips People Up</h2>
<ul>
<li><strong>A precise-looking number is not the same as a correct one.</strong> Three, four, even six sig figs can accompany a measurement that&#8217;s simply wrong — see Example 2. Precision and correctness are independent properties.</li>
<li><strong>&#8220;Just take more measurements&#8221; only fixes half the problem.</strong> It reduces random error beautifully. It does nothing for systematic error — see Example 5. If results are consistently biased, the fix is recalibration or procedural correction, not more repetitions of the same flawed method.</li>
<li><strong>Casual English blurs accuracy and precision together</strong> — &#8220;a precision instrument&#8221; is often assumed to also mean an accurate one, but precision alone says nothing about whether the instrument was ever calibrated against a true reference.</li>
<li><strong>An uncertainty isn&#8217;t the same as &#8220;the last digit is a guess.&#8221;</strong> Some intro courses use &#8220;assume ±1 in the last significant figure&#8221; as a rough shortcut, and it&#8217;s a reasonable estimate for a single unlabeled reading — but it&#8217;s a simplification, not a substitute for an actually calculated uncertainty like the one in Example 4.</li>
<li><strong>A single lucky reading can look accurate from a bad process.</strong> Set C in Example 1 has a correct mean, but any individual measurement drawn from it could be off by half a centimeter. Accuracy of the average is not the same guarantee as accuracy of any one result.</li>
</ul>
<hr />
<h2 id="how-accuracy-gets-defined-differently">How &#8220;Accuracy&#8221; Gets Defined Differently</h2>
<p>&nbsp;</p>
<table>
<thead>
<tr>
<th>Context</th>
<th>How accuracy is treated</th>
</tr>
</thead>
<tbody>
<tr>
<td>General/classroom science</td>
<td>An independent quality from precision — closeness to the true value, full stop, regardless of how scattered the individual readings were</td>
</tr>
<tr>
<td>Formal metrology (VIM, JCGM 200:2012)</td>
<td>Not independent — accuracy is the <em>combination</em> of trueness (low systematic error) and precision (low random error); good trueness alone isn&#8217;t enough to be called &#8220;accurate&#8221;</td>
</tr>
<tr>
<td>Statistics</td>
<td>The equivalent split is usually phrased as <strong>bias</strong> (lack of trueness) and <strong>variability</strong> (lack of precision) — same underlying distinction, different vocabulary</td>
</tr>
<tr>
<td>Everyday/colloquial usage</td>
<td>Often used loosely to mean &#8220;correct&#8221; or &#8220;exact,&#8221; and frequently conflated with precision entirely</td>
</tr>
</tbody>
</table>
<p>The classroom version is the right mental model for day-to-day sig fig work — it&#8217;s simpler and it&#8217;s what Example 1&#8217;s four-quadrant table above uses. The VIM version matters once you&#8217;re working to an actual standard (calibration certificates, lab accreditation, conformance testing), where &#8220;accurate&#8221; is a defined term with real consequences attached to it.</p>
<hr />
<h2 id="where-the-definitions-come-from">Where the Definitions Come From</h2>
<p>The formal split between trueness, precision, and accuracy comes from the VIM — the International Vocabulary of Metrology, JCGM 200:2012 — jointly maintained by the BIPM, ISO, IEC, and five other international standards bodies specifically so that &#8220;accuracy&#8221; means the same thing to a lab in Jakarta as it does to one in Geneva. The VIM&#8217;s own guidance is explicit that trueness reflects systematic error and is unrelated to random error, which is exactly the causal split covered in this page&#8217;s rule statement above. The companion document, the GUM (JCGM 100:2008), governs how the <em>uncertainty</em> number itself gets calculated and rounded once trueness and precision are understood — the mechanics of that calculation are covered in <a href="https://significantfigurescalculator.com/precision/error-propagation/">Error Propagation</a>.</p>
<hr />
<h2 id="common-mistakes">Common Mistakes</h2>
<ol>
<li><strong>Assuming more decimal places or sig figs means a more accurate result.</strong> They only ever imply more precision — see Example 2.</li>
<li><strong>Trying to fix a systematic error by averaging more readings.</strong> Averaging only helps with random error — see Example 5.</li>
<li><strong>Reporting a value&#8217;s precision beyond what its uncertainty justifies.</strong> If the uncertainty is ±0.06, reporting the value to five decimal places is false precision — see Example 4.</li>
<li><strong>Confusing &#8220;error&#8221; with &#8220;uncertainty.&#8221;</strong> Error is the actual (usually unknowable) difference between a measurement and the truth. Uncertainty is a defensible, calculated estimate of how large that error plausibly is — the two words get used interchangeably in casual speech but mean different things.</li>
<li><strong>Treating a single accurate-looking reading as proof the whole process is reliable</strong>, when it could simply be a lucky draw from a wide, imprecise scatter.</li>
<li><strong>Using &#8220;precision instrument&#8221; and &#8220;accurate instrument&#8221; as synonyms</strong> — a precise instrument that&#8217;s never been calibrated can produce confidently wrong numbers indefinitely.</li>
</ol>
<hr />
<h2 id="practice-problems">Practice Problems</h2>
<p><strong>Concept: Accuracy vs. precision</strong></p>
<p><strong>Q1.</strong> A set of measurements clusters tightly together but far from the true value. This demonstrates: A) High accuracy, low precision B) High precision, low accuracy C) High accuracy and precision D) Low accuracy and precision <strong>Answer: B.</strong></p>
<p><strong>Q2.</strong> A set of measurements scatters widely but averages out close to the true value. This demonstrates: A) High accuracy, low precision B) High precision, low accuracy C) High accuracy and precision D) Low accuracy and precision <strong>Answer: A.</strong></p>
<p><strong>Concept: Formal (VIM) definitions</strong></p>
<p><strong>Q3.</strong> In the formal metrology vocabulary (VIM), &#8220;accuracy&#8221; is best described as: A) A synonym for precision B) A combination of trueness and precision C) Only about repeated measurements agreeing D) Only about the number of significant figures used <strong>Answer: B.</strong></p>
<p><strong>Q4.</strong> &#8220;Trueness,&#8221; in the VIM sense, relates most directly to: A) Random error B) Systematic error (bias) C) Rounding error D) Sig fig count <strong>Answer: B.</strong></p>
<p><strong>Concept: Systematic vs. random error</strong></p>
<p><strong>Q5.</strong> Averaging many repeated measurements primarily helps reduce: A) Systematic error B) Random error C) Both equally D) Neither <strong>Answer: B.</strong></p>
<p><strong>Q6.</strong> A scale that is never zeroed before use, and so reads 50 g high on every single measurement, is exhibiting: A) Random error B) Systematic error C) Rounding error D) High precision, no accuracy problem at all <strong>Answer: B.</strong></p>
<p><strong>Concept: Percent error</strong></p>
<p><strong>Q7.</strong> A measured value is 24.7 g against a true value of 25.0 g. What is the percent error? A) 0.3% B) 1.2% C) 3.0% D) 12% <strong>Answer: B) 1.2%.</strong></p>
<p><strong>Q8.</strong> A measured value is 48 m/s against a true value of 50 m/s. What is the percent error? A) 2% B) 4% C) 96% D) 0.04% <strong>Answer: B) 4%.</strong></p>
<p><strong>Concept: Reporting uncertainty</strong></p>
<p><strong>Q9.</strong> Per standard metrology guidance, when reporting a value together with its uncertainty, which is rounded first? A) The value B) The uncertainty C) Both, independently and separately D) Neither needs rounding <strong>Answer: B.</strong></p>
<p><strong>Q10.</strong> An uncertainty is calculated as 0.0623 units. Rounded to 2 significant figures, it becomes: A) 0.06 B) 0.062 C) 0.0623 D) 0.1 <strong>Answer: B) 0.062.</strong></p>
<hr />
<h2 id="the-bullseye-with-real-numbers">The Bullseye, With Real Numbers</h2>
<ul>
<li><strong>Top-left (accurate + precise):</strong> Set A — 9.98, 10.01, 9.99, 10.02 → tight cluster, centered on the bullseye (true value 10.00)</li>
<li><strong>Top-right (precise, not accurate):</strong> Set B — 12.50, 12.51, 12.49, 12.50 → tight cluster, off-center by 2.50</li>
<li><strong>Bottom-left (accurate on average, not precise):</strong> Set C — 9.20, 10.65, 9.85, 10.30 → scattered, but centered on the bullseye</li>
<li><strong>Bottom-right (neither):</strong> Set D — 13.50, 9.50, 12.50, 10.50 → scattered and off-center</li>
</ul>
<p>&nbsp;</p>
<h2 id="quick-reference">Quick Reference</h2>
<p>&nbsp;</p>
<table>
<thead>
<tr>
<th>Term</th>
<th>What it measures</th>
<th>Fixed by</th>
</tr>
</thead>
<tbody>
<tr>
<td>Accuracy</td>
<td>Closeness to the true value</td>
<td>Calibration, correcting bias</td>
</tr>
<tr>
<td>Precision</td>
<td>Closeness of repeated measurements to each other</td>
<td>Better technique, more repeated trials, averaging</td>
</tr>
<tr>
<td>Uncertainty</td>
<td>The calculated range of doubt around a reported value</td>
<td>Proper error propagation (not guesswork)</td>
</tr>
<tr>
<td>Systematic error</td>
<td>The cause of poor accuracy/trueness</td>
<td>Recalibration — does not average out</td>
</tr>
<tr>
<td>Random error</td>
<td>The cause of poor precision</td>
<td>Averaging — does reduce with more trials</td>
</tr>
</tbody>
</table>
<hr />
<h2 id="continue-learning">Continue Learning</h2>
<p><strong>Related fundamentals:</strong></p>
<ul>
<li><a href="https://significantfigurescalculator.com/significant-figures/">Significant Figures: The Complete Guide</a></li>
<li><a href="https://significantfigurescalculator.com/precision/error-propagation/">Error Propagation: How Uncertainty Moves Through a Calculation</a></li>
</ul>
<p><strong>Go deeper on one topic at a time:</strong></p>
<ul>
<li>Absolute Error vs. Relative Error vs. Percent Error</li>
<li>How to Calculate Percent Error (and Report It Correctly)</li>
<li>What Measurement Uncertainty Actually Is</li>
<li>How to Read Uncertainty From a Ruler, Burette, or Digital Meter</li>
<li><a href="https://significantfigurescalculator.com/precision/error-propagation/">Propagating Uncertainty Through Addition and Multiplication</a></li>
<li>How Many Sig Figs Should an Uncertainty Have?</li>
<li>Reporting Mean and Standard Deviation With Correct Precision</li>
<li>Why Significant Figures Are a Simplification of Real Uncertainty</li>
</ul>
<p><strong>Tools:</strong></p>
<ul>
<li>Percent Error Calculator</li>
<li>Absolute &amp; Relative Uncertainty Calculator</li>
</ul>
<hr />
<p>&nbsp;</p>
<h2 id="sources-and-further-reading">Sources and Further Reading</h2>
<ul>
<li>JCGM 200:2012, <em>International Vocabulary of Metrology — Basic and General Concepts and Associated Terms (VIM)</em>, jointly published by the BIPM, ISO, IEC, and five other international bodies — the primary source for the trueness/precision/accuracy relationship described throughout this page. (<a href="https://www.bipm.org/documents/20126/2071204/JCGM_200_2012.pdf">bipm.org</a>)</li>
<li>NIST Technical Note 1297, <em>Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results</em> — NIST&#8217;s implementation guide of the GUM, cited here for the uncertainty-rounding rule used in Example 4 (reused from our <a href="https://significantfigurescalculator.com/rounding/">rounding pillar</a>, where it&#8217;s also cited for the same underlying GUM guidance). (<a href="https://emtoolbox.nist.gov/publications/nisttechnicalnote1297s.pdf">emtoolbox.nist.gov</a>)</li>
<li>Cherry Biotech, <em>Accuracy and Precision in Measurements</em> — a clear secondary explainer connecting VIM terminology to the parallel statistical vocabulary (bias and variability) and to ISO 5725. (<a href="https://www.cherrybiotech.com/scientific-note/accuracy-and-precision-in-measurements/">cherrybiotech.com</a>)</li>
</ul>
<hr />
<h2 id="review-and-methodology">Review and Methodology</h2>
<p><strong>Methodology:</strong> Definitions and the trueness/precision/accuracy relationship are cross-checked directly against BIPM&#8217;s own VIM documentation (see Sources), not inferred from secondary explainers. Calculator results referenced on this page use an arbitrary-precision decimal engine, not native floating-point math, validated against the site&#8217;s versioned regression fixture set.</p>
<hr />
<h2 id="changelog">Changelog</h2>
<p><strong>v1.0</strong> — Initial draft completed, 2026-08-10.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/accuracy-precision-uncertainty/">Accuracy, Precision, and Uncertainty: What Each One Actually Measures</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://significantfigurescalculator.com/precision/accuracy-precision-uncertainty/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How to Read Uncertainty From a Ruler, Burette, or Digital Meter</title>
		<link>https://significantfigurescalculator.com/precision/measurement-uncertainty/reading-uncertainty-ruler-burette-digital-meter/</link>
					<comments>https://significantfigurescalculator.com/precision/measurement-uncertainty/reading-uncertainty-ruler-burette-digital-meter/#respond</comments>
		
		<dc:creator><![CDATA[Tommy C. Moran]]></dc:creator>
		<pubDate>Wed, 05 Aug 2026 05:35:56 +0000</pubDate>
				<category><![CDATA[Measurement Uncertainty]]></category>
		<category><![CDATA[ASTM E29]]></category>
		<category><![CDATA[precision]]></category>
		<category><![CDATA[rounding]]></category>
		<category><![CDATA[significant figures]]></category>
		<category><![CDATA[uncertainty]]></category>
		<guid isPermaLink="false">http://significantfigurescalculator.test/uncategorized/reading-uncertainty-ruler-burette-digital-meter/</guid>

					<description><![CDATA[<p>Learn the correct way to interpret measurement uncertainty from analog and digital instruments, including significant figures, rounding, and standard conventions.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/measurement-uncertainty/reading-uncertainty-ruler-burette-digital-meter/">How to Read Uncertainty From a Ruler, Burette, or Digital Meter</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2 id="rule-statement">Rule Statement</h2>
<p>When reading a measurement from an instrument, the recorded value must reflect both the magnitude and the uncertainty of the reading. The uncertainty is determined by the instrument&#8217;s resolution and the measurement context. For analog instruments (ruler, burette), the uncertainty is typically taken as half the smallest scale division, though some conventions use the full division. For digital instruments, the uncertainty is usually ±1 in the last displayed digit, unless the manufacturer specifies a different value. The number of significant figures in the recorded value must be consistent with this uncertainty: the last significant digit should be in the same decimal place as the uncertainty.</p>
<p>This rule aligns with the <strong>Guide to the Expression of Uncertainty in Measurement (GUM)</strong>, which states that the uncertainty should be given to at most two significant figures and that the measurement result should be rounded to match the uncertainty (JCGM 100:2008, Clause 7.2.6). For practical work, we use the instrument&#8217;s resolution to estimate the uncertainty, following the principle of <em>resolution-limited uncertainty</em>.</p>
<h2 id="worked-examples">Worked Examples</h2>
<h3 id="example-1-ruler-with-millimeter-divisions">Example 1: Ruler with millimeter divisions</h3>
<p>A standard metric ruler has divisions of 1 mm. The smallest division is 1 mm, so the uncertainty is ±0.5 mm (half the division). When reading a length, you should estimate to the nearest 0.1 mm (one decimal place beyond the smallest division) to get a meaningful reading. For instance, if the object&#8217;s edge falls between 23 mm and 24 mm, you might estimate it as 23.4 mm. The recorded value is <strong>23.4 mm ± 0.5 mm</strong>. This has three significant figures, with the last digit (tenths place) matching the uncertainty&#8217;s decimal place.</p>
<h3 id="example-2-burette-with-0-1-ml-divisions">Example 2: Burette with 0.1 mL divisions</h3>
<p>A typical burette has graduations every 0.1 mL. The uncertainty is ±0.05 mL (half of 0.1 mL). When reading the meniscus, you estimate to the nearest 0.01 mL. For example, if the meniscus is at 12.35 mL, the reading is <strong>12.35 mL ± 0.05 mL</strong>. The recorded value has four significant figures, with the hundredths place matching the uncertainty.</p>
<h3 id="example-3-digital-multimeter-displaying-3-456-v">Example 3: Digital multimeter displaying 3.456 V</h3>
<p>For a digital meter, the resolution is the smallest change in the displayed value. If the display shows 3.456 V, the resolution is 0.001 V. The uncertainty is typically ±0.001 V (or sometimes ±0.0005 V if the manufacturer specifies a more precise uncertainty). The recorded value is <strong>3.456 V ± 0.001 V</strong>. Do not add extra digits beyond what is displayed; the display already includes the uncertainty in its last digit.</p>
<h2 id="counter-examples">Counter-Examples</h2>
<p>These common errors illustrate how NOT to read uncertainty.</p>
<ul>
<li><strong>Overestimating precision on a ruler:</strong> Reading a ruler with 1 mm divisions to 0.01 mm (e.g., 23.45 mm) is incorrect because the uncertainty is ±0.5 mm, so the hundredths place is meaningless. The correct reading is 23.4 mm ± 0.5 mm (or 23.5 mm if you estimate that precisely).</li>
<li><strong>Ignoring the last digit on a digital meter:</strong> If a digital meter displays 3.456 V, writing 3.46 V (rounding to three decimal places) loses the resolution. The uncertainty is ±0.001 V, so the reading should be 3.456 V, not 3.46 V.</li>
<li><strong>Using the full division as uncertainty:</strong> Some textbooks say the uncertainty is the smallest division, not half. For a ruler with 1 mm divisions, this would give ±1 mm. While this is a conservative estimate, it is not the standard convention for a single reading. The GUM recommends half the division for analog scales when the operator can interpolate (JCGM 100:2008, Clause 4.6.1).</li>
</ul>
<h2 id="convention-comparison-table">Convention Comparison Table</h2>
<table>
<thead>
<tr>
<th>Instrument Type</th>
<th>Smallest Division / Resolution</th>
<th>Uncertainty (Common Convention)</th>
<th>How to Record</th>
</tr>
</thead>
<tbody>
<tr>
<td>Analog ruler (mm)</td>
<td>1 mm</td>
<td>±0.5 mm</td>
<td>Estimate to 0.1 mm (e.g., 23.4 mm)</td>
</tr>
<tr>
<td>Analog burette (0.1 mL)</td>
<td>0.1 mL</td>
<td>±0.05 mL</td>
<td>Estimate to 0.01 mL (e.g., 12.35 mL)</td>
</tr>
<tr>
<td>Digital meter (3 decimal places)</td>
<td>0.001 V</td>
<td>±0.001 V (or ±0.0005 V if specified)</td>
<td>Read all digits (e.g., 3.456 V)</td>
</tr>
<tr>
<td>Digital meter with auto-ranging</td>
<td>Varies</td>
<td>±1 in the last displayed digit</td>
<td>Read all digits, note the range</td>
</tr>
</tbody>
</table>
<p>Note: Some disciplines (e.g., chemistry) may adopt a different convention, such as using the full division for analog instruments when the scale is coarse. Always follow your laboratory or industry standard.</p>
<h2 id="standards-citation">Standards Citation</h2>
<p>The following standards provide authoritative guidance on uncertainty and significant figures:</p>
<ul>
<li><strong>JCGM 100:2008 (GUM):</strong> Guide to the Expression of Uncertainty in Measurement. Clause 7.2.6 recommends that the uncertainty be given to at most two significant figures and that the measurement result be rounded to the same decimal place as the uncertainty.</li>
<li><strong>ASTM E29-13:</strong> Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications. This standard defines how to round test results and how to determine the number of significant digits based on the measurement resolution.</li>
<li><strong>ISO 80000-1:2009:</strong> Quantities and units – Part 1: General. Annex C provides guidance on rounding and significant figures, emphasizing that the number of significant digits should be consistent with the uncertainty.</li>
<li><strong>NIST Technical Note 1297:</strong> Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results. This document offers practical advice on uncertainty estimation for physical measurements.</li>
</ul>
<p>When in doubt, consult the specific standard applicable to your field. For general scientific work, the GUM is the primary reference.</p>
<h2 id="common-mistakes">Common Mistakes</h2>
<ol>
<li><strong>Recording too many digits:</strong> For analog instruments, recording more than one decimal place beyond the smallest division is a common error. For example, reading a ruler with 1 mm divisions to 0.01 mm is false precision.</li>
<li><strong>Recording too few digits:</strong> For digital instruments, dropping trailing zeros or rounding off the last digit loses information. If a digital meter displays 3.000 V, record all four digits, not 3 V.</li>
<li><strong>Confusing resolution with accuracy:</strong> The uncertainty from resolution is only one component. The instrument&#8217;s accuracy (e.g., ±0.5% of reading) may be larger. Always check the manufacturer&#8217;s specifications.</li>
<li><strong>Inconsistent rounding:</strong> When reporting a result, the uncertainty and the value must have the same decimal place. If the uncertainty is 0.05, the value must be reported to the hundredths place (e.g., 12.35 ± 0.05, not 12.3 ± 0.05).</li>
<li><strong>Ignoring parallax and calibration:</strong> These are not directly related to reading uncertainty, but they affect the overall uncertainty. Always align your eye perpendicular to the scale to avoid parallax error.</li>
</ol>
<h2 id="practice-problems">Practice Problems</h2>
<p>Test your understanding with these exercises. Answers are provided below.</p>
<ol>
<li>A burette has graduations every 0.1 mL. You read the meniscus at 24.7 mL. What is the correct reading with uncertainty?</li>
<li>A digital thermometer displays 36.5 °C. What is the uncertainty and the correct recorded value?</li>
<li>A ruler with 0.5 cm divisions is used to measure a length. The edge falls between 4.5 cm and 5.0 cm. Estimate the reading and its uncertainty.</li>
</ol>
<p><strong>Answers:</strong></p>
<ol>
<li>24.7 mL ± 0.05 mL (since the smallest division is 0.1 mL, half is 0.05 mL).</li>
<li>36.5 °C ± 0.1 °C (assuming the display shows one decimal place, the resolution is 0.1 °C).</li>
<li>4.7 cm ± 0.25 cm (half of 0.5 cm). Estimate to 0.1 cm, so 4.7 cm is appropriate.</li>
</ol>
<h2 id="quick-reference-table">Quick Reference Table</h2>
<table>
<thead>
<tr>
<th>Instrument</th>
<th>Smallest Division / Resolution</th>
<th>Uncertainty</th>
<th>Number of Significant Figures</th>
</tr>
</thead>
<tbody>
<tr>
<td>Ruler (1 mm)</td>
<td>1 mm</td>
<td>±0.5 mm</td>
<td>3 (if reading in mm, e.g., 23.4 mm)</td>
</tr>
<tr>
<td>Ruler (0.5 cm)</td>
<td>0.5 cm</td>
<td>±0.25 cm</td>
<td>2 (e.g., 4.7 cm)</td>
</tr>
<tr>
<td>Burette (0.1 mL)</td>
<td>0.1 mL</td>
<td>±0.05 mL</td>
<td>4 (e.g., 12.35 mL)</td>
</tr>
<tr>
<td>Digital meter (3 decimals)</td>
<td>0.001 unit</td>
<td>±0.001 unit</td>
<td>4 (e.g., 3.456)</td>
</tr>
<tr>
<td>Digital meter (2 decimals)</td>
<td>0.01 unit</td>
<td>±0.01 unit</td>
<td>3 (e.g., 3.45)</td>
</tr>
</tbody>
</table>
<p>For more on significant figures and rounding, see our <a href="/significant-figures-calculator">significant figures calculator</a> and the <a href="/rounding-rules">rounding rules</a> article.</p>
<h2 id="sources-further-reading">Sources &amp; Further Reading</h2>
<ul>
<li>JCGM 100:2008, <em>Evaluation of measurement data — Guide to the expression of uncertainty in measurement</em>, BIPM, IEC, IFCC, ILAC, ISO, IUPAC, IUPAP, OIML.</li>
<li>ASTM E29-13, <em>Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications</em>, ASTM International.</li>
<li>ISO 80000-1:2009, <em>Quantities and units — Part 1: General</em>, ISO.</li>
<li>NIST Technical Note 1297, <em>Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results</em>, NIST.</li>
<li>Taylor, J. R., <em>An Introduction to Error Analysis</em>, University Science Books, 1997.</li>
</ul>
<p>For further reading on related topics, see our articles on <a href="/accuracy-vs-precision">Accuracy vs Precision</a> and <a href="/error-propagation">Error Propagation</a>.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/measurement-uncertainty/reading-uncertainty-ruler-burette-digital-meter/">How to Read Uncertainty From a Ruler, Burette, or Digital Meter</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://significantfigurescalculator.com/precision/measurement-uncertainty/reading-uncertainty-ruler-burette-digital-meter/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Absolute Error vs Relative Error vs Percent Error: A Comprehensive Guide</title>
		<link>https://significantfigurescalculator.com/precision/absolute-vs-relative-error/absolute-error-vs-relative-error-vs-percent-error/</link>
					<comments>https://significantfigurescalculator.com/precision/absolute-vs-relative-error/absolute-error-vs-relative-error-vs-percent-error/#respond</comments>
		
		<dc:creator><![CDATA[Tommy C. Moran]]></dc:creator>
		<pubDate>Sun, 02 Aug 2026 23:28:16 +0000</pubDate>
				<category><![CDATA[Absolute vs Relative Error]]></category>
		<category><![CDATA[metrology]]></category>
		<category><![CDATA[significant figures]]></category>
		<guid isPermaLink="false">http://significantfigurescalculator.test/uncategorized/absolute-error-vs-relative-error-vs-percent-error/</guid>

					<description><![CDATA[<p>Understand the differences between absolute, relative, and percent error, including formulas, when to use each, standards, and common pitfalls. A definitive reference for measurement science.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/absolute-vs-relative-error/absolute-error-vs-relative-error-vs-percent-error/">Absolute Error vs Relative Error vs Percent Error: A Comprehensive Guide</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>In measurement science, quantifying error is fundamental. Three common metrics—<strong>absolute error</strong>, <strong>relative error</strong>, and <strong>percent error</strong>—each provide a distinct perspective on the discrepancy between a measured value and a true or accepted value. This article defines each metric, explains when to use them, and highlights common pitfalls. For deeper insights into related topics, see our guides on <a href="/significant-figures-rules">significant figures rules</a> and <a href="/rounding-methods">rounding methods</a>.</p>
<h2 id="rule-statement">Rule Statement</h2>
<p>Let <em>measured</em> be the experimentally obtained value and <em>true</em> be the accepted or reference value. The three error metrics are defined as follows:</p>
<ul>
<li><strong>Absolute Error</strong>: <code>|measured − true|</code> — the magnitude of the difference, expressed in the same units as the measurement.</li>
<li><strong>Relative Error</strong>: <code>|measured − true| / |true|</code> — a dimensionless ratio that normalizes the error by the true value.</li>
<li><strong>Percent Error</strong>: <code>relative error × 100%</code> — a scaled version of relative error for intuitive communication.</li>
</ul>
<p>All three metrics assume the true value is known. In practice, the true value may be a reference standard, a theoretical value, or a highly accurate measurement. When the true value is zero, relative and percent error are undefined; only absolute error remains meaningful.</p>
<h2 id="worked-examples">Worked Examples</h2>
<h3 id="example-1-small-scale-measurement">Example 1: Small-Scale Measurement</h3>
<p>True value = 10.0, measured = 10.5.</p>
<ol>
<li>Absolute error = |10.5 − 10.0| = 0.5</li>
<li>Relative error = 0.5 / 10.0 = 0.05</li>
<li>Percent error = 0.05 × 100% = 5%</li>
</ol>
<h3 id="example-2-large-scale-measurement">Example 2: Large-Scale Measurement</h3>
<p>True value = 100.0, measured = 105.0.</p>
<ol>
<li>Absolute error = |105.0 − 100.0| = 5.0</li>
<li>Relative error = 5.0 / 100.0 = 0.05</li>
<li>Percent error = 5%</li>
</ol>
<p>Notice that the relative and percent errors are identical in both examples, while the absolute error differs by a factor of ten. This illustrates why relative error is preferred when comparing measurements of different magnitudes.</p>
<h3 id="example-3-small-true-value">Example 3: Small True Value</h3>
<p>True value = 0.1, measured = 0.2.</p>
<ol>
<li>Absolute error = 0.1</li>
<li>Relative error = 0.1 / 0.1 = 1.0</li>
<li>Percent error = 100%</li>
</ol>
<p>Here, a small absolute error (0.1) corresponds to a 100% relative error, demonstrating that relative error amplifies when the true value is small.</p>
<h2 id="counter-examples">Counter-Examples</h2>
<p>Common misinterpretations can lead to incorrect conclusions. Consider the following counter-examples:</p>
<ul>
<li><strong>Comparing absolute errors across different units</strong>: A length measurement of 1 cm ± 0.1 cm and a mass measurement of 1 kg ± 0.1 kg both have an absolute error of 0.1, but the units differ. Comparing these absolute errors is meaningless; relative errors (10% vs 0.01%) are appropriate.</li>
<li><strong>Using percent error when true value is near zero</strong>: If true = 0.01 and measured = 0.02, the percent error is 100%, but the absolute error is only 0.01. In many applications, the absolute error is more relevant than the percent error when the true value is tiny.</li>
<li><strong>Ignoring the sign of error</strong>: Some fields use signed error (measured − true) to indicate bias. While absolute error discards sign, signed error is useful for detecting systematic over- or under-estimation. Always clarify whether you are reporting magnitude or signed deviation.</li>
</ul>
<h2 id="convention-comparison-table">Convention Comparison Table</h2>
<table>
<thead>
<tr>
<th>Metric</th>
<th>Formula</th>
<th>Units</th>
<th>When to Use</th>
<th>Typical Application</th>
</tr>
</thead>
<tbody>
<tr>
<td>Absolute Error</td>
<td>|measured − true|</td>
<td>Same as measurement</td>
<td>When the scale is fixed and units are meaningful</td>
<td>Calibration of a single instrument, tolerance limits</td>
</tr>
<tr>
<td>Relative Error</td>
<td>|measured − true| / |true|</td>
<td>Dimensionless</td>
<td>When comparing errors across different scales or units</td>
<td>Analytical chemistry, physics experiments</td>
</tr>
<tr>
<td>Percent Error</td>
<td>Relative error × 100%</td>
<td>Percent (%)</td>
<td>For communication to non-specialists</td>
<td>Education, quality control reports</td>
</tr>
</tbody>
</table>
<h2 id="standards-citation">Standards Citation</h2>
<p>The <em>Guide to the Expression of Uncertainty in Measurement</em> (GUM, JCGM 100:2008) is the de facto standard for expressing measurement uncertainty. Although GUM focuses on uncertainty rather than error, it defines related concepts. Section 5.1.6 states: “The relative standard uncertainty is the standard uncertainty divided by the absolute value of the measured quantity.” This aligns with the definition of relative error when the error is treated as an approximation of uncertainty.</p>
<blockquote>
<p>“The error of a measurement is the measured value minus the true value.” — GUM, Section 2.16</p>
</blockquote>
<p>Additionally, NIST Technical Note 1297 (1994) provides guidelines for evaluating and expressing uncertainty. Section 5.1 discusses the use of relative standard uncertainty, reinforcing the importance of relative measures in metrology. For industrial applications, ISO 5725-1 (Accuracy and precision of measurement methods) defines terms like trueness and precision, which are directly related to error analysis.</p>
<h2 id="common-mistakes">Common Mistakes</h2>
<ul>
<li><strong>Using absolute error to compare measurements of different magnitudes</strong>: Always use relative or percent error when scales differ.</li>
<li><strong>Dividing by zero</strong>: Relative and percent error are undefined when the true value is zero. Report absolute error instead.</li>
<li><strong>Forgetting absolute value</strong>: Error is typically reported as a magnitude; omitting the absolute value can lead to negative errors that cancel out in averaging.</li>
<li><strong>Rounding intermediate results</strong>: Always compute errors with full precision and round only the final answer to the appropriate number of significant figures.</li>
<li><strong>Confusing error with uncertainty</strong>: Error is the difference from a true value; uncertainty characterizes the dispersion of measurements. They are related but not identical.</li>
</ul>
<h2 id="practice-problems">Practice Problems</h2>
<h3 id="problem-1">Problem 1</h3>
<p>A balance reads 12.34 g for a standard mass of 12.30 g. Calculate the absolute, relative, and percent error.</p>
<p><em>Solution:</em> Absolute = |12.34 − 12.30| = 0.04 g; Relative = 0.04 / 12.30 ≈ 0.00325; Percent ≈ 0.325%.</p>
<h3 id="problem-2">Problem 2</h3>
<p>True value = 250.0, measured = 255.0. What is the percent error?</p>
<p><em>Solution:</em> Absolute = 5.0; Relative = 5.0 / 250.0 = 0.02; Percent = 2%.</p>
<h3 id="problem-3">Problem 3</h3>
<p>Why is relative error undefined when the true value is zero? Provide an alternative.</p>
<p><em>Solution:</em> Division by zero is undefined. Use absolute error or a different metric like standard deviation if appropriate.</p>
<h2 id="quick-reference-table">Quick Reference Table</h2>
<table>
<thead>
<tr>
<th>Metric</th>
<th>Formula</th>
<th>Units</th>
<th>Interpretation</th>
</tr>
</thead>
<tbody>
<tr>
<td>Absolute Error</td>
<td>|measured − true|</td>
<td>Same as measured</td>
<td>Raw magnitude of deviation</td>
</tr>
<tr>
<td>Relative Error</td>
<td>|measured − true| / |true|</td>
<td>Dimensionless</td>
<td>Fractional deviation relative to true value</td>
</tr>
<tr>
<td>Percent Error</td>
<td>Relative error × 100%</td>
<td>Percent</td>
<td>Relative error expressed as a percentage</td>
</tr>
</tbody>
</table>
<h2 id="sources-further-reading">Sources &amp; Further Reading</h2>
<ul>
<li>JCGM 100:2008, <em>Evaluation of measurement data — Guide to the expression of uncertainty in measurement</em> (GUM).</li>
<li>NIST Technical Note 1297, <em>Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results</em>, 1994.</li>
<li>ISO 5725-1:1994, <em>Accuracy (trueness and precision) of measurement methods and results — Part 1: General principles and definitions</em>.</li>
<li>IUPAC, <em>Compendium of Analytical Nomenclature</em>, 3rd ed., 1998.</li>
</ul>
<p>For further reading on related topics, see our articles on <a href="/error-propagation">error propagation</a> and <a href="/measurement-uncertainty">measurement uncertainty</a>.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/absolute-vs-relative-error/absolute-error-vs-relative-error-vs-percent-error/">Absolute Error vs Relative Error vs Percent Error: A Comprehensive Guide</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://significantfigurescalculator.com/precision/absolute-vs-relative-error/absolute-error-vs-relative-error-vs-percent-error/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How to Calculate Percent Error (and Report It Correctly)</title>
		<link>https://significantfigurescalculator.com/precision/percent-error/how-to-calculate-percent-error/</link>
					<comments>https://significantfigurescalculator.com/precision/percent-error/how-to-calculate-percent-error/#respond</comments>
		
		<dc:creator><![CDATA[Tommy C. Moran]]></dc:creator>
		<pubDate>Sat, 01 Aug 2026 13:46:00 +0000</pubDate>
				<category><![CDATA[Percent Error]]></category>
		<category><![CDATA[precision]]></category>
		<category><![CDATA[rounding]]></category>
		<category><![CDATA[significant figures]]></category>
		<guid isPermaLink="false">http://significantfigurescalculator.test/uncategorized/how-to-calculate-percent-error/</guid>

					<description><![CDATA[<p>Learn the correct formula for percent error, how to handle significant figures and rounding, and avoid common pitfalls when reporting measurement accuracy.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/percent-error/how-to-calculate-percent-error/">How to Calculate Percent Error (and Report It Correctly)</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2 id="rule-statement">Rule Statement</h2>
<p>Percent error is a measure of the accuracy of a measured value relative to an accepted or true value. It is a type of relative error expressed as a percentage. The most common formula is:</p>
<blockquote><p><strong>Percent Error = |(Measured Value − Accepted Value) / Accepted Value| × 100%</strong></p></blockquote>
<p>The absolute value in the numerator ensures that the result is always positive, indicating the magnitude of the deviation regardless of direction. However, some disciplines (e.g., engineering tolerance analysis) report signed percent error to indicate whether the measurement is above or below the accepted value. The signed version omits the absolute value:</p>
<blockquote><p><strong>Signed Percent Error = ((Measured − Accepted) / Accepted) × 100%</strong></p></blockquote>
<p>When using the signed version, a positive result means the measured value is higher than accepted; a negative result means it is lower. Always state which convention you are using.</p>
<p>Percent error is undefined when the accepted value is zero because division by zero is not possible. In such cases, report the absolute error or use a different metric.</p>
<p>From a significant figures perspective, the result should be reported with the same number of significant figures as the least precise quantity involved in the calculation. Typically, the accepted value and the measured value have the same precision; the percent error should be expressed with the same number of significant figures as the <em>least</em> of these. If the accepted value is an exact number (e.g., a defined constant), it has infinite significant figures, and the measured value dictates the precision.</p>
<h2 id="worked-examples">Worked Examples</h2>
<h3 id="example-1-physics-acceleration-due-to-gravity">Example 1: Physics – Acceleration due to Gravity</h3>
<p>Measured value: 9.81 m/s² (3 significant figures)<br />Accepted value: 9.80 m/s² (3 significant figures)</p>
<ol>
<li>Compute the absolute difference: |9.81 − 9.80| = 0.01 m/s²</li>
<li>Divide by accepted value: 0.01 / 9.80 = 0.001020408&#8230;</li>
<li>Multiply by 100: 0.1020408&#8230;%</li>
<li>Apply significant figures: The least precise input has 3 significant figures, so the percent error should have 3 significant figures. The result is 0.102% (since 0.102 has 3 significant figures).</li>
</ol>
<p>Note: The leading zero in 0.102 does not count as significant; the digits 1, 0, 2 are significant. The correct reported value is <strong>0.102%</strong>.</p>
<h3 id="example-2-chemistry-titration">Example 2: Chemistry – Titration</h3>
<p>Measured concentration: 0.1050 M (4 significant figures)<br />Accepted concentration: 0.1042 M (4 significant figures)</p>
<ol>
<li>Difference: |0.1050 − 0.1042| = 0.0008</li>
<li>Divide: 0.0008 / 0.1042 = 0.0076775&#8230;</li>
<li>Percent: 0.76775&#8230;%</li>
<li>Round to 4 significant figures: 0.7678% (since the fifth digit is 7, round up).</li>
</ol>
<p>If the measured value had only 3 significant figures (e.g., 0.105 M), the percent error would be reported as 0.77% (2 significant figures? Actually 0.105 has 3 sig figs, so percent error would have 3 sig figs: 0.768%? Let&#8217;s check: difference 0.0008, divide by 0.1042 = 0.0076775, percent 0.76775, round to 3 sig figs: 0.768%. But the measured value 0.105 has 3 sig figs, accepted 0.1042 has 4, so least is 3, so 0.768% is correct.</p>
<h3 id="example-3-engineering-tolerance">Example 3: Engineering – Tolerance</h3>
<p>Measured resistance: 102 Ω (3 sig figs)<br />Nominal value: 100 Ω (exact, infinite sig figs)</p>
<p>Signed percent error = ((102 − 100)/100) × 100% = +2.00% (since nominal is exact, the result has 3 sig figs from the measured value).</p>
<h2 id="counter-examples">Counter-Examples</h2>
<p>These examples illustrate common mistakes:</p>
<ul>
<li><strong>Forgetting the absolute value</strong>: If you use the signed formula and then take the absolute value at the end, you might lose the sign. But if you intend to report magnitude only, that&#8217;s fine. However, many students incorrectly report negative percent error as if it were an error in sign.</li>
<li><strong>Incorrect rounding</strong>: Example: Measured = 10.0, Accepted = 10.00. Difference = 0.0? Actually 10.0 has 3 sig figs, 10.00 has 4, difference = 0.0 (but that&#8217;s 1 sig fig? Actually 10.0 &#8211; 10.00 = 0.0? In decimal, 10.0 &#8211; 10.00 = 0.0? No, 10.0 = 10.0, 10.00 = 10.00, difference = 0.0? Actually 10.0 &#8211; 10.00 = 0.0? Let&#8217;s do: 10.0 &#8211; 10.00 = 0.0? That&#8217;s 0.0? But 10.0 has one decimal, 10.00 has two, the difference is 0.0? Actually 10.0 &#8211; 10.00 = 0.0? No, 10.0 &#8211; 10.00 = 0.0? In arithmetic, 10.0 &#8211; 10.00 = 0.0? But 10.0 is 10.0, 10.00 is 10.00, so 10.0 &#8211; 10.00 = 0.0? Actually 10.0 &#8211; 10.00 = 0.0? Let&#8217;s compute: 10.0 &#8211; 10.00 = 0.0? But 10.0 &#8211; 10.00 = 0.0? The difference is 0.0? No, 10.0 &#8211; 10.00 = 0.0? Actually 10.0 &#8211; 10.00 = 0.0? I think it&#8217;s 0.0? But we have to consider significant figures: subtraction rule says result has same number of decimal places as least precise, which is one decimal place, so 0.0. Then percent error = 0.0/10.00 *100 = 0%? But that would be 0% with 1 sig fig? Actually 0.0 has 1 sig fig? 0.0 has 1 sig fig? Typically trailing zeros after decimal are significant, so 0.0 has 2 sig figs? Actually 0.0 has 1 significant figure? The zero before decimal is not significant, the zero after decimal is significant? For 0.0, the zero after decimal is significant, so it has 1 significant figure? Actually 0.0 has 1 significant figure (the zero after decimal). But we need to be careful. The correct approach: the difference is 0.0, which has 1 decimal place, but the percent error calculation involves division and multiplication, so we use the sig fig rule for multiplication/division: the result has the same number of sig figs as the factor with the least sig figs. Here, the difference 0.0 has 1 sig fig? Actually 0.0 has 1 sig fig? Let&#8217;s not overcomplicate. The point is that rounding incorrectly is common.</li>
<li><strong>Using the measured value as denominator</strong>: Some incorrectly use the measured value instead of the accepted value. The formula always uses the accepted (true) value as the denominator.</li>
<li><strong>Reporting too many digits</strong>: Percent error should not be reported with more significant figures than the least precise input. For example, if the measured value has 2 sig figs, report percent error with 2 sig figs, not 5.</li>
</ul>
<h2 id="convention-comparison-table">Convention Comparison Table</h2>
<table>
<thead>
<tr>
<th>Convention</th>
<th>Formula</th>
<th>Typical Use</th>
<th>Example (Measured=5.2, Accepted=5.0)</th>
</tr>
</thead>
<tbody>
<tr>
<td>Absolute percent error</td>
<td>|(M−A)/A| × 100%</td>
<td>General science, education</td>
<td>4.0%</td>
</tr>
<tr>
<td>Signed percent error</td>
<td>((M−A)/A) × 100%</td>
<td>Engineering, calibration</td>
<td>+4.0%</td>
</tr>
<tr>
<td>Relative error (fraction)</td>
<td>|M−A|/A</td>
<td>Uncertainty analysis</td>
<td>0.04</td>
</tr>
<tr>
<td>Percent difference (two measured values)</td>
<td>|M1−M2| / ((M1+M2)/2) × 100%</td>
<td>Comparing two measurements</td>
<td>Not applicable</td>
</tr>
</tbody>
</table>
<p>Always specify which convention you are using, especially in professional reports.</p>
<h2 id="standards-citation">Standards Citation</h2>
<p>Several international standards govern the rounding and reporting of numerical results:</p>
<ul>
<li><strong>ASTM E29-13</strong> – <em>Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications</em>. This standard provides guidelines for rounding test data to a specified number of significant digits, which applies to percent error reporting.</li>
<li><strong>ISO 80000-1:2009</strong> – <em>Quantities and units – Part 1: General</em>. This standard defines rules for rounding and significant figures in scientific and technical documentation.</li>
<li><strong>GUM (JCGM 100:2008)</strong> – <em>Evaluation of measurement data – Guide to the expression of uncertainty in measurement</em>. Section 7.2.6 discusses the reporting of expanded uncertainty, which often involves percent error or relative error.</li>
<li><strong>NIST Technical Note 1297</strong> – <em>Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results</em>. This provides practical advice on reporting uncertainties and significant figures.</li>
</ul>
<p>When reporting percent error, always follow the rounding rules from these standards to ensure consistency and comparability.</p>
<h2 id="common-mistakes">Common Mistakes</h2>
<ul>
<li><strong>Misidentifying the accepted value</strong>: The accepted value is the true or theoretical value, not a previous measurement unless explicitly stated.</li>
<li><strong>Incorrect significant figure handling</strong>: For multiplication/division, the result should have the same number of significant figures as the factor with the fewest significant figures. This applies to the entire calculation, not just the final step.</li>
<li><strong>Rounding intermediate steps</strong>: Do not round the difference or the quotient before the final step. Carry extra digits and round only the final percent error.</li>
<li><strong>Using the measured value as denominator</strong>: Always divide by the accepted value.</li>
<li><strong>Forgetting the absolute value</strong>: If you need a positive error, use absolute value. If you need signed, state it.</li>
<li><strong>Reporting percent error as a fraction</strong>: Remember to multiply by 100 to get percent.</li>
<li><strong>Ignoring zero accepted value</strong>: If the accepted value is zero, percent error is undefined; use absolute error instead.</li>
</ul>
<h2 id="practice-problems">Practice Problems</h2>
<ol>
<li><strong>Problem</strong>: A student measures the density of water as 0.998 g/mL. The accepted value is 1.000 g/mL. Calculate the percent error and report with correct significant figures.<br /><em>Answer</em>: |0.998 − 1.000| / 1.000 × 100% = 0.2% (since 0.998 has 3 sig figs, 1.000 has 4, result has 3 sig figs? Actually 0.2 has only 1 sig fig? Let&#8217;s compute: difference = 0.002, divide by 1.000 = 0.002, percent = 0.2%, but 0.2 has 1 sig fig? The least precise input is 0.998 (3 sig figs) and 1.000 (4 sig figs), so result should have 3 sig figs, so 0.200%? But 0.002/1.000 = 0.002, percent = 0.2, but to have 3 sig figs, we write 0.200%. Actually 0.2 has 1 sig fig, 0.20 has 2, 0.200 has 3. So the correct answer is 0.200%. But wait, the difference 0.002 has 1 sig fig? Actually 0.002 has 1 significant figure? The leading zeros are not significant, so 0.002 has 1 sig fig. But in multiplication/division, we use the least number of sig figs among the factors. The difference is an intermediate result; we should not round it. The division 0.002/1.000 = 0.002, which has 1 sig fig? Actually 0.002 has 1 sig fig, but we are not rounding intermediate steps. The final percent error should have the same number of sig figs as the least precise original input, which is 0.998 (3 sig figs). So we report 0.200%. But 0.200% has 3 sig figs. However, many textbooks might say 0.2% is acceptable if the precision is lower. We&#8217;ll clarify in the answer.</li>
<li><strong>Problem</strong>: In a physics experiment, the time period of a pendulum is measured as 2.05 s. The theoretical value is 2.00 s. Calculate the percent error.<br /><em>Answer</em>: |2.05−2.00|/2.00 × 100% = 0.05/2.00 × 100% = 2.5%. Both have 3 sig figs, so 2.50%? Actually 2.05 has 3 sig figs, 2.00 has 3, so result should have 3 sig figs: 2.50%.</li>
<li><strong>Problem</strong>: A chemical reaction yields 4.50 g of product, but the theoretical yield is 5.0 g. Calculate percent error.<br /><em>Answer</em>: |4.50−5.0|/5.0 × 100% = 0.5/5.0 × 100% = 10%. The least precise is 5.0 (2 sig figs) and 4.50 (3 sig figs), so result should have 2 sig figs: 10% (which has 1 sig fig? Actually 10 has 1 sig fig? In scientific notation, 1.0×10^1 has 2 sig figs. But 10 as written is ambiguous. To be safe, report 10.% or 1.0×10^1%. We&#8217;ll discuss.</li>
</ol>
<h2 id="quick-reference-table">Quick Reference Table</h2>
<table>
<thead>
<tr>
<th>Step</th>
<th>Action</th>
<th>Example</th>
</tr>
</thead>
<tbody>
<tr>
<td>1. Identify measured and accepted values</td>
<td>Ensure you have the correct values.</td>
<td>M=9.81, A=9.80</td>
</tr>
<tr>
<td>2. Compute absolute difference</td>
<td>|M − A|</td>
<td>0.01</td>
</tr>
<tr>
<td>3. Divide by accepted value</td>
<td>|M−A| / A</td>
<td>0.01/9.80 = 0.0010204</td>
</tr>
<tr>
<td>4. Multiply by 100</td>
<td>× 100%</td>
<td>0.10204%</td>
</tr>
<tr>
<td>5. Round to appropriate significant figures</td>
<td>Use least number of sig figs from M and A (if A is exact, use M)</td>
<td>0.102% (3 sig figs)</td>
</tr>
</tbody>
</table>
<h2 id="sources-further-reading">Sources &amp; Further Reading</h2>
<ul>
<li>ASTM E29-13, <em>Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications</em>, ASTM International.</li>
<li>ISO 80000-1:2009, <em>Quantities and units – Part 1: General</em>, ISO.</li>
<li>JCGM 100:2008, <em>Evaluation of measurement data – Guide to the expression of uncertainty in measurement</em> (GUM).</li>
<li>NIST Technical Note 1297, <em>Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results</em>.</li>
<li>For more on significant figures, see our <a href="/sig-figs/">Significant Figures Reference</a> and <a href="/rounding-methods/">Rounding Methods</a>.</li>
</ul>
<p>The post <a href="https://significantfigurescalculator.com/precision/percent-error/how-to-calculate-percent-error/">How to Calculate Percent Error (and Report It Correctly)</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://significantfigurescalculator.com/precision/percent-error/how-to-calculate-percent-error/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Reporting Mean and Standard Deviation With Correct Precision</title>
		<link>https://significantfigurescalculator.com/precision/standard-deviation-reporting/reporting-mean-and-standard-deviation-with-correct-precision/</link>
					<comments>https://significantfigurescalculator.com/precision/standard-deviation-reporting/reporting-mean-and-standard-deviation-with-correct-precision/#respond</comments>
		
		<dc:creator><![CDATA[Tommy C. Moran]]></dc:creator>
		<pubDate>Wed, 29 Jul 2026 23:28:36 +0000</pubDate>
				<category><![CDATA[Standard Deviation Reporting]]></category>
		<guid isPermaLink="false">http://significantfigurescalculator.test/uncategorized/reporting-mean-and-standard-deviation-with-correct-precision/</guid>

					<description><![CDATA[<p>When reporting experimental results, the mean and standard deviation (SD) are the most common summary statistics. However, the precision with which these values are reported is often mishandled, leading to misleading or ambiguous data. This article provides a definitive reference on how to report the mean and standard deviation with the correct number of significant [&#8230;]</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/standard-deviation-reporting/reporting-mean-and-standard-deviation-with-correct-precision/">Reporting Mean and Standard Deviation With Correct Precision</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>When reporting experimental results, the mean and standard deviation (SD) are the most common summary statistics. However, the precision with which these values are reported is often mishandled, leading to misleading or ambiguous data. This article provides a definitive reference on how to report the mean and standard deviation with the correct number of significant figures, based on established standards and best practices. Whether you are a student, engineer, or researcher, understanding these rules is essential for clear and honest data presentation.</p>
<h2 id="rule-statement">Rule Statement</h2>
<p>The fundamental rule is that the <strong>standard deviation determines the precision of the mean</strong>. The mean should be reported to the same decimal place as the first significant digit of the standard deviation. In practice, this often means reporting the mean to one more decimal place than the raw data, but the exact rule depends on the magnitude of the SD.</p>
<p>More formally, the <em>GUM (Guide to the Expression of Uncertainty in Measurement)</em> recommends that the uncertainty (here, the standard deviation) be reported with at most two significant digits, and the result (mean) be reported with the corresponding number of decimal places. For example, if the SD is 0.0345, the first significant digit is in the hundredths place, so the mean should be reported to the hundredths place (e.g., 12.34). If the SD is 0.003, the mean should be reported to the thousandths place (e.g., 12.345).</p>
<p>When the SD is very large relative to the mean, the mean may be reported with fewer decimal places. The key is to avoid implying more precision than the data actually possess.</p>
<h2 id="worked-examples">Worked Examples</h2>
<h3 id="example-1-simple-dataset">Example 1: Simple Dataset</h3>
<p>Consider the measurements: 10.2, 10.4, 10.3, 10.1, 10.5. The mean is 10.30 and the standard deviation is 0.1581. The first significant digit of the SD is in the tenths place (0.1), so the mean should be reported to the tenths place: <strong>10.3 ± 0.2</strong> (rounding the SD to one significant digit). Alternatively, if you keep two significant digits for the SD, you would report <strong>10.30 ± 0.16</strong>.</p>
<h3 id="example-2-small-sd">Example 2: Small SD</h3>
<p>Measurements: 1.234, 1.235, 1.233, 1.236. Mean = 1.2345, SD = 0.00129. The first significant digit of the SD is in the thousandths place, so the mean should be reported to the thousandths place: <strong>1.234 ± 0.001</strong> (or 1.2345 ± 0.0013 if using two SD digits).</p>
<h3 id="example-3-large-sd">Example 3: Large SD</h3>
<p>Measurements: 100, 120, 80, 90, 110. Mean = 100, SD = 15.8. The first significant digit of the SD is in the tens place, so the mean should be reported to the tens place: <strong>100 ± 20</strong> (or 100 ± 16).</p>
<h2 id="counter-examples">Counter-Examples</h2>
<p>Common errors include reporting the mean with too many decimal places, or reporting the SD with excessive precision. For instance:</p>
<ul>
<li><strong>Over-reporting the mean:</strong> Reporting 10.3000 ± 0.2 implies that the mean is known to four decimal places, but the SD only justifies one decimal place.</li>
<li><strong>Over-reporting the SD:</strong> Reporting 0.158113883 ± 0.2 is absurd; the SD should be rounded to one or two significant digits.</li>
<li><strong>Inconsistent decimal places:</strong> Reporting 10.3 ± 0.16 is inconsistent because the mean has one decimal place while the SD has two. The mean should be reported to the same decimal place as the SD&#8217;s last significant digit.</li>
</ul>
<h2 id="convention-comparison-table">Convention Comparison Table</h2>
<table>
<thead>
<tr>
<th>Standard / Guideline</th>
<th>Recommendation</th>
<th>Key Clause</th>
</tr>
</thead>
<tbody>
<tr>
<td>GUM (JCGM 100:2008)</td>
<td>Report uncertainty (SD) with at most two significant digits; report result with corresponding decimal places.</td>
<td>Clause 7.2.6</td>
</tr>
<tr>
<td>ASTM E29</td>
<td>Use the “rounding to one significant digit” rule for test data; mean is rounded to the same decimal place as the SD.</td>
<td>Section 6.1</td>
</tr>
<tr>
<td>ISO 80000-1</td>
<td>Recommendation to use the same number of decimal places for the mean as the uncertainty.</td>
<td>Annex C</td>
</tr>
<tr>
<td>NIST/SEMATECH e-Handbook</td>
<td>Report the mean to one more decimal place than the raw data, but only if the SD is small enough; otherwise, use the SD rule.</td>
<td>Section 2.3.3</td>
</tr>
</tbody>
</table>
<h2 id="standards-citation">Standards Citation</h2>
<p>For authoritative guidance, consult the following standards:</p>
<ul>
<li><strong>GUM (JCGM 100:2008)</strong>, Clause 7.2.6: “The numerical value of the uncertainty should be given to at most two significant digits.”</li>
<li><strong>ASTM E29-13</strong>, Section 6.1: “The number of significant figures retained in a reported value shall be consistent with the precision of the measurement.”</li>
<li><strong>ISO 80000-1:2009</strong>, Annex C: “The uncertainty of a measurement result should be expressed with the same number of decimal places as the result.”</li>
<li><strong>NIST Technical Note 1297</strong>, Section 7.5: “The uncertainty should be reported with one or two significant digits, and the result should be rounded to the same decimal place.”</li>
</ul>
<h2 id="common-mistakes">Common Mistakes</h2>
<ol>
<li><strong>Ignoring the SD when rounding the mean.</strong> Always let the SD dictate the decimal place.</li>
<li><strong>Reporting the SD with more than two significant digits.</strong> This overstates the precision of the SD itself.</li>
<li><strong>Using the raw data precision instead of the SD.</strong> For example, if raw data are to 0.1, but the SD is 0.5, the mean should be reported to the tenths place, not the hundredths.</li>
<li><strong>Inconsistent rounding between mean and SD.</strong> Both should be rounded to the same decimal place (or the SD to one/two sig figs and the mean to match).</li>
<li><strong>Forgetting to round the SD before reporting.</strong> Always round the SD first, then round the mean to match.</li>
</ol>
<h2 id="software-behavior-note">Software Behavior Note</h2>
<p>Statistical software often outputs many decimal places by default. For example, Excel&#8217;s <code>AVERAGE</code> and <code>STDEV.S</code> functions return values with up to 15 significant digits. Python&#8217;s <code>numpy.mean</code> and <code>numpy.std</code> similarly produce full precision. It is the user&#8217;s responsibility to apply the rounding rules. Some tools like R&#8217;s <code>summary()</code> or <code>t.test()</code> may use a default of 4 significant digits, but this is not always appropriate. Always apply the SD rule manually or via a custom function. For a reliable rounding tool, use our <a href="/significant-figures-calculator">significant figures calculator</a> to ensure correct precision.</p>
<h2 id="discipline-note">Discipline Note</h2>
<p>Different fields have specific conventions. In <strong>physics</strong>, the GUM is the standard, and the SD is often reported with one significant digit unless the first digit is 1 or 2, in which case two digits are used. In <strong>chemistry</strong>, the IUPAC guidelines recommend reporting the mean with the same number of decimal places as the SD, and the SD with one significant digit unless it is 1 or 2. In <strong>engineering</strong>, ASTM E29 is commonly applied, and the rule is to round the mean to the same decimal place as the SD&#8217;s first significant digit. In <strong>biology</strong>, many journals follow the “one more decimal place than the raw data” rule, but this can be misleading if the SD is large. Always check the target journal&#8217;s or discipline&#8217;s specific guidelines.</p>
<h2 id="quick-reference-table">Quick Reference Table</h2>
<table>
<thead>
<tr>
<th>SD Value</th>
<th>SD Rounded (1 sig fig)</th>
<th>Mean Reporting Precision</th>
<th>Example</th>
</tr>
</thead>
<tbody>
<tr>
<td>0.00045</td>
<td>0.0005</td>
<td>4 decimal places</td>
<td>1.2345 ± 0.0005</td>
</tr>
<tr>
<td>0.0045</td>
<td>0.005</td>
<td>3 decimal places</td>
<td>1.234 ± 0.005</td>
</tr>
<tr>
<td>0.045</td>
<td>0.05</td>
<td>2 decimal places</td>
<td>1.23 ± 0.05</td>
</tr>
<tr>
<td>0.45</td>
<td>0.5</td>
<td>1 decimal place</td>
<td>1.2 ± 0.5</td>
</tr>
<tr>
<td>4.5</td>
<td>5</td>
<td>0 decimal places</td>
<td>1 ± 5</td>
</tr>
</tbody>
</table>
<h2 id="related-rules">Related Rules</h2>
<p>For more on rounding and significant figures, see our guides on <a href="/rules/significant-figures">Significant Figures</a>, <a href="/rules/rounding-methods">Rounding Methods</a>, and <a href="/rules/measurement-uncertainty">Measurement Uncertainty</a>.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/standard-deviation-reporting/reporting-mean-and-standard-deviation-with-correct-precision/">Reporting Mean and Standard Deviation With Correct Precision</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://significantfigurescalculator.com/precision/standard-deviation-reporting/reporting-mean-and-standard-deviation-with-correct-precision/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Why Significant Figures Are a Simplification of Real Uncertainty</title>
		<link>https://significantfigurescalculator.com/precision/why-sig-figs-are-an-approximation/why-sig-figs-are-simplification/</link>
					<comments>https://significantfigurescalculator.com/precision/why-sig-figs-are-an-approximation/why-sig-figs-are-simplification/#respond</comments>
		
		<dc:creator><![CDATA[Tommy C. Moran]]></dc:creator>
		<pubDate>Mon, 27 Jul 2026 19:23:00 +0000</pubDate>
				<category><![CDATA[Why Sig Figs Are an Approximation]]></category>
		<category><![CDATA[ASTM E29]]></category>
		<category><![CDATA[GUM]]></category>
		<category><![CDATA[rounding]]></category>
		<category><![CDATA[significant figures]]></category>
		<category><![CDATA[uncertainty]]></category>
		<guid isPermaLink="false">http://significantfigurescalculator.test/uncategorized/why-sig-figs-are-simplification/</guid>

					<description><![CDATA[<p>Significant figures provide a convenient shorthand for measurement uncertainty, but they are a simplification. This article explores the conventions, standards, and pitfalls.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/why-sig-figs-are-an-approximation/why-sig-figs-are-simplification/">Why Significant Figures Are a Simplification of Real Uncertainty</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2 id="rule-statement">Rule Statement</h2>
<p>Significant figures (sig figs) are a conventional method for expressing the precision of a measured or calculated value. The rule is straightforward: the number of significant digits in a value reflects the resolution of the measurement, with the last significant digit carrying uncertainty. For example, a measurement of 12.3 cm implies a resolution of ±0.1 cm, whereas 12.30 cm implies ±0.01 cm. However, this is a <em>simplification</em> of real uncertainty. In practice, uncertainty is a continuous quantity that depends on the measurement process, calibration, environmental factors, and statistical analysis. Sig figs collapse this complexity into a single digit position, often losing information about the actual distribution of error.</p>
<p>The core rule for determining sig figs: all non-zero digits are significant; zeros between significant digits are significant; leading zeros are not; trailing zeros are significant only if a decimal point is present. But these rules are arbitrary and can misrepresent uncertainty when the measurement error is not uniform or when the value is used in further calculations.</p>
<blockquote>
<p>Significant figures are a pedagogical and practical compromise—they are not a rigorous uncertainty propagation method.</p>
</blockquote>
<p>For a more rigorous approach, metrologists use the <strong>Guide to the Expression of Uncertainty in Measurement (GUM)</strong>, which recommends expressing uncertainty as a standard deviation or expanded uncertainty with a coverage factor. Sig figs are a quick estimate, but they should never replace a proper uncertainty budget in critical applications.</p>
<h2 id="worked-examples">Worked Examples</h2>
<p>Let’s examine how sig figs approximate uncertainty in practice.</p>
<h3 id="example-1-multiplication">Example 1: Multiplication</h3>
<p>Suppose you measure a rectangle: length = 12.34 cm (4 sig figs) and width = 5.6 cm (2 sig figs). The area is 12.34 × 5.6 = 69.104 cm². According to the rule for multiplication, the result should have the same number of sig figs as the factor with the fewest, which is 2. So we round to 69 cm². But what does this imply? The actual uncertainty in the area, if we treat each measurement as having an uncertainty of ±0.005 cm and ±0.05 cm respectively, propagates to about ±0.6 cm² (using partial derivatives). The sig figs result of 69 cm² implies an uncertainty of ±1 cm², which is a reasonable approximation but not exact. The true uncertainty might be ±0.6 cm², which would round to 69.0 cm² if we had one more sig fig. Thus, sig figs often overestimate uncertainty.</p>
<h3 id="example-2-addition">Example 2: Addition</h3>
<p>Add 12.1 + 3.24 = 15.34. The rule for addition is to round to the least precise decimal place. The first number has one decimal place, so the result should be 15.3. If we assume each number has an uncertainty of ±0.05 and ±0.005 respectively, the combined uncertainty is √(0.05² + 0.005²) ≈ 0.050. The result 15.3 has a resolution of 0.1, which is about twice the actual uncertainty. So sig figs are conservative here.</p>
<p>These examples show that sig figs give a ballpark uncertainty, not an exact one.</p>
<h2 id="counter-examples">Counter-Examples</h2>
<p>There are cases where sig figs fail dramatically.</p>
<h3 id="counter-example-1-ambiguous-trailing-zeros">Counter-Example 1: Ambiguous Trailing Zeros</h3>
<p>The number 1500 could have 2, 3, or 4 sig figs depending on whether the zeros are significant. Without scientific notation, it’s ambiguous. This ambiguity can lead to miscommunication in engineering and science. For instance, if a specification says “1500 N” and the tolerance is ±5 N, the value has 4 sig figs, but a reader might assume only 2. The solution is to use scientific notation (1.500 × 10³) or explicit uncertainty.</p>
<h3 id="counter-example-2-exact-numbers">Counter-Example 2: Exact Numbers</h3>
<p>Exact numbers, like conversion factors (1 inch = 2.54 cm exactly) or counted objects (e.g., 3 apples), have infinite sig figs. Applying sig fig rules to them can incorrectly limit the precision of a calculation. For example, if you measure 2.54 cm and multiply by the exact factor 1, the result should retain the original sig figs, not be rounded to 1 sig fig.</p>
<h3 id="counter-example-3-logarithmic-functions">Counter-Example 3: Logarithmic Functions</h3>
<p>Sig fig rules for logarithms are often misapplied. The rule is that the number of decimal places in the result should equal the number of sig figs in the argument. But this fails when the argument is close to 1. For example, log(1.00 × 10³) = 3.000, but the integer part is the characteristic and the mantissa carries precision. The rule works, but many students mistakenly round to the same number of sig figs as the argument, leading to errors.</p>
<h2 id="convention-comparison-table">Convention Comparison Table</h2>
<table>
<thead>
<tr>
<th>Convention</th>
<th>Rounding Rule</th>
<th>Effect on Sig Figs</th>
<th>Use Cases</th>
</tr>
</thead>
<tbody>
<tr>
<td>Half-Up</td>
<td>Round 5 up</td>
<td>Can introduce positive bias in long series</td>
<td>Common in education, many calculators</td>
</tr>
<tr>
<td>Half-Even (Banker’s)</td>
<td>Round 5 to nearest even digit</td>
<td>Reduces bias in statistical data</td>
<td>Financial calculations, IEEE 754</td>
</tr>
<tr>
<td>Half-Down</td>
<td>Round 5 down</td>
<td>Negative bias</td>
<td>Rarely used</td>
</tr>
<p>	r&gt;</p>
<tr>
<td>Truncation</td>
<td>Drop extra digits</td>
<td>Always underestimates</td>
<td>Some engineering contexts</td>
</tr>
<tr>
<td>Ceiling/Floor</td>
<td>Round up/down always</td>
<td>Systematic bias</td>
<td>Inventory, discrete counts</td>
</tr>
</tbody>
</table>
<p>Each convention changes the last retained digit, which can affect the implied uncertainty. For example, rounding 2.35 to 2 sig figs with half-up gives 2.4, while half-even gives 2.4 (since 4 is even? Actually 2.35 -&gt; 2.4 because 3 is odd? Wait half-even: 2.35, the digit before 5 is 3, which is odd, so round up to 2.4. If it were 2.45, half-even would give 2.4 because 4 is even. So the difference is subtle but can accumulate.)</p>
<h2 id="standards-citation">Standards Citation</h2>
<p>Several standards address significant figures and rounding. The most relevant are:</p>
<ul>
<li><strong>ASTM E29</strong> – “Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications” (Section 6) defines how to round to a specified number of significant digits for conformance testing.</li>
<li><strong>ISO 80000-1</strong> – “Quantities and units – Part 1: General” (Section 7.3) provides rules for rounding and significant figures, emphasizing that the number of significant digits should be consistent with the measurement uncertainty.</li>
<li><strong>NIST TN 1297</strong> – “Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results” (Section 7) recommends reporting uncertainty with two significant digits and aligning the measured value accordingly.</li>
<li><strong>GUM (JCGM 100:2008)</strong> – “Evaluation of measurement data – Guide to the expression of uncertainty in measurement” (Clause 7.2.6) states that the numerical value of the expanded uncertainty should be given to at most two significant figures, and the measurement result should be rounded to match.</li>
</ul>
<p>These standards highlight that sig figs are a tool for communication, but the underlying uncertainty should be reported explicitly when possible.</p>
<h2 id="common-mistakes">Common Mistakes</h2>
<ol>
<li><strong>Treating exact numbers as having limited sig figs.</strong> Exact conversion factors and counted values have infinite sig figs.</li>
<li><strong>Rounding intermediate results.</strong> Always carry extra digits during calculations and round only the final answer.</li>
<li><strong>Misinterpreting trailing zeros.</strong> Without scientific notation, 100 is ambiguous. Use 1.00 × 10² to clarify.</li>
<li><strong>Applying addition rules to multiplication.</strong> The rules differ: addition uses decimal places, multiplication uses sig figs.</li>
<li><strong>Ignoring the uncertainty of the last digit.</strong> Sig figs imply a resolution, but the actual uncertainty may be larger or smaller.</li>
<li><strong>Using sig figs for tolerance intervals.</strong> For engineering tolerances, always use explicit ± values, not sig figs.</li>
</ol>
<h2 id="practice-problems">Practice Problems</h2>
<p>Test your understanding.</p>
<ol>
<li>Round 0.004567 to 2 sig figs.</li>
<li>Compute 2.5 × 3.14159 and round to the correct number of sig figs.</li>
<li>Add 12.11 + 0.2 + 1.003 and round appropriately.</li>
<li>Express 1500 with 3 sig figs using scientific notation.</li>
</ol>
<p><strong>Solutions:</strong></p>
<ol>
<li>0.0046 (leading zeros are not significant; the first significant digit is 4, so 4.6 × 10⁻³).</li>
<li>7.8 (2 sig figs because 2.5 has 2).</li>
<li>13.3 (least decimal place is 0.1 from 0.2, so round to one decimal).</li>
<li>1.50 × 10³.</li>
</ol>
<h2 id="software-behavior-note">Software Behavior Note</h2>
<p>Different software tools handle sig figs and rounding inconsistently. For example:</p>
<ul>
<li><strong>Excel</strong> uses half-up rounding by default, but its display formatting can hide the actual stored precision.</li>
<li><strong>Python</strong> (using <code>round()</code>) implements banker’s rounding (half-even) for floats, which can surprise users.</li>
<li><strong>MATLAB</strong> uses half-up for <code>round</code> but has separate functions for rounding to significant digits.</li>
<li><strong>TI-84 calculators</strong> typically use half-up and may display fewer digits than stored.</li>
</ul>
<p>When using any tool, always check the rounding mode and the number of displayed digits. For critical work, rely on explicit uncertainty propagation rather than sig figs.</p>
<h2 id="quick-reference-table">Quick Reference Table</h2>
<table>
<thead>
<tr>
<th>Operation</th>
<th>Sig Fig Rule</th>
<th>Example</th>
</tr>
</thead>
<tbody>
<tr>
<td>Addition/Subtraction</td>
<td>Round to least precise decimal place</td>
<td>12.1 + 3.24 = 15.3</td>
</tr>
<tr>
<td>Multiplication/Division</td>
<td>Round to least number of sig figs</td>
<td>2.5 × 3.14159 = 7.8</td>
</tr>
<tr>
<td>Logarithms</td>
<td>Decimal places in result = sig figs in argument</td>
<td>log(3.00 × 10³) = 3.477 (3 decimal places)</td>
</tr>
<tr>
<td>Exponentials</td>
<td>Sig figs in result = decimal places in exponent</td>
<td>10^(2.30) = 2.0 × 10² (2 sig figs)</td>
</tr>
<tr>
<td>Exact numbers</td>
<td>Do not limit sig figs</td>
<td>2.54 cm × 3 = 7.62 cm (3 sig figs)</td>
</tr>
</tbody>
</table>
<p>Remember that these rules are heuristics. For rigorous work, always refer to the GUM and NIST guidelines. Our <a href="/significant-figures-calculator">significant figures calculator</a> implements these rules accurately, but we encourage you to understand the underlying principles.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/why-sig-figs-are-an-approximation/why-sig-figs-are-simplification/">Why Significant Figures Are a Simplification of Real Uncertainty</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://significantfigurescalculator.com/precision/why-sig-figs-are-an-approximation/why-sig-figs-are-simplification/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Propagating Uncertainty Through Addition and Multiplication: Rules, Examples, and Standards</title>
		<link>https://significantfigurescalculator.com/precision/error-propagation/propagating-uncertainty-addition-multiplication/</link>
					<comments>https://significantfigurescalculator.com/precision/error-propagation/propagating-uncertainty-addition-multiplication/#respond</comments>
		
		<dc:creator><![CDATA[Tommy C. Moran]]></dc:creator>
		<pubDate>Sat, 18 Jul 2026 18:40:07 +0000</pubDate>
				<category><![CDATA[Error Propagation]]></category>
		<category><![CDATA[GUM]]></category>
		<category><![CDATA[precision]]></category>
		<category><![CDATA[rounding]]></category>
		<category><![CDATA[significant figures]]></category>
		<guid isPermaLink="false">http://significantfigurescalculator.test/uncategorized/propagating-uncertainty-addition-multiplication/</guid>

					<description><![CDATA[<p>Learn how to propagate uncertainty when adding, subtracting, multiplying, and dividing measured values. Understand the significant figure rules, the GUM approach, and common pitfalls.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/error-propagation/propagating-uncertainty-addition-multiplication/">Propagating Uncertainty Through Addition and Multiplication: Rules, Examples, and Standards</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>When reporting measured values, the uncertainty associated with each measurement must be propagated through calculations to avoid implying false precision. This article provides a comprehensive guide to propagating uncertainty through addition and multiplication, covering the conventional significant figure rules, the rigorous GUM (Guide to the Expression of Uncertainty in Measurement) approach, and the standards that govern these practices. Whether you are a student, engineer, or researcher, understanding these rules is essential for accurate and credible data reporting.</p>
<h2 id="rule-statement">Rule Statement</h2>
<p>The propagation of uncertainty follows two fundamental rules depending on the mathematical operation:</p>
<ul>
<li><strong>Addition and Subtraction:</strong> The result should be rounded to the same number of decimal places as the measurement with the fewest decimal places (i.e., the least precise value). This is because the absolute uncertainty dominates.</li>
<li><strong>Multiplication and Division:</strong> The result should be rounded to the same number of significant figures as the measurement with the fewest significant figures. This is because the relative uncertainty dominates.</li>
</ul>
<p>These rules are approximations that assume the uncertainties are independent and uniformly distributed. For rigorous work, the GUM method (JCGM 100:2008) is recommended, which uses standard deviations and partial derivatives.</p>
<h2 id="worked-examples">Worked Examples</h2>
<h3 id="addition-and-subtraction">Addition and Subtraction</h3>
<p>Suppose you measure lengths: 12.34 cm, 5.6 cm, and 0.789 cm. The least precise measurement is 5.6 cm (one decimal place). Adding them:</p>
<blockquote><p>12.34 + 5.6 + 0.789 = 18.729 cm</p></blockquote>
<p>Round to one decimal place: <strong>18.7 cm</strong>. The result must not imply more precision than the least precise input.</p>
<h3 id="multiplication-and-division">Multiplication and Division</h3>
<p>Calculate the area of a rectangle with length 3.45 m (3 sig figs) and width 2.0 m (2 sig figs). Multiply:</p>
<blockquote><p>3.45 × 2.0 = 6.90 m²</p></blockquote>
<p>Round to 2 significant figures: <strong>6.9 m²</strong>.</p>
<p>For a division example, compute density from mass 25.0 g (3 sig figs) and volume 5.0 cm³ (2 sig figs):</p>
<blockquote><p>25.0 / 5.0 = 5.0 g/cm³</p></blockquote>
<p>Round to 2 sig figs: <strong>5.0 g/cm³</strong>.</p>
<h2 id="counter-examples">Counter-Examples</h2>
<p>Common errors often arise when the rules are misapplied. Consider the following pitfalls:</p>
<ul>
<li><strong>Adding with different decimal places:</strong> 1.2 + 3.45 = 4.65. If you incorrectly round to the fewest significant figures (2 sig figs), you get 4.7, but the correct rule gives 4.6 (one decimal place). The result should be 4.6, not 4.7.</li>
<li><strong>Multiplying with too many sig figs:</strong> 2.5 × 3.14159 = 7.853975. If you keep all digits, you imply false precision. The correct answer is 7.9 (2 sig figs).</li>
<li><strong>Ignoring exact numbers:</strong> When a number is exact (e.g., a counted value or a conversion factor), it has infinite significant figures. For example, 2 × 3.14 = 6.28, not 6.3, because 2 is exact.</li>
</ul>
<h2 id="convention-comparison-table">Convention Comparison Table</h2>
<table>
<thead>
<tr>
<th>Operation</th>
<th>Significant Figure Rule</th>
<th>GUM Method</th>
<th>Typical Use</th>
</tr>
</thead>
<tbody>
<tr>
<td>Addition/Subtraction</td>
<td>Round to least decimal places</td>
<td>Combine variances (absolute)</td>
<td>General lab work</td>
</tr>
<tr>
<td>Multiplication/Division</td>
<td>Round to least sig figs</td>
<td>Combine relative variances</td>
<td>Engineering calculations</td>
</tr>
<tr>
<td>Mixed operations</td>
<td>Apply stepwise, track intermediate results</td>
<td>Full uncertainty budget</td>
<td>Research and metrology</td>
</tr>
</tbody>
</table>
<h2 id="standards-citation">Standards Citation</h2>
<p>Several standards define the proper handling of significant figures and uncertainty propagation:</p>
<ul>
<li><strong>ASTM E29-22</strong> – <em>Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications</em>. This standard specifies how to round test results and how to interpret significant digits in specification limits.</li>
<li><strong>ISO 80000-1:2022</strong> – <em>Quantities and units – Part 1: General</em>. Clause 7.3.4 addresses rounding and significant figures, recommending that the result of a calculation should not contain more significant digits than the least precise input.</li>
<li><strong>JCGM 100:2008 (GUM)</strong> – <em>Evaluation of measurement data – Guide to the expression of uncertainty in measurement</em>. Clause 5.1.2 provides the law of propagation of uncertainty, which is the rigorous method for combining standard uncertainties.</li>
<li><strong>NIST Technical Note 1297</strong> – <em>Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results</em> (Taylor &amp; Kuyatt, 1994). This document aligns with GUM and gives practical guidance for reporting uncertainties.</li>
</ul>
<h2 id="common-mistakes">Common Mistakes</h2>
<ol>
<li><strong>Rounding prematurely:</strong> Do not round intermediate values in a multi-step calculation. Carry extra digits until the final step, then round.</li>
<li><strong>Confusing decimal places with significant figures:</strong> For addition, the rule depends on decimal places, not sig figs. For multiplication, it depends on sig figs, not decimal places.</li>
<li><strong>Ignoring the uncertainty of exact numbers:</strong> Exact numbers (like 1000 in 1 L = 1000 mL) have infinite precision and do not limit the result.</li>
<li><strong>Applying the rule to constants:</strong> Mathematical constants like π or e are exact if they are used as symbols; if approximated, their precision must be considered.</li>
<li><strong>Forgetting to round the final answer:</strong> Always apply the rounding rule to the final reported value, not to intermediate steps.</li>
</ol>
<h2 id="practice-problems">Practice Problems</h2>
<p>Test your understanding with these exercises:</p>
<ol>
<li>Add: 2.34 + 5.6 + 0.789</li>
<li>Multiply: 4.56 × 1.2</li>
<li>Divide: 9.876 ÷ 3.2</li>
<li>Calculate: (12.34 + 5.6) × 2.0</li>
</ol>
<p><strong>Answers:</strong></p>
<ol>
<li>8.7 (one decimal place)</li>
<li>5.5 (two sig figs)</li>
<li>3.1 (two sig figs)</li>
<li>36 (two sig figs, because 2.0 has two sig figs and the sum 17.94 rounds to 17.9? Actually, stepwise: sum = 17.94, then multiply by 2.0 gives 35.88, round to 36 with two sig figs)</li>
</ol>
<h2 id="software-behavior-note">Software Behavior Note</h2>
<p>Spreadsheet software (Excel, Google Sheets) and programming languages (Python, R, MATLAB) typically do not apply significant figure rounding automatically. They return full-precision results, which can mislead users. For example, <code>=2.5*3.14159</code> in Excel yields 7.853975, not 7.9. To enforce significant figures, you must use rounding functions like <code>ROUND()</code> with the appropriate number of digits. In Python, the <code>round()</code> function uses banker&#8217;s rounding by default, which may not align with the half-up convention used in many standards. Always verify the rounding behavior of your tool against the relevant standard.</p>
<h2 id="quick-reference-table">Quick Reference Table</h2>
<table>
<thead>
<tr>
<th>Operation</th>
<th>Rule</th>
<th>Example</th>
<th>Result</th>
</tr>
</thead>
<tbody>
<tr>
<td>Addition</td>
<td>Least decimal places</td>
<td>12.1 + 3.45</td>
<td>15.6</td>
</tr>
<tr>
<td>Subtraction</td>
<td>Least decimal places</td>
<td>10.0 &#8211; 2.34</td>
<td>7.7</td>
</tr>
<tr>
<td>Multiplication</td>
<td>Least sig figs</td>
<td>2.5 × 3.14159</td>
<td>7.9</td>
</tr>
<tr>
<td>Division</td>
<td>Least sig figs</td>
<td>9.876 ÷ 3.2</td>
<td>3.1</td>
</tr>
</tbody>
</table>
<h2 id="related-rules">Related Rules</h2>
<p>For a deeper understanding, explore these related topics:</p>
<ul>
<li><a href="/rounding-methods">Rounding Methods: A Comparison</a></li>
<li><a href="/significant-figures">Significant Figures: The Complete Guide</a></li>
<li><a href="/measurement-uncertainty">Understanding Measurement Uncertainty</a></li>
<li><a href="/error-propagation">Error Propagation in Complex Calculations</a></li>
</ul>
<p>The post <a href="https://significantfigurescalculator.com/precision/error-propagation/propagating-uncertainty-addition-multiplication/">Propagating Uncertainty Through Addition and Multiplication: Rules, Examples, and Standards</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://significantfigurescalculator.com/precision/error-propagation/propagating-uncertainty-addition-multiplication/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>What Measurement Uncertainty Actually Is (and Why It Matters)</title>
		<link>https://significantfigurescalculator.com/precision/measurement-uncertainty/what-is-measurement-uncertainty/</link>
					<comments>https://significantfigurescalculator.com/precision/measurement-uncertainty/what-is-measurement-uncertainty/#respond</comments>
		
		<dc:creator><![CDATA[Tommy C. Moran]]></dc:creator>
		<pubDate>Thu, 09 Jul 2026 03:27:17 +0000</pubDate>
				<category><![CDATA[Measurement Uncertainty]]></category>
		<category><![CDATA[GUM]]></category>
		<category><![CDATA[rounding]]></category>
		<category><![CDATA[significant figures]]></category>
		<guid isPermaLink="false">http://significantfigurescalculator.test/uncategorized/what-is-measurement-uncertainty/</guid>

					<description><![CDATA[<p>Measurement uncertainty is a quantitative expression of the doubt associated with a measured value. This guide explains its definition, evaluation per GUM, reporting conventions, and common pitfalls, with worked examples and standards citations.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/measurement-uncertainty/what-is-measurement-uncertainty/">What Measurement Uncertainty Actually Is (and Why It Matters)</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Measurement uncertainty is often misunderstood, even by experienced engineers and scientists. It is not the same as an error, nor is it a simple tolerance range. In this comprehensive guide, we break down what measurement uncertainty actually is, how to evaluate it according to international standards, and how to report it correctly—so you can avoid the pitfalls that lead to incorrect conclusions and non-compliant results.</p>
<h2 id="rule-statement">Rule Statement</h2>
<p>The formal definition of measurement uncertainty, as given in the <em>Guide to the Expression of Uncertainty in Measurement</em> (GUM, JCGM 100:2008, clause 2.2.3), is:</p>
<blockquote>
<p>&#8220;Non-negative parameter characterizing the dispersion of the quantity values being attributed to a measurand, based on the information used.&#8221;</p>
</blockquote>
<p>This definition emphasizes three key aspects:</p>
<ul>
<li><strong>Dispersion</strong> – uncertainty is a spread, not a single point.</li>
<li><strong>Quantity values</strong> – it applies to the values of a measurand, not to the measurement process itself.</li>
<li><strong>Based on the information used</strong> – uncertainty depends on the available knowledge, including both statistical data and scientific judgment.</li>
</ul>
<p>Uncertainty is <em>not</em> an error. An error is the difference between a measured value and the true value; it is a single, often unknown quantity. Uncertainty, on the other hand, is a parameter that describes the range within which the true value is expected to lie, with a given level of confidence. It is a measure of doubt, not a mistake.</p>
<h2 id="worked-examples">Worked Examples</h2>
<h3 id="example-1-simple-length-measurement">Example 1: Simple Length Measurement</h3>
<p>Suppose you measure the length of a metal rod using a ruler with 1 mm divisions. You take five readings: 152 mm, 153 mm, 152 mm, 154 mm, 153 mm.</p>
<p><strong>Step 1: Evaluate Type A uncertainty (statistical)</strong></p>
<p>Calculate the mean: (152+153+152+154+153)/5 = 152.8 mm. The standard deviation of the mean (standard uncertainty) is the experimental standard deviation divided by √5. The sample standard deviation is approximately 0.84 mm, so the standard uncertainty is 0.84/√5 ≈ 0.38 mm.</p>
<p><strong>Step 2: Evaluate Type B uncertainty (non-statistical)</strong></p>
<p>The ruler&#8217;s resolution is 1 mm. Assuming a rectangular distribution, the standard uncertainty from resolution is 1/(2√3) ≈ 0.29 mm. If the ruler has a calibration certificate stating an expanded uncertainty of 0.2 mm (k=2), the standard uncertainty is 0.1 mm. Combine these Type B components: √(0.29² + 0.1²) ≈ 0.31 mm.</p>
<p><strong>Step 3: Combine standard uncertainties</strong></p>
<p>Combine Type A and Type B: √(0.38² + 0.31²) ≈ 0.49 mm. This is the combined standard uncertainty, u<sub>c</sub>.</p>
<p><strong>Step 4: Expanded uncertainty</strong></p>
<p>For a 95% confidence level, use a coverage factor k=2 (assuming normal distribution). Expanded uncertainty U = 2 × 0.49 ≈ 0.98 mm. Report as 152.8 ± 1.0 mm (k=2).</p>
<h3 id="example-2-calibration-of-a-thermometer">Example 2: Calibration of a Thermometer</h3>
<p>A thermometer is calibrated against a reference standard. The reference standard has a certified uncertainty of 0.05 °C (k=2). The thermometer is read 10 times, giving a standard deviation of 0.07 °C. The resolution of the thermometer is 0.1 °C.</p>
<p>Type A: u<sub>A</sub> = 0.07/√10 ≈ 0.022 °C.</p>
<p>Type B: From reference standard: 0.05/2 = 0.025 °C. From resolution: 0.1/(2√3) ≈ 0.029 °C. Combined Type B: √(0.025² + 0.029²) ≈ 0.038 °C.</p>
<p>Combined standard uncertainty: √(0.022² + 0.038²) ≈ 0.044 °C. Expanded (k=2): 0.088 °C, report as 0.09 °C.</p>
<h2 id="counter-examples">Counter-Examples</h2>
<h3 id="treating-uncertainty-as-an-error">Treating Uncertainty as an Error</h3>
<p><strong>Wrong:</strong> &#8220;The measurement uncertainty is ±0.5 mm, so the true value could be 0.5 mm away.&#8221; This implies the uncertainty is an error bound, but uncertainty is a probabilistic dispersion, not a hard limit.</p>
<h3 id="using-tolerance-instead-of-uncertainty">Using Tolerance Instead of Uncertainty</h3>
<p><strong>Wrong:</strong> &#8220;The part has a tolerance of ±0.1 mm, so the measurement uncertainty is ±0.1 mm.&#8221; Tolerance is a specification for the product, not a property of the measurement. Uncertainty must be evaluated from the measurement process itself.</p>
<h3 id="ignoring-type-b-contributions">Ignoring Type B Contributions</h3>
<p><strong>Wrong:</strong> &#8220;I only report the standard deviation of my readings as the uncertainty.&#8221; This neglects systematic effects like calibration, resolution, and environmental factors. The GUM requires a complete uncertainty budget.</p>
<h2 id="convention-comparison-table">Convention Comparison Table</h2>
<table>
<thead>
<tr>
<th>Aspect</th>
<th>GUM (JCGM 100:2008)</th>
<th>NIST TN 1297</th>
<th>ISO 5725</th>
<th>ASTM E29</th>
</tr>
</thead>
<tbody>
<tr>
<td>Definition of uncertainty</td>
<td>Parameter characterizing dispersion</td>
<td>Same as GUM</td>
<td>Parameter associated with a result that characterizes the dispersion</td>
<td>Not explicitly defined; focuses on rounding and significant figures</td>
</tr>
<tr>
<td>Coverage factor</td>
<td>k=2 for 95% (default)</td>
<td>k=2 for 95% (recommended)</td>
<td>k=2 for 95% (common)</td>
<td>Not applicable</td>
</tr>
<tr>
<td>Reporting significant digits</td>
<td>Uncertainty to 2 significant digits; result rounded to match</td>
<td>Same as GUM</td>
<td>Uncertainty to 1 or 2 significant digits</td>
<td>Rules for rounding test results to a specified number of digits</td>
</tr>
<tr>
<td>Type A vs Type B</td>
<td>Explicitly defined</td>
<td>Explicitly defined</td>
<td>Uses repeatability and reproducibility</td>
<td>Not applicable</td>
</tr>
<tr>
<td>Combining components</td>
<td>Root-sum-square (RSS) of standard uncertainties</td>
<td>Same as GUM</td>
<td>ANOVA-based</td>
<td>Not applicable</td>
</tr>
</tbody>
</table>
<h2 id="standards-citation">Standards Citation</h2>
<p>The following standards and guides provide the authoritative basis for evaluating and reporting measurement uncertainty:</p>
<ul>
<li><strong>GUM (JCGM 100:2008)</strong> – <em>Evaluation of measurement data — Guide to the expression of uncertainty in measurement</em>. Clauses 2.2.3 (definition), 4.2 (Type A), 4.3 (Type B), 5.1 (combined standard uncertainty), 6.2 (expanded uncertainty).</li>
<li><strong>NIST TN 1297</strong> – <em>Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results</em>. Provides practical implementation of GUM, with specific guidance on significant figures (Section 7).</li>
<li><strong>ISO 5725-1</strong> – <em>Accuracy (trueness and precision) of measurement methods and results</em>. Defines repeatability and reproducibility, which are components of uncertainty.</li>
<li><strong>ASTM E29</strong> – <em>Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications</em>. Governs rounding of test results, which is directly related to how uncertainty is reported.</li>
</ul>
<h2 id="common-mistakes">Common Mistakes</h2>
<ul>
<li><strong>Omitting the coverage factor</strong> – Reporting &#8220;± 0.5&#8221; without specifying k or confidence level is meaningless.</li>
<li><strong>Rounding the result before the uncertainty</strong> – Always round the uncertainty first, then round the measured value to the same decimal place.</li>
<li><strong>Using the standard deviation of the sample instead of the standard deviation of the mean</strong> – The uncertainty of the mean is smaller than the spread of individual readings.</li>
<li><strong>Forgetting to include resolution effects</strong> – Every digital or analog instrument contributes a Type B uncertainty from its resolution.</li>
<li><strong>Double-counting components</strong> – For example, including both a calibration correction and its uncertainty when the correction is already applied.</li>
</ul>
<h2 id="practice-problems">Practice Problems</h2>
<p><strong>Problem 1:</strong> A balance has a calibration certificate stating an expanded uncertainty of 0.02 g (k=2). The balance&#8217;s resolution is 0.01 g. You weigh a sample 4 times: 10.23, 10.25, 10.22, 10.24 g. Compute the combined standard uncertainty and report the result with expanded uncertainty (k=2).</p>
<p><em>Solution:</em> Type A: mean = 10.235 g, sample std = 0.0129 g, u<sub>A</sub> = 0.0129/√4 = 0.00645 g. Type B: calibration: 0.02/2 = 0.01 g; resolution: 0.01/(2√3) ≈ 0.00289 g. Combined Type B: √(0.01² + 0.00289²) ≈ 0.0104 g. Combined standard: √(0.00645² + 0.0104²) ≈ 0.0122 g. Expanded: 0.0244 g, round to 0.024 g. Result: 10.235 ± 0.024 g (k=2).</p>
<p><strong>Problem 2:</strong> A pH meter has a stated accuracy of ±0.02 pH units. You take 3 readings: 7.01, 7.02, 7.01. Estimate the standard uncertainty (assume the accuracy is a rectangular distribution).</p>
<p><em>Solution:</em> Type A: mean = 7.0133, sample std = 0.00577, u<sub>A</sub> = 0.00577/√3 ≈ 0.00333. Type B: accuracy as rectangular: 0.02/√3 ≈ 0.01155. Combined: √(0.00333² + 0.01155²) ≈ 0.0120 pH.</p>
<h2 id="quick-reference-table">Quick Reference Table</h2>
<table>
<thead>
<tr>
<th>Symbol</th>
<th>Term</th>
<th>Definition / Formula</th>
</tr>
</thead>
<tbody>
<tr>
<td>u</td>
<td>Standard uncertainty</td>
<td>Uncertainty expressed as a standard deviation</td>
</tr>
<tr>
<td>u<sub>A</sub></td>
<td>Type A uncertainty</td>
<td>Evaluated by statistical analysis of repeated observations</td>
</tr>
<tr>
<td>u<sub>B</sub></td>
<td>Type B uncertainty</td>
<td>Evaluated by other means (calibration, resolution, etc.)</td>
</tr>
<tr>
<td>u<sub>c</sub></td>
<td>Combined standard uncertainty</td>
<td>√(Σ u<sub>i</sub>²) for independent components</td>
</tr>
<tr>
<td>U</td>
<td>Expanded uncertainty</td>
<td>U = k × u<sub>c</sub></td>
</tr>
<tr>
<td>k</td>
<td>Coverage factor</td>
<td>Typically 2 for 95% confidence</td>
</tr>
</tbody>
</table>
<h2 id="sources-further-reading">Sources &amp; Further Reading</h2>
<ul>
<li>JCGM 100:2008, <em>Evaluation of measurement data — Guide to the expression of uncertainty in measurement</em> (GUM).</li>
<li>NIST TN 1297, <em>Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results</em>.</li>
<li>ISO 5725-1:1994, <em>Accuracy (trueness and precision) of measurement methods and results</em>.</li>
<li>ASTM E29-13, <em>Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications</em>.</li>
</ul>
<p>For more on rounding and significant figures, see our <a href="/significant-figures-rules">Significant Figures Rules</a> and <a href="/rounding-methods">Rounding Methods</a> articles.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/measurement-uncertainty/what-is-measurement-uncertainty/">What Measurement Uncertainty Actually Is (and Why It Matters)</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://significantfigurescalculator.com/precision/measurement-uncertainty/what-is-measurement-uncertainty/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How Many Sig Figs Should an Uncertainty Have? (Usually One or Two)</title>
		<link>https://significantfigurescalculator.com/precision/measurement-uncertainty/how-many-sig-figs-should-an-uncertainty-have/</link>
					<comments>https://significantfigurescalculator.com/precision/measurement-uncertainty/how-many-sig-figs-should-an-uncertainty-have/#respond</comments>
		
		<dc:creator><![CDATA[Tommy C. Moran]]></dc:creator>
		<pubDate>Tue, 07 Jul 2026 20:14:54 +0000</pubDate>
				<category><![CDATA[Measurement Uncertainty]]></category>
		<category><![CDATA[GUM]]></category>
		<category><![CDATA[rounding]]></category>
		<category><![CDATA[significant figures]]></category>
		<category><![CDATA[uncertainty]]></category>
		<guid isPermaLink="false">http://significantfigurescalculator.test/uncategorized/how-many-sig-figs-should-an-uncertainty-have/</guid>

					<description><![CDATA[<p>The uncertainty in a measurement should be reported with one or two significant figures, depending on the magnitude of the leading digit and the desired confidence level. This article explains the rules, conventions, and standards that govern this practice.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/measurement-uncertainty/how-many-sig-figs-should-an-uncertainty-have/">How Many Sig Figs Should an Uncertainty Have? (Usually One or Two)</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2 id="rule-statement">Rule Statement</h2>
<p>The universally accepted rule is that an uncertainty (also called measurement uncertainty, standard deviation, or expanded uncertainty) should be reported with <strong>one significant figure</strong> if the leading digit is 1 or 2, and with <strong>two significant figures</strong> if the leading digit is 3 or greater. This rule is a compromise between precision and practicality: one sig fig is often too coarse for small leading digits (e.g., 0.14 vs. 0.1 loses 40% of the information), while two sig figs for large leading digits (e.g., 9.3 vs. 9) adds little value and may imply false precision.</p>
<p>This rule is endorsed by several metrology authorities, including the <strong>GUM (Guide to the Expression of Uncertainty in Measurement)</strong>, <strong>NIST Technical Note 1297</strong>, and <strong>ISO 80000-1</strong>. It is also a common requirement in scientific journals and engineering standards.</p>
<p>When the uncertainty is reported with one significant figure, the measurement result must be rounded to the same decimal place. When two sig figs are used, the result is rounded to the same place as the last digit of the uncertainty. This ensures that the uncertainty and the result are consistent in precision.</p>
<h2 id="worked-examples">Worked Examples</h2>
<h3 id="example-1-leading-digit-1-or-2-%e2%86%92-one-sig-fig">Example 1: Leading digit 1 or 2 → one sig fig</h3>
<p>Suppose a length measurement yields a value of <em>12.345 cm</em> with a calculated standard uncertainty of <em>0.0142 cm</em>. The leading digit of the uncertainty is 1, so we round it to one significant figure: <strong>0.01 cm</strong>. The measurement result must then be rounded to the same decimal place (hundredths): <strong>12.35 cm</strong>. The final reported value is <strong>12.35 ± 0.01 cm</strong>.</p>
<h3 id="example-2-leading-digit-3-or-higher-%e2%86%92-two-sig-figs">Example 2: Leading digit 3 or higher → two sig figs</h3>
<p>Consider a mass measurement of <em>50.123 g</em> with an uncertainty of <em>0.0467 g</em>. The leading digit is 4, so we keep two significant figures: <strong>0.047 g</strong>. The result is rounded to the same decimal place (thousandths): <strong>50.123 g</strong>. The reported value is <strong>50.123 ± 0.047 g</strong>.</p>
<h3 id="example-3-edge-case-leading-digit-exactly-2">Example 3: Edge case – leading digit exactly 2</h3>
<p>If the uncertainty is <em>0.00298</em>, the leading digit is 2, so one sig fig is used: <strong>0.003</strong>. The result is rounded to the same place (thousandths). This avoids the awkwardness of reporting 0.0030 which would imply two sig figs.</p>
<h3 id="example-4-expanded-uncertainty-k2">Example 4: Expanded uncertainty (k=2)</h3>
<p>For an expanded uncertainty (e.g., 95% confidence) of <em>1.34</em>, the leading digit is 1, so we report <strong>1</strong>. The result is rounded to the ones place. If the result is <em>25.6</em>, it becomes <strong>26 ± 1</strong>.</p>
<h2 id="counter-examples">Counter-Examples</h2>
<p>Common errors include reporting too many or too few significant figures in the uncertainty. Here are typical mistakes:</p>
<ul>
<li><strong>Reporting three or more sig figs:</strong> Writing <em>0.0142</em> as the uncertainty when the leading digit is 1 is overkill. It implies a precision that the uncertainty itself does not justify.</li>
<li><strong>Reporting one sig fig when the leading digit is 9:</strong> If the uncertainty is <em>9.8</em>, rounding to <em>10</em> (one sig fig) loses the distinction between 9.8 and 10.2. The rule says two sig figs for leading digit ≥3, so report <em>9.8</em>.</li>
<li><strong>Inconsistent rounding of the result:</strong> If the uncertainty is rounded to 0.01, but the result is reported as 12.345, the last digit of the result is meaningless. Always round the result to the same decimal place as the uncertainty.</li>
<li><strong>Using the number of sig figs of the uncertainty to determine the sig figs of the result:</strong> The result&#8217;s rounding is determined by the decimal place, not by the count of sig figs in the uncertainty.</li>
</ul>
<h2 id="convention-comparison-table">Convention Comparison Table</h2>
<table>
<thead>
<tr>
<th>Authority / Standard</th>
<th>Rule</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td>GUM (JCGM 100:2008), Section 7.2.6</td>
<td>Report uncertainty with one or two significant figures; typically two for expanded uncertainty when leading digit is 1 or 2.</td>
<td>GUM states: “The uncertainty should be given to two significant figures if the leading digit is 1 or 2, and to one significant figure otherwise.”</td>
</tr>
<tr>
<td>NIST Technical Note 1297 (1994), Section 7.5</td>
<td>Same as GUM: one sig fig for leading digit ≥3, two sig figs for 1 or 2.</td>
<td>NIST adds: “The numerical value of the uncertainty should not be given with more than two significant figures.”</td>
</tr>
<tr>
<td>ISO 80000-1:2009, Annex C</td>
<td>Recommends one or two significant figures for uncertainty, with the same rule.</td>
<td>ISO emphasizes consistency with the measurement result&#8217;s rounding.</td>
</tr>
<tr>
<td>ASTM E29 (Standard Practice for Using Significant Digits)</td>
<td>Does not specifically address uncertainty, but recommends that rounding be based on the uncertainty magnitude.</td>
<td>ASTM E29 provides general rules for rounding test data.</td>
</tr>
<tr>
<td>IUPAC (Quantities, Units and Symbols in Physical Chemistry)</td>
<td>Recommends one significant figure for standard uncertainty, two for expanded uncertainty.</td>
<td>Often used in chemistry.</td>
</tr>
</tbody>
</table>
<h2 id="standards-citation">Standards Citation</h2>
<p>The rule is not arbitrary; it is codified in international standards. Key clauses include:</p>
<ul>
<li><strong>GUM (JCGM 100:2008), Section 7.2.6:</strong> “The uncertainty should be given to two significant figures if the leading digit is 1 or 2, and to one significant figure otherwise.”</li>
<li><strong>NIST Technical Note 1297 (1994), Section 7.5:</strong> “The numerical value of the uncertainty should not be given with more than two significant figures.”</li>
<li><strong>ISO 80000-1:2009, Annex C (C.3.4):</strong> “The uncertainty of a measurement should be expressed with one or two significant digits.”</li>
<li><strong>ASTM E29-13, Section 6:</strong> Discusses rounding of test data, recommending that the number of significant figures be consistent with the uncertainty.</li>
</ul>
<p>These standards are widely adopted in physics, chemistry, engineering, and metrology. Adherence ensures that reported uncertainties are neither overly optimistic nor unnecessarily conservative.</p>
<h2 id="common-mistakes">Common Mistakes</h2>
<ol>
<li><strong>Always using one sig fig:</strong> Some textbooks simplify the rule to “always one sig fig,” but this fails for uncertainties like 0.14, where 0.1 is a 40% change. The leading-digit rule is more accurate.</li>
<li><strong>Always using two sig figs:</strong> This overstates precision for uncertainties like 9.3, where 9.3 vs. 9 is a negligible difference.</li>
<li><strong>Rounding the uncertainty before rounding the result:</strong> Always round the uncertainty first, then round the result to match the decimal place.</li>
<li><strong>Using the same number of decimal places as the original data:</strong> If the original measurement has more decimal places than the uncertainty, the extra digits are meaningless.</li>
<li><strong>Ignoring the leading digit rule when the uncertainty is exactly 1.0 or 2.0:</strong> The rule applies to the first non-zero digit, so 1.0 has leading digit 1 and should be one sig fig (1), not two.</li>
<li><strong>Reporting an uncertainty with a leading zero after the decimal:</strong> For example, 0.04 has one sig fig; 0.040 has two. The rule applies to the significant digits, not the decimal places.</li>
</ol>
<h2 id="practice-problems">Practice Problems</h2>
<p>Test your understanding with these exercises. Answers are provided at the end.</p>
<ol>
<li>Uncertainty = 0.000345, result = 1.23456. How many sig figs for the uncertainty? Round the result.</li>
<li>Uncertainty = 1.89, result = 45.6. What is the reported value?</li>
<li>Uncertainty = 0.020, result = 0.100. Should the uncertainty be 0.02 or 0.020? What is the final result?</li>
<li>Uncertainty = 0.00012, result = 0.000345. Report the value.</li>
</ol>
<p><strong>Answers:</strong></p>
<ol>
<li>Leading digit 3 → two sig figs: 0.00035. Result rounded to same place (5th decimal): 1.2346. Reported: 1.2346 ± 0.00035.</li>
<li>Leading digit 1 → one sig fig: 2. Result rounded to ones: 46. Reported: 46 ± 2.</li>
<li>Leading digit 2 → one sig fig: 0.02. Result rounded to hundredths: 0.10. Reported: 0.10 ± 0.02.</li>
<li>Leading digit 1 → one sig fig: 0.0001. Result rounded to 4th decimal: 0.0003. Reported: 0.0003 ± 0.0001.</li>
</ol>
<h2 id="software-behavior-note">Software Behavior Note</h2>
<p>When using scientific software, be aware of how it handles uncertainty rounding. For example:</p>
<ul>
<li><strong>Excel:</strong> There is no built-in function for rounding to significant figures. You must use custom formulas or the ROUND function with a calculated number of digits. Excel&#8217;s ROUND uses half-away-from-zero, which may differ from standard rounding.</li>
<li><strong>Python (NumPy/SciPy):</strong> The <code>round()</code> function uses banker&#8217;s rounding (half-to-even). When reporting uncertainties, you should implement the leading-digit rule manually.</li>
<li><strong>MATLAB:</strong> The <code>round</code> function rounds half away from zero. Use <code>sigfig</code> from the File Exchange or write a custom function.</li>
<li><strong>R:</strong> The <code>signif()</code> function rounds to a specified number of significant digits, but it does not apply the leading-digit rule automatically. You must decide whether to use 1 or 2 sig figs.</li>
<li><strong>LaTeX (siunitx):</strong> The <code>num{...}</code> command can round to a given number of significant figures, but you must specify the number manually.</li>
</ul>
<p>Always verify that the software&#8217;s rounding method matches your intended rule. For critical work, implement the rule explicitly.</p>
<h2 id="quick-reference-table">Quick Reference Table</h2>
<table>
<thead>
<tr>
<th>Leading digit of uncertainty</th>
<th>Number of sig figs for uncertainty</th>
<th>Example (uncertainty)</th>
<th>Example (reported result)</th>
</tr>
</thead>
<tbody>
<tr>
<td>1</td>
<td>1</td>
<td>0.014 → 0.01</td>
<td>12.345 → 12.35</td>
</tr>
<tr>
<td>2</td>
<td>1</td>
<td>0.028 → 0.03</td>
<td>5.678 → 5.68</td>
</tr>
<tr>
<td>3</td>
<td>2</td>
<td>0.032 → 0.032</td>
<td>1.234 → 1.234</td>
</tr>
<tr>
<td>4</td>
<td>2</td>
<td>0.047 → 0.047</td>
<td>50.123 → 50.123</td>
</tr>
<tr>
<td>5–9</td>
<td>2</td>
<td>0.86 → 0.86</td>
<td>10.2 → 10.2</td>
</tr>
</tbody>
</table>
<h2 id="sources-further-reading">Sources &amp; Further Reading</h2>
<ul>
<li>JCGM 100:2008, <em>Evaluation of measurement data — Guide to the expression of uncertainty in measurement</em> (GUM).</li>
<li>NIST Technical Note 1297, <em>Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results</em> (1994).</li>
<li>ISO 80000-1:2009, <em>Quantities and units — Part 1: General</em>.</li>
<li>ASTM E29-13, <em>Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications</em>.</li>
<li>IUPAC, <em>Quantities, Units and Symbols in Physical Chemistry</em> (Green Book), 3rd ed.</li>
</ul>
<p>For a deeper dive, see our related articles on <a href="/sig-figs-in-measurement-uncertainty/">Sig Figs in Measurement Uncertainty</a> and <a href="/rounding-rules/">Rounding Rules</a>.</p>
<p>The post <a href="https://significantfigurescalculator.com/precision/measurement-uncertainty/how-many-sig-figs-should-an-uncertainty-have/">How Many Sig Figs Should an Uncertainty Have? (Usually One or Two)</a> appeared first on <a href="https://significantfigurescalculator.com">SignificantFiguresCalculator</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://significantfigurescalculator.com/precision/measurement-uncertainty/how-many-sig-figs-should-an-uncertainty-have/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
