Rule Statement: What Must Be Documented

A lab report should explicitly state the rounding convention in the methods or data-analysis section. At minimum, document: the rounding method (half-up, half-even/banker’s, truncation, ceiling, floor); the precision target (significant figures or decimal places); how uncertainty is rounded; whether rounding occurs at intermediate steps or only at the final step; how trailing zeros are represented; which numbers are exact; and what software or calculator was used.

A complete sentence might read: ‘All reported values were rounded at the final step to three significant figures using half-even rounding; uncertainties were rounded to one significant figure and reported to the same decimal place as the value. Exact counts were treated as exact. Calculations used Python 3.12 round().’ This level of detail makes the report reproducible and auditable.

• Method: half-up, half-even, truncation, ceiling, floor.
• Precision: significant figures or decimal places.
• Uncertainty: one or two significant figures; same decimal place as value.
• Timing: final-step rounding only; guard digits retained.
• Notation: scientific notation or overline for trailing zeros.
• Software: name, version, and rounding function.

Documentation is not optional; it is part of metrological traceability.

Standards Citation: What the Authorities Require

Cite a recognized standard when your SOP, journal, or accreditation body requires it. The table below summarizes the most relevant clauses for lab reports.

Convention Comparison Table

Worked Examples

Example 1: Mean and uncertainty

A sample has mean 12.3456 and standard deviation s = 0.0234 for n = 5. The standard uncertainty is u = s/√n = 0.0234/2.236 = 0.01046. For k = 2, U = 2u = 0.02092. Round U to one significant figure: 0.02. The mean must be rounded to the same decimal place (hundredths): 12.35. Report: 12.35 ± 0.02 (k = 2). Document: ‘Uncertainty rounded to one significant figure; mean rounded to same decimal place; half-even applied only to exact 5s.’

Example 2: Multiplication and division

2.45 cm × 3.1 cm = 7.595 cm². The limiting factor is 3.1, with two significant figures. Round the final product to two significant figures: 7.6 cm². Document: ‘Products and quotients rounded to the least number of significant figures at the final step.’

Example 3: Addition and subtraction

12.1 mL + 0.234 mL + 5.67 mL = 18.004 mL. The least precise decimal place is tenths (12.1). Round the final sum to tenths: 18.0 mL. Document: ‘Sums and differences rounded to the least precise decimal place.’

Counter-Examples: What Not to Do

• Double rounding: 2.4451 to two decimals. Direct rounding gives 2.45 because the third digit is 5 followed by 1. Rounding first to three decimals gives 2.445, then to two decimals with half-even gives 2.44. Round once from raw data.
• Mismatched precision: Reporting 12.3456 ± 0.02 implies the value is known to four decimal places while the uncertainty is only two. Report 12.35 ± 0.02.
• Ambiguous trailing zeros: 1200 may have two, three, or four significant figures. Write 1.2 × 10³, 1.20 × 10³, or 1.200 × 10³, or use overline notation.
• Omitting the method: ‘Values were rounded’ does not say whether exact 5s went up or to even. State the method.
• Calculator display: Copying 0.333333333 from a display overstates precision. Round to the correct significant figures.

Common Mistakes

Quick Reference Table

For deeper rules, see Rounding Rules, Significant Figures, Measurement Uncertainty, ASTM E29, Banker’s Rounding, and Ambiguous Trailing Zeros.

Sources & Further Reading

• ASTM E29-13(2019), Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications.
• ISO 80000-1:2009, Quantities and units — Part 1: General, Clause 7.3.
• JCGM 100:2008, Evaluation of measurement data — Guide to the expression of uncertainty in measurement (GUM), Clause 7.2.6.
• NIST TN 1297 (1994), Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results.
• ISO/IEC 17025:2017, General requirements for the competence of testing and calibration laboratories, Clause 7.8.2.

Reviewer Box

Reviewer: Metrology review panel. Last reviewed: 2025-01-15. Scope: General lab reporting; always follow your laboratory SOP and accreditation requirements. This reference is maintained as part of our precision-and-rounding library.

The post How to Document Rounding Conventions in Lab Reports: A Guide for Students and Researchers appeared first on SignificantFiguresCalculator.

This site is a precision-and-rounding reference, not merely a significant figures calculator. The calculator is useful, but the rules, standards, and examples below are the core of the resource. For related material, see Exact Numbers, Significant Figures, and Why Sig Figs Are an Approximation.

Rule Statement

Use this rule: exact numbers and defined constants have infinite significant figures and never limit the precision of a calculation. Measured quantities have finite significant figures and do limit the result. The Avogadro constant belongs to the first group in the current SI.

Formally, the mole is defined by fixing the numerical value of the Avogadro constant to exactly 6.02214076 × 10²³ when expressed in mol⁻¹. Therefore:

• N_A = 6.02214076 × 10²³ mol⁻¹ (exact, by definition).
• The Avogadro number = 6.02214076 × 10²³ (exact, dimensionless).
• Any experimental realization of the mole — for example, determining the amount of substance from a measured mass and molar mass — carries measurement uncertainty.
• If you replace the exact constant with 6.022 × 10²³, you are using a rounded approximation, not the exact constant. That approximation may limit the result if the other data have more significant figures.

Key distinction: The constant is exact. The process of measuring a sample is not. The exact constant does not add uncertainty; the measured sample data does.

Convention Comparison Table

For broader rounding conventions, compare Rounding Rules and Scientific Notation.

Worked Examples

Example 1: Molecules in a measured amount

How many molecules are in 2.50 mol of water? The value 2.50 mol has three significant figures. The Avogadro constant is exact, so it does not limit the result.

1. Write the conversion: N = (2.50 mol)(6.02214076 × 10²³ mol⁻¹).
2. Multiply: (2.50)(6.02214076) = 15.0553519.
3. Attach the power: 15.0553519 × 10²³ = 1.50553519 × 10²⁴.
4. Round to three significant figures because 2.50 has three: 1.51 × 10²⁴ molecules.

Notice that the exact constant could be written with 20 digits, and the answer would still be 1.51 × 10²⁴. Only the measured 2.50 mol limits the precision.

Example 2: Atoms to moles

A sample contains 3.01 × 10²³ atoms. Convert to moles. The count is given as 3.01 × 10²³, so it has three significant figures. The conversion uses the exact Avogadro constant.

1. Set up: n = (3.01 × 10²³ atoms) / (6.02214076 × 10²³ atoms mol⁻¹).
2. Divide: 3.01 / 6.02214076 = 0.499822…
3. Round to three significant figures: 0.500 mol.

If a historical measured value of N_A were used instead, its uncertainty would enter the result. Under the current SI, the conversion factor itself is exact.

Example 3: Mass to molecules with measured molar mass

Calculate the number of water molecules in 1.00 g of water, using M(H₂O) = 18.015 g mol⁻¹. Both 1.00 g and 18.015 g mol⁻¹ are measured or conventionally evaluated quantities with finite significant figures. The exact Avogadro constant does not limit the result.

1. Amount: n = 1.00 g / 18.015 g mol⁻¹ = 0.055509… mol.
2. Molecules: N = (0.055509… mol)(6.02214076 × 10²³ mol⁻¹) = 3.3428… × 10²².
3. The limiting input has three significant figures, so report 3.34 × 10²² molecules.

Counter-Examples

• Wrong: ‘Avogadro’s number has 9 significant figures, so my answer must have 9 significant figures.’ Why it is wrong: The exact constant has infinite significant figures; it does not force extra precision.
• Wrong: ‘The current Avogadro constant is 6.02214076 × 10²³ mol⁻¹ with an uncertainty, so I must propagate that uncertainty.’ Why it is wrong: That numerical value is exact by SI definition. Uncertainty belongs to experimental realization, not to the constant.
• Wrong: Rounding 6.02214076 × 10²³ to 6.0 × 10²³ before a calculation and then treating 6.0 as exact. Why it is wrong: You have introduced avoidable rounding error. Use the exact value in the calculation, then round once at the end.
• Wrong: Reporting 1.50553519 × 10²⁴ molecules from 2.50 mol. Why it is wrong: The measured amount has three significant figures, so the final answer should have three.

For more on avoiding these issues, see Rounding vs Significant Figures and Double Rounding Error.

Standards Citation

The exact status of the Avogadro constant follows from the SI defining constants. Key references include:

• BIPM, SI Brochure, 9th edition (2019), Section 2.3.1. Defines the mole by fixing the numerical value of the Avogadro constant to exactly 6.02214076 × 10²³ mol⁻¹.
• NIST SP 330 (2019), Section 2.3.1. U.S. edition of the SI Brochure; same definition and exact status.
• JCGM 100:2008 (GUM), Clauses 3.3.2 and 5.1.2. Discusses exact quantities and the reporting of measurement results with an appropriate number of digits.
• ISO 80000-1:2009, Clauses 6.4–6.5. Provides general rules for rounding and significant figures in quantity values.
• ASTM E29-22, Sections 4–7. Standard practice for using significant digits in test data and determining conformance.

Common Mistakes

1. Confusing the Avogadro constant with the Avogadro number. The constant has unit mol⁻¹; the number is dimensionless. Both are exact in the current SI when written with the defined value.
2. Treating 6.022 × 10²³ as the exact constant. It is a rounded display value. Use the full defined value when precision matters.
3. Letting an exact conversion factor limit significant figures. Exact conversions — including N_A, 1 mol = 6.02214076 × 10²³ entities, and 1 km = 1000 m — do not limit.
4. Propagating historical uncertainty for the modern constant. Before 2019, N_A was measured. Since 2019, it is defined.
5. Forgetting that sample mass and molar mass are measured. These quantities usually determine the final significant figures in mole calculations.
6. Rounding in the middle of a multi-step calculation. Keep extra digits until the final result, then round once. See Double Rounding Error.

Quick Reference Table

Related Rules

• Exact Numbers — how exact values behave in calculations.
• Significant Figures — core counting and rounding rules.
• Rounding Rules — half-up, half-even, and convention choices.
• Measurement Uncertainty — why sig figs are a simplified uncertainty model.
• Chemistry — mole calculations, molar mass, and solution stoichiometry.
• Physics — constants, units, and dimensional analysis.

Sources & Further Reading

• BIPM. The International System of Units (SI), 9th ed. (2019). Section 2.3.1.
• NIST. NIST Special Publication 330: The International System of Units (SI) (2019). Section 2.3.1.
• JCGM. Evaluation of Measurement Data — Guide to the Expression of Uncertainty in Measurement (GUM), JCGM 100:2008.
• ISO. ISO 80000-1:2009 Quantities and units — Part 1: General. Clauses 6.4–6.5.
• ASTM. ASTM E29-22, Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications.

For more precision guidance, explore GUM Guide, ISO 80000, and ASTM E29.

The post Avogadro’s Number and Significant Figures: Exact or Measured? appeared first on SignificantFiguresCalculator.

This site is a precision and rounding reference, not just a calculator. Excel does not ship with a native SIGFIG function. The ROUND function rounds to a fixed number of decimal places, not to a number of significant figures. To make Excel respect significant-figure rules, you must convert the desired number of significant figures into the correct decimal place, then call ROUND.

For a value x in cell A2 and n significant figures, the custom formula is:

=IF(A2=0,0,ROUND(A2,n-1-INT(LOG10(ABS(A2)))))

The exponent term INT(LOG10(ABS(x))) gives the power of ten of the leading significant digit. The decimal-place argument d = n − 1 − INT(LOG10(ABS(x))) tells Excel where the last significant digit lies. For values less than 1, Excel’s INT correctly floors negative logarithms; TRUNC does not.

In Excel 365, wrap it as a LAMBDA and define a name such as SIGFIG: =LAMBDA(x,n,IF(x=0,0,ROUND(x,n-1-INT(LOG10(ABS(x)))))). Then use =SIGFIG(A2,3). Older versions require repeating the formula or a VBA user-defined function.

Worked Examples

The table below shows the decimal-place conversion and the resulting ROUND call. Remember that the numeric result may not display trailing zeros as significant unless you apply a custom format.

Step-by-step for 1234.567 to 3 sig figs: The leading digit 1 is in the thousands place, so LOG10(1234.567) ≈ 3.0915. INT gives 3. d = 3 − 1 − 3 = −1. ROUND(1234.567,−1) rounds to the nearest ten, giving 1230.

Step-by-step for 0.0012345 to 3 sig figs: LOG10(0.0012345) ≈ −2.9084. INT gives −3. d = 3 − 1 − (−3) = 5. ROUND(0.0012345,5) gives 0.00123.

Counter-Examples

These common errors show why the custom formula must be built carefully.

• Using ROUND(A2,n): For 1234.567 with n=3, =ROUND(A2,3) returns 1234.567. It rounds to three decimal places, not to three significant figures. The correct answer is 1230.
• Using TRUNC for the exponent: For 0.0012345, TRUNC(LOG10(0.0012345)) = −2, so d = 4, giving 0.0012 (two significant figures). Correct uses INT = −3, d = 5, giving 0.00123.
• Omitting ABS: =LOG10(−1234) returns #NUM!, breaking the formula.
• Omitting zero handling: =LOG10(0) returns #NUM!.
• Assuming display equals significance: The formula returns numeric 10 for 9.99→2 sig figs; Excel General format shows 10, not 10. or 1.0E+01. Use scientific notation or a custom format to display the trailing zero.
• Using MROUND: =MROUND(1234.567,10^(n−1−INT(LOG10(ABS(A2))))) is not equivalent because MROUND rounds to a multiple, not to a decimal place. For n=3, the multiple is 0.1, so the result is 1234.6, not 1230.

Software Behavior Note

Excel stores numbers in IEEE 754 binary64. The custom formula works on the stored binary value, not on the displayed text. This matters in three ways.

1. Round-half-away-from-zero: Excel’s ROUND rounds ties away from zero (e.g., 2.5→3, −2.5→−3). ISO 80000-1:2009 Clause 5.4.2 and ASTM E29-22 often use round-half-to-even for exact ties. If your discipline requires half-even, wrap the result in a conditional tie-breaker or use a VBA/LAMBDA routine that implements ASTM E29.
2. Trailing zeros: Numeric values do not preserve trailing zeros. 10, 10.0, and 10.00 are the same number in Excel. To display sig figs, apply a custom number format, e.g., 0.00E+00 for three sig figs, or compute a text string.
3. Floating-point artifacts: LOG10 near powers of ten can be slightly above or below an integer. For example, LOG10(1000) may evaluate to 3 or 2.9999999999999996 depending on the upstream calculation. In practice, the INT-based formula is robust for normal spreadsheet work, but for critical metrology, round the exponent or use a tolerance: =ROUND(n−1−INT(LOG10(ABS(A2))),0).

Quick Reference Table

Common Mistakes

• Confusing significant figures with decimal places.
• Using ROUND(A2,n) instead of converting n to decimal places.
• Using TRUNC instead of INT for negative logarithms.
• Forgetting ABS for negative values.
• Forgetting the zero case, causing #NUM! errors.
• Expecting numeric formatting to change the stored value.
• Assuming Excel follows ASTM E29 or ISO 80000 tie rules. Excel’s ROUND does not.
• Double rounding: rounding intermediate results to sig figs before the final calculation. Carry guard digits, then round once at the end.
• Using MROUND as a shortcut for sig-fig rounding.
• Ignoring floating-point representation near powers of ten.

Standards Citation

• ISO 80000-1:2009, Quantities and units — Part 1: General, Clause 5.4.2 gives rules for rounding to a specified number of significant digits, including tie-to-even.
• ASTM E29-22, Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications, Section 6 provides rounding procedures for test data; ties are generally resolved to the nearest even digit.
• NIST SP 811 (2008), Guide for the Use of the International System of Units (SI), Section 5.4 discusses rounding and significant digits for SI values.
• JCGM 100:2008 (GUM), Evaluation of measurement data — Guide to the expression of uncertainty in measurement, Clause 7.2.2 recommends reporting uncertainty to one or two significant digits, which drives the final rounding of the measurand.
• NIST TN 1297 (1994), Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results, provides practical rounding guidance for uncertainty statements.

Related Rules

Significant-figure rounding is only one part of the precision toolkit. For addition and subtraction, the result is limited by decimal places; see Addition and Subtraction. For multiplication and division, the result is limited by the factor with the fewest significant figures; see Multiplication and Division. Exact numbers have infinite significance; see Exact Numbers. Scientific notation removes trailing-zero ambiguity; see Scientific Notation. Rounding methods such as half-up, half-even, and truncation are compared in Rounding Methods. For standards, see ASTM E29 and ISO 80000. For spreadsheet-specific notes, see Excel.

Sources & Further Reading

• ISO 80000-1:2009, Quantities and units — Part 1: General. Clause 5.4.2.
• ASTM E29-22, Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications.
• NIST SP 811 (2008), Guide for the Use of the International System of Units (SI), Section 5.4.
• JCGM 100:2008 (GUM), Evaluation of measurement data — Guide to the expression of uncertainty in measurement, Clause 7.2.2.
• NIST TN 1297 (1994), Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results.

The post How to Make Excel Respect Sig Fig Rules: A Custom Rounding Formula appeared first on SignificantFiguresCalculator.

In scientific and engineering reporting, a data table is more than a collection of numbers; it is a communication of measurement uncertainty. The fundamental rule for data tables is Uniformity of Precision: all values in a single column representing the same physical quantity must be reported to the same decimal place (absolute precision), regardless of the number of significant figures each individual value possesses.

This ensures that the reader can visually assess the precision of the dataset at a glance and prevents the accidental implication that some measurements are more precise than others simply due to their magnitude. While our site provides the industry’s most accurate significant figures calculator for individual computations, the application of these results within a table requires adherence to metrological reporting standards.

Standards Citation: ISO and GUM Frameworks

Professional reporting is governed by international standards to ensure reproducibility and clarity. The following standards dictate the treatment of significant figures and uncertainty in tables:

• ISO 80000-1: Specifies the general rules for quantities and units. It emphasizes that the last digit of a numerical value is the first uncertain digit.
• GUM (Guide to the Expression of Uncertainty in Measurement): The GUM framework stipulates that the reported value should be consistent with the uncertainty. Specifically, the numerical value of the result should be rounded to the same decimal place as the uncertainty (standard uncertainty or expanded uncertainty).
• ASTM E29: Provides the standard practice for using significant digits in experimental data, stressing that the number of significant digits should be based on the precision of the measuring instrument.

Note: In high-precision metrology, the GUM approach (matching value precision to uncertainty precision) supersedes basic “sig fig” rules taught in introductory chemistry or physics.

Worked Examples: Applying Consistency

Scenario: Reporting Mass Measurements

Suppose a researcher measures three samples using a balance with a precision of ±0.01 g. The raw readings are 12.4 g, 12.456 g, and 12.003 g. If the instrument precision is 0.01 g, all values must be rounded to the hundredths place.

1. Value 1: 12.4 $rightarrow$ 12.40 g (Trailing zero added to match precision)
2. Value 2: 12.456 $rightarrow$ 12.46 g (Rounded up)
3. Value 3: 12.003 $rightarrow$ 12.00 g (Rounded down)

The resulting table is clean and professional, indicating a consistent measurement resolution across all samples.

Counter-Examples: Common Reporting Errors

The following table demonstrates incorrect reporting practices often seen in student labs or unvetted technical reports.

The Fix: If the instrument precision is 0.01 g, the values must be 10.20, 10.25, and 10.30. If the precision is 0.1 g, they must be 10.2, 10.3, and 10.3.

Convention Comparison Table

Depending on the discipline, the way significant figures are handled in tables may vary slightly. This table compares the most common conventions.

Common Mistakes in Data Reporting

• The “Calculator Dump”: Copying and pasting 10+ decimal places from a calculator or software (like Excel) into a table. This implies a level of precision that does not exist.
• Double Rounding: Rounding a number at an intermediate step, then rounding again for the final table. This introduces cumulative error. Always keep guard digits until the final reporting step.
• Mixing Scientific and Standard Notation: Using 1.2e-3 and 0.0045 in the same column. Choose one format and apply it globally.
• Ignoring Leading Zeros: Failing to realize that 0.005 has only one significant figure, whereas 0.00500 has three.

Quick Reference Table: Table Formatting Checklist

Software Behavior Note

Modern software tools often handle precision in ways that can mislead a researcher. For example, Microsoft Excel and Google Sheets often hide trailing zeros by default or automatically format numbers based on cell width. To ensure professional reporting, users should explicitly set the “Number Format” to a fixed number of decimal places rather than relying on “General” formatting. In Python, the round() function implements “Round Half to Even” (Banker’s Rounding), which differs from the “Round Half Up” method taught in many schools. Always verify the rounding algorithm of your software before generating final data tables.

The post Significant Figures in Data Tables: Best Practices for Clear Reporting appeared first on SignificantFiguresCalculator.

Significant figures are the digits in a measured value that carry meaning for its precision. In JavaScript, every Number is an IEEE 754 binary64 floating-point value, so decimal significant-figure rounding can produce surprising results. The governing rule is simple: determine significant figures from the measurement, carry extra digits through intermediate calculations, and round only once at the final step. This site is a precision and rounding reference, not merely a calculator; the significant figures calculator implements the same decimal-safe rules documented here.

• All non-zero digits are significant.
• Zeros between non-zero digits are significant.
• Leading zeros are never significant.
• Trailing zeros after a decimal point are significant.
• Trailing zeros in a whole number without a decimal point are ambiguous; use scientific notation or an overline to remove ambiguity.

For addition and subtraction, round to the least precise decimal place. For multiplication and division, round to the least number of significant figures. See addition and subtraction rules and multiplication and division rules.

Standards Citation

Metrology and testing standards give authoritative rounding guidance. ISO 80000-1:2009, Quantities and units — Part 1: General, Clause 7.3.4 requires that rounding be performed in one step to avoid double-rounding error. ASTM E29-13a, Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications, Section 6 specifies rounding rules, including round half even for exact ties. JCGM 100:2008 (the GUM), Clause 7.2.2 recommends that uncertainty be reported to two significant digits. NIST Technical Note 1297, Section 7.2, gives compatible guidance for expressing uncertainty.

Round once, at the end. Report uncertainty and value with consistent significant digits. Do not let binary floating-point artifacts dictate decimal precision.

Software Behavior Note: JavaScript and IEEE 754

ECMAScript uses IEEE 754 binary64 for all Number values. There is no native decimal type. Values such as 0.1, 0.2, and 1.005 are not exactly representable in binary, so they are stored as nearby binary fractions. The classic demonstration is:

0.1 + 0.2 // 0.30000000000000004

Number.prototype.toFixed and Number.prototype.toPrecision return strings, but they operate on the underlying binary value. That means tie cases can round in unexpected directions. For example, (1.005).toFixed(2) returns '1.00', not '1.01', because 1.005 is stored slightly below 1.005. Math.round rounds half toward positive infinity: Math.round(2.5) is 3, but Math.round(-2.5) is -2. It is not banker’s rounding and does not follow ASTM E29 tie rules.

For significant-figure work, parse decimal input as a string, round on decimal digits, or use a decimal library such as decimal.js or big.js. If you must use native methods, treat them as display helpers, not as metrology-grade rounding engines.

Worked Examples

Example 1: 1.005 to three significant figures

Exact decimal reasoning: the digits are 1, 0, 0, and the next digit is 5. Round half up gives 1.01. In JavaScript, (1.005).toPrecision(3) returns '1.00' because the stored value is approximately 1.00499999999999989. The safe pattern is to parse the string '1.005' and round in decimal space.

Example 2: 0.1 + 0.2

The exact decimal sum is 0.3. JavaScript returns 0.30000000000000004. If the final answer is limited to one significant figure, report 0.3. The artifact is invisible after rounding, but it can break equality tests and accumulate in long calculations.

Example 3: 123.456 to four significant figures

Exact decimal: 123.5. JavaScript: (123.456).toPrecision(4) returns '123.5'. This case works because the binary error is far below the rounding threshold. Do not generalize from a single success.

Example 4: Multiplication with significant figures

Multiply 2.34 by 5.6. The exact product is 13.104. The first factor has three significant figures; the second has two. The result must have two significant figures: 13. JavaScript may show 13.104000000000001, so round only after the multiplication.

Counter-Examples

• Counter-example 1: (1.005).toFixed(2) gives '1.00'. Expected decimal result: '1.01'.
• Counter-example 2: Math.round(-2.5) gives -2. A symmetric half-away-from-zero rule would give -3.
• Counter-example 3: Rounding after every step. Adding 0.1, 0.2, and 0.3 and rounding to one significant figure at each stage can hide the true final precision. Round once at the end.
• Counter-example 4: Assuming 1.230 stores four significant figures. JavaScript stores the same Number for 1.230 and 1.23; trailing zeros are not preserved.

Convention Comparison Table

Common Mistakes

• Confusing decimal places with significant figures.
• Using binary floats for decimal money or exact decimal measurements.
• Double rounding: rounding intermediate results before the final step.
• Treating exact numbers, such as counts or defined constants, as if they limited significant figures.
• Assuming toPrecision always produces standards-compliant significant-figure rounding.
• Ignoring uncertainty propagation. See error propagation and measurement uncertainty.

Quick Reference Table

Sources & Further Reading

• ISO 80000-1:2009, Quantities and units — Part 1: General, Clause 7.3.4.
• ASTM E29-13a, Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications, Section 6.
• JCGM 100:2008, Evaluation of measurement data — Guide to the expression of uncertainty in measurement (GUM), Clause 7.2.2.
• NIST Technical Note 1297, Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results, Section 7.2.
• ECMAScript Language Specification, Number.prototype.toFixed and Number.prototype.toPrecision.
• IEEE 754-2019, Standard for Floating-Point Arithmetic.

The post Significant Figures in JavaScript: Avoiding Floating-Point Rounding Errors appeared first on SignificantFiguresCalculator.

Rule Statement

The governing rule is simple: round only once, at the end of the calculation. Carry at least one or two guard digits beyond the final significant figures or decimal places. Do not round intermediate results unless a standard or specification explicitly requires it.

ISO 80000-1:2009, clause 7.3, specifies that rounding should be performed only once to avoid the accumulation of rounding errors. ASTM E29-13a, Section 6, provides a consistent rounding method for test data. JCGM 100:2008 (GUM), clause 7.2.6, warns against excessive digits when reporting estimates and uncertainties.

When an intermediate rounding is unavoidable—for example, when a measurement instrument displays a limited number of digits—document the intermediate precision and apply a consistent tie-breaking convention. The most common conventions are round-half-up and round-half-even (banker’s rounding). See Round Half Even and Rounding Methods.

Worked Examples

Example 1: 2.4445 to 3 significant figures

Direct rounding: The number 2.4445 has five significant figures. To round to three significant figures, inspect the fourth digit (4). Because 4 is less than 5, the retained digits stay: 2.44.

Double rounding (round-half-up): First round 2.4445 to four significant figures. The fifth digit is 5, so round up: 2.445. Then round 2.445 to three significant figures. The fourth digit is 5, so round up: 2.45. The double-rounded result differs by 0.01.

Double rounding (round-half-even): First round 2.4445 to four significant figures. The digit to drop is 5, and the preceding digit is 4 (even), so it stays: 2.444. Then round to three significant figures: 2.44. Here the tie-breaking convention masks the error, but double rounding remains risky.

Example 2: 0.125 to 2 decimal places

Direct: 0.125 rounded to two decimal places using round-half-up is 0.13.

Double: Round first to one decimal place: 0.125 → 0.1 (since the second decimal is 2). Then round 0.1 to two decimal places: 0.10. The result is off by 0.03. This example shows that rounding to a precision lower than the final target destroys information before the final step.

Example 3: Uncertainty reporting

Suppose a measurement gives mean y = 10.2345 and standard uncertainty u(y) = 0.0123. GUM clause 7.2.6 recommends reporting the uncertainty to two significant figures: 0.012. The mean should then be rounded to the same decimal place: 10.234. If you first round the mean to 10.235 and then to 10.23, you may introduce double-rounding error. Always round the uncertainty first, then the estimate, using guard digits in the intermediate calculation.

Counter-Examples

Double rounding is often mistaken for harmless tidying. These counter-examples show where it fails.

• Summing rounded addends: Compute 1.005 + 1.005 + 1.005. Direct sum = 3.015, which rounds to 3.02 at two decimal places. If you round each addend first: 1.01 + 1.01 + 1.01 = 3.03. The difference is 0.01.
• Chained unit conversions: Convert 1.2345 m to cm (123.45 cm) and then to mm (1234.5 mm). If you round to 123 cm and then to 1230 mm, you lose 4.5 mm. Carry full precision through the chain.
• Percentage of a rounded base: 0.445% of 1000 = 4.45, which rounds to 4.5. If you first round 0.445% to 0.45%, you get 4.5. Here the result matches, but if the base were 999, the error would appear. Test with multiple values before assuming safety.

Convention Comparison Table

Standards Citation

Several international standards directly address rounding and double rounding.

• ASTM E29-13a, Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications, Section 6. It specifies a consistent rounding method and warns against intermediate rounding in conformance decisions.
• ISO 80000-1:2009, Quantities and units — Part 1: General, clause 7.3. It states that rounding should be performed only once and gives the round-half-even rule for exact ties.
• JCGM 100:2008 (GUM), Evaluation of measurement data — Guide to the expression of uncertainty in measurement, clause 7.2.6. It advises against excessive digits and recommends rounding the uncertainty before the estimate.
• NIST Special Publication 811, Guide for the Use of the International System of Units (SI), section 9.4. It provides practical rounding guidance for SI values.

"The numerical values of the estimate y and its standard uncertainty u(y) or expanded uncertainty U should not be given with an excessive number of digits." — JCGM 100:2008, 7.2.6.

Common Mistakes

• Rounding at every step. This is the classic double-rounding error. Keep intermediate values in full precision or with guard digits.
• Mixing tie-breaking rules. Using round-half-up for one step and round-half-even for another can create inconsistent results.
• Trusting displayed values. A calculator may show 2.445 but store 2.4445. Re-entering the displayed value introduces double rounding.
• Rounding uncertainty after the mean. GUM recommends rounding the uncertainty first, then the estimate to the same decimal place.
• Confusing significant figures with decimal places. These are different concepts. See Rounding vs Significant Figures.

Practice Problems

1. Round 3.14159 to three significant figures directly. Then round it to four significant figures first, and then to three. Compare the results. Answer: Direct 3.14; double: 3.142 → 3.14. No difference here, but try 3.1455.
2. Compute 1.005 + 1.005 + 1.005. Round each addend to two decimal places, sum, and compare with the direct sum rounded to two decimal places. Answer: Double 3.03; direct 3.02.
3. Mean = 12.3456, u = 0.0789. Report according to GUM 7.2.6. What happens if you round the mean to two decimal places first? Answer: u → 0.079; mean → 12.346. If mean first: 12.35 → 12.35, which may misalign with uncertainty.

Software Behavior Note

Software often uses binary floating-point (IEEE 754), where decimal fractions such as 0.1 and 0.125 are not exact. This can cause double rounding even when you round only once in decimal. For example, Python’s round() uses round-half-even, Excel’s ROUND() uses round-half-away-from-zero, MATLAB rounds half-away-from-zero, and JavaScript’s Math.round() rounds half-up toward +∞. Chaining these functions or re-entering displayed values can produce double-rounding errors. Use decimal libraries, carry guard digits, or use our significant figures calculator for controlled rounding. See Excel, Python, and JavaScript floating-point.

Discipline Note

Different fields have different conventions. Chemistry and biology often emphasize significant figures for lab measurements. Physics and engineering use uncertainty propagation and standards such as ASTM E29 for conformance. Astronomy may carry many digits but still rounds final results. Finance may use banker’s rounding to avoid systematic bias. Always follow the governing standard for your discipline. For more, see Chemistry, Engineering, and Measurement Uncertainty.

The post Double Rounding: Why Rounding Intermediate Results Ruins Precision appeared first on SignificantFiguresCalculator.

Rule Statement

For multiplication and division, the result carries the same number of significant figures as the factor with the fewest significant figures. This applies directly to c = A/(εb) and to A = εbc when A is calculated from ε, b, and c. For logarithms, the rule changes: the number of decimal places in the logarithm equals the number of significant figures in the original number. Because A = -log10(T), the decimal places in absorbance are set by the significant figures in transmittance T.

Path length b is a measured length. Treat 1.000 cm as four sig figs, 1.00 cm as three, 1.0 cm as two, and 1 cm as one unless the context establishes an exact nominal value. Instrument specifications, such as ±0.003 A, often override raw digit counts; report to the uncertainty, not beyond it. See Multiplication and Division and Logarithms.

Visual/Digit Map

For A = εbc, map each factor: ε often has 3 sig figs; b can have 4 sig figs; c is determined by A and ε. The limiting factor controls the final rounding.

Worked Examples

Example 1: Concentration from Absorbance

Given A = 0.523 (3 sig figs), ε = 1.50×10^4 L mol^-1 cm^-1 (3 sig figs), and b = 1.000 cm (4 sig figs), calculate c.

1. Compute the denominator: εb = (1.50×10^4)(1.000) = 1.50×10^4 L mol^-1.
2. Divide: c = 0.523 / (1.50×10^4) = 3.486666…×10^-5 M.
3. Identify the limiting factor: A and ε each have 3 sig figs; b has 4. The result therefore has 3 sig figs.
4. Report: c = 3.49×10^-5 M.

Example 2: Transmittance to Absorbance

T = 0.250 (3 sig figs). A = -log10(0.250) = 0.60205999… The log rule gives three decimal places, so A = 0.602.

Example 3: Two-Significant-Figure Absorptivity

A = 1.00 (3 sig figs), ε = 2.0×10^3 L mol^-1 cm^-1 (2 sig figs), b = 1.00 cm (3 sig figs). c = 1.00 / [(2.0×10^3)(1.00)] = 5.0×10^-4 M. The limiting factor is ε with 2 sig figs, so c = 5.0×10^-4 M.

Counter-Examples

• False precision from the display. A spectrophotometer displaying 0.5234 may have ±0.003 A noise. Reporting concentration to five sig figs is invalid. Round to the uncertainty.
• Confusing decimal places with significant figures. A = 0.0520 has three sig figs (5, 2, 0), not four. Leading zeros are placeholders.
• Treating nominal 1 cm as exact. If a cell path is 1 cm but not calibrated, its tolerance may limit concentration more than A. A 1 cm cell might be 1.00 ±0.01 cm, i.e., about 1% relative.
• Using the multiplication rule on logs. T = 0.500 has 3 sig figs; A = 0.301 has three decimal places. Do not simply count digits 3, 0, 1 in A as if place value did not matter.

Convention Comparison Table

Standards Citation

ASTM E29-22a, Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications, provides rounding and sig-fig conventions for test data. ASTM E275 describes UV-Vis spectrophotometer performance, including photometric accuracy and noise, which set practical absorbance precision. ISO 80000-1:2009, Clause 5.4.6, gives rounding rules for quantities and units. The GUM, JCGM 100:2008, Clause 7.2.6, advises reporting uncertainty to at most two significant digits and matching the decimal place of the result to the uncertainty. NIST Technical Note 1297, Section 7, gives compatible guidance for NIST measurement results.

Common Mistakes

• Keeping all calculator digits when computing c = A/(εb).
• Forgetting that T as a percent must be converted to a fraction before taking a logarithm.
• Assuming every absorbance digit is significant. In 0.005, only the 5 is significant.
• Rounding intermediate results too early; carry extra digits and round once at the end. See Double Rounding Error.
• Reporting concentration without uncertainty when calibration-curve uncertainty dominates.

Practice Problems

1. T = 0.400 (3 sig figs). Find A to the correct decimal places. Answer: A = -log10(0.400) = 0.398.
2. A = 0.750 (3 sig figs), ε = 1.20×10^4 L mol^-1 cm^-1 (3 sig figs), b = 1.00 cm (3 sig figs). Find c. Answer: c = 0.750 / [(1.20×10^4)(1.00)] = 6.25×10^-5 M.
3. Absorbance is read as 0.812 with instrument uncertainty ±0.004 A. How should A be reported? Answer: 0.812 ±0.004 A; do not report 0.8123.
4. Path length is measured as 10.0 mm. How many sig figs? Answer: 3, equivalent to 1.00 cm.

Quick Reference Table

Related Rules

• Multiplication and Division
• Logarithms
• Scientific Notation
• Measurement Uncertainty
• Rounding Rules
• Error Propagation
• Significant Figures

The post Significant Figures in Spectrophotometry: Beer-Lambert Law, Absorbance, Path Length, and Concentration appeared first on SignificantFiguresCalculator.

In the realm of metrology and scientific measurement, accuracy and precision are not interchangeable synonyms; they describe two distinct components of measurement error. This site serves as a comprehensive precision and rounding reference to ensure that data reporting adheres to international standards, providing not only the industry’s most accurate significant figures calculator but the theoretical depth required to interpret its results.

Defining Accuracy

Accuracy is the degree of closeness of a measurement (a result of a measurement procedure) to a true value or an accepted reference value. In technical terms, accuracy is a combination of both systematic error (bias) and random error. A measurement is considered accurate if the average of a series of measurements is close to the true value.

Defining Precision

Precision, often referred to as repeatability or reproducibility, is the degree to which repeated measurements under unchanged conditions show the same results. Precision is concerned exclusively with the distribution of the data points—the narrower the cluster, the higher the precision—regardless of whether that cluster is centered on the true value.

Reference Note: While colloquial language uses these terms interchangeably, professional engineering and laboratory reports must distinguish between them to properly identify whether a measurement system suffers from bias (accuracy issue) or instability/noise (precision issue).

Standards Citation

To maintain global uniformity, the definitions of accuracy and precision are governed by several international bodies. Adherence to these standards is mandatory for ISO certification and peer-reviewed scientific publication.

• ISO 5725-1: This standard defines accuracy as the closeness of agreement between a test result and the accepted reference value. It further divides accuracy into trueness (the closeness of the mean of a large number of replicates to the true value) and precision.
• The GUM (Guide to the Expression of Uncertainty in Measurement): Published by the BIPM, the GUM provides the framework for calculating uncertainty. It emphasizes that precision is quantified by the standard deviation of a set of measurements, whereas accuracy is evaluated by the error (the difference between the measured value and the true value).
• NIST (National Institute of Standards and Technology): NIST guidelines emphasize that precision is a measure of the random error, while accuracy is impacted by both random and systematic errors.

Convention Comparison Table

The following table summarizes the fundamental differences between accuracy and precision across various metrological dimensions.

Worked Examples

To illustrate these concepts, consider a laboratory scenario where a technician is measuring a certified 10.000 g standard weight using three different scales.

Scenario A: High Accuracy, Low Precision

The technician takes five measurements: 9.8g, 10.2g, 9.7g, 10.3g, and 10.0g.
Analysis: The average is (9.8 + 10.2 + 9.7 + 10.3 + 10.0) / 5 = 10.000g. The average is exactly the true value, meaning the scale is accurate. However, the range is 0.6g, indicating low precision.

Scenario B: Low Accuracy, High Precision

The technician takes five measurements: 10.51g, 10.52g, 10.50g, 10.51g, and 10.51g.
Analysis: The average is 10.51g, which is 0.51g away from the true value, indicating low accuracy (significant systematic bias). However, the values are extremely close to one another, indicating high precision.

Scenario C: High Accuracy, High Precision

The technician takes five measurements: 10.001g, 9.999g, 10.000g, 10.002g, and 9.998g.
Analysis: The average is 10.000g (accurate) and the standard deviation is minimal (precise). This is the ideal state for any measurement system.

Counter-Examples

Common misconceptions often lead to incorrect data reporting. Below are counter-examples of flawed reasoning.

• The “High Precision implies Accuracy” Fallacy: A student argues that because their digital caliper reads exactly 25.40mm three times in a row, the measurement must be correct. Error: The caliper could be improperly zeroed (offset error). The measurement is precise, but not accurate.
• The “Average implies Accuracy” Fallacy: A researcher claims a method is accurate because the mean of 100 trials equals the target value, despite a massive standard deviation. Error: While the trueness is high, the method is unreliable for single-point measurements due to poor precision.
• Confusing Resolution with Precision: A scale that displays four decimal places (high resolution) is often mistaken for a precise scale. Error: Resolution is the smallest increment a device can detect; precision is the ability to repeat that detection. A high-resolution device can still be imprecise if the readings fluctuate wildly.

Common Mistakes

When reporting measurements, professionals often fall into these traps. Avoiding these ensures your work meets ASTM E29 and significant figures standards.

• Over-reporting Significant Figures: Reporting a precise but inaccurate measurement to five decimal places suggests a level of confidence that the accuracy does not support.
• Ignoring Calibration: Assuming a new instrument is accurate. Precision is often built into the hardware, but accuracy must be verified via calibration against a known standard.
• Confusing Precision with Sensitivity: Sensitivity is the ratio of the change in output to the change in input. A highly sensitive instrument may be very precise, but if it isn’t calibrated, it remains inaccurate.

Quick Reference Table

Use this table for rapid identification of measurement issues during data analysis.

Related Rules

To fully master measurement reporting, you should explore the following related concepts on our reference site:

• Significant Figures: Learn how to determine which digits in a precise measurement are actually meaningful.
• Rounding Methods: Explore Banker’s Rounding (Round Half to Even) to avoid cumulative bias in large datasets.
• Error Propagation: Understand how precision errors in individual measurements compound during multiplication and division.
• Measurement Uncertainty: Transition from simple precision to calculating expanded uncertainty according to GUM guidelines.

The post Accuracy vs Precision: Definitions, Differences, and Why Both Matter appeared first on SignificantFiguresCalculator.

In the realm of metrology, error is defined as the difference between a measured value and the true value of the measurand. To maintain the highest standards of precision and rounding, one must distinguish between two fundamental types of error: Systematic Error and Random Error.

Systematic Error (Bias)

Systematic error is a consistent, repeatable offset that occurs in the same direction (either always too high or always too low). It affects the accuracy of a measurement. According to the Guide to the Expression of Uncertainty in Measurement (GUM), systematic errors can often be corrected if the source is identified.

Random Error (Noise)

Random error refers to unpredictable fluctuations in the measurement process. These errors are stochastic and affect the precision (or repeatability) of the measurement. Unlike systematic errors, random errors cannot be eliminated, only minimized through statistical averaging.

Convention Comparison Table

The following table provides a side-by-side comparison of the two error types to assist in rapid identification during laboratory or engineering audits.

Standards Citation

Professional metrology relies on codified standards to ensure global interoperability. When reporting error and uncertainty, the following standards are authoritative:

• ISO/IEC Guide 98-3 (GUM): The primary international standard for expressing uncertainty. It defines the distinction between Type A evaluation (statistical analysis of series of observations) and Type B evaluation (based on other means, such as calibration certificates).
• NIST Special Publication 260: Provides guidelines for the calibration of instruments, emphasizing the reduction of systematic bias through traceability.
• ASTM E29: Standard Practice for Using Significant Digits in Test Data to Minimize Round-Off Error. This ensures that the precision of the reported result reflects the actual uncertainty of the measurement process.

Worked Examples

Example 1: The Uncalibrated Digital Scale

A technician weighs a certified 100.00g mass. The scale consistently reads 100.20g, 100.21g, and 100.19g.

1. Identification: The readings are tightly clustered (high precision) but consistently higher than the true value. This indicates a systematic error of approximately +0.20g.
2. Reasoning: Because the error is unidirectional, it is a bias.
3. Fix: Perform a zero-point calibration or subtract the 0.20g offset from all future readings.

Example 2: Atmospheric Pressure Fluctuations

An engineer measures the diameter of a precision cylinder five times: 25.01mm, 24.98mm, 25.00mm, 25.03mm, and 24.97mm.

1. Identification: The values fluctuate around the target of 25.00mm. This is random error.
2. Reasoning: The errors are symmetric and unpredictable, likely caused by slight temperature shifts or operator variance.
3. Fix: Calculate the arithmetic mean. The mean of these five values is 24.998mm, which reduces the impact of the random noise.

Counter-Examples: Common Misidentifications

Warning: Confusing random error for systematic error leads to incorrect calibration, which can introduce new biases into a system.

Scenario: A researcher sees a measurement that is 5% off the expected value and immediately assumes the instrument needs calibration (Systematic Error).

The Error: If this was a single measurement, it could simply be a random outlier. Calibrating an instrument based on one anomalous data point creates a permanent systematic bias for all future correct measurements. This is a violation of GUM principles.

Correct Approach: Perform a series of repetitions. If the 5% offset persists across 10 trials, it is systematic. If the values scatter around the true value, it is random.

Common Mistakes

• Over-rounding before the final step: A critical error in precision reporting. Always maintain extra guard digits during calculations and round only at the final step according to Rounding Rules.
• Assuming “Average” eliminates all error: Averaging only reduces random error. If your scale is off by 1kg, averaging 100 weigh-ins will still leave you with a 1kg systematic error.
• Confusing Precision with Accuracy: A measurement can be highly precise (low random error) but wildly inaccurate (high systematic error).

Quick Reference Table: Identification Logic

Discipline Note

The approach to error differs slightly across fields. In Chemistry, systematic errors often stem from impurities in reagents (matrix effects). In Physics, they often arise from instrument limitations. In Engineering, tolerance intervals are used to define the acceptable bounds of both error types. Regardless of the field, this site provides the most rigorous reference for the subsequent rounding of these results, ensuring that the reported significant figures match the uncertainty of the measurement.

The post Systematic vs Random Error: How to Identify and Fix Each appeared first on SignificantFiguresCalculator.

Rule Statement

To round a nonzero number x to n significant figures:

1. Find the order of magnitude: m = floor(log10(abs(x))).
2. Scale so the first significant digit sits in the units place: scale = 10^(n - 1 - m).
3. Round the scaled value and divide back: y = round(x * scale) / scale.

In MATLAB, the compact numeric expression is y = round(x, n - 1 - floor(log10(abs(x)))) when x is nonzero. For x = 0, return 0 and handle formatting separately because log10(0) is -Inf. For display rather than numeric storage, sprintf('%.*g', n, x) or num2str(x, n) formats to n significant digits.

See Rounding Rules for the general digit-by-digit procedure and Significant Figures for counting conventions.

Software Behavior Note

MATLAB’s round has two important behaviors. First, round(x, k) rounds to k decimal places, not k significant figures. round(123.456, 3) returns 123.456, while three significant figures would be 123. Second, round breaks ties away from zero: round(0.5) is 1 and round(-0.5) is -1. That is not banker’s rounding; if you need round-half-to-even, implement it explicitly or use an external function. See Banker’s Rounding.

format short, format long, and format short e change only the command-window display. They do not round the stored value. num2str(x, n) and sprintf('%.*g', n, x) produce character output with n significant digits. To preserve trailing zeros as significant, use the # flag: sprintf('%#.*g', n, x) renders 12 as 12.0 for n = 3.

For arrays, vectorize with a zero guard:

scale = 10.^(n - 1 - floor(log10(abs(x)))); scale(x == 0) = 1; y = round(x .* scale) ./ scale; y(x == 0) = 0;

Worked Examples

Example 1: 123.456 to 3 significant figures

m = floor(log10(123.456)) = 2; exponent = 3 - 1 - 2 = 0; round(123.456, 0) = 123. Result: 123.

Example 2: 0.00123456 to 3 significant figures

m = floor(log10(0.00123456)) = -3; exponent = 3 - 1 - (-3) = 5; round(0.00123456, 5) = 0.00123. Result: 0.00123.

Example 3: 9.876 to 3 significant figures

m = 0; exponent = 2; round(9.876, 2) = 9.88. Note that this is not the same as rounding to 2 decimal places in all cases; the rule tracks the first significant digit.

Example 4: -0.04567 to 2 significant figures

abs(x) = 0.04567; m = -2; exponent = 2 - 1 - (-2) = 3; round(-0.04567, 3) = -0.046. Result: -0.046. The sign is retained; the significant digits are 4 and 6.

Counter-Examples

• Decimal places mistaken for significant figures: round(9.876, 3) gives 9.876, not 9.88.
• Display used as rounding: format short may show 3.1416, but pi remains full precision in memory. Do not rely on display for compliance data.
• Double rounding: rounding 0.4445 to 3 significant figures via an intermediate 2-decimal step can produce 0.445 instead of the correct 0.444 under some tie rules. Round once, at the end. See Double Rounding Error.
• Ignoring zero: floor(log10(0)) returns -Inf; the formula fails unless zero is explicitly handled.
• Forgetting abs: negative inputs produce complex logarithms or errors. Always use log10(abs(x)).

Quick Reference Table

For notation-specific rules, see Scientific Notation and Engineering Notation.

Standards Citation

Precision practice is governed by consensus standards. ASTM E29-22 covers the use of significant digits in test data and conformance decisions. ISO 80000-1:2009, Clause 6.4 gives general rounding rules for quantities and units. NIST SP 811, Section 8.1 provides SI rounding guidance, and JCGM 100:2008 (GUM), Clause 7.2.6 recommends reporting uncertainty to one or two significant digits. Use these when a project, lab, or regulator requires traceable rounding. See Measurement Uncertainty and GUM Guide.

Discipline Note

Engineering and physical-science reporting usually follows three principles. First, keep full precision during calculation; round only the final reported value. Second, let measurement uncertainty set the last significant digit. Third, match the reported value to the uncertainty: round uncertainty to one or two significant digits, then round the estimate to the same decimal place. In chemistry, addition/subtraction uses decimal-place rules while multiplication/division uses significant-figure rules; MATLAB does not infer those measurement rules automatically. In astronomy and physics, scientific notation avoids ambiguous trailing zeros. See Standard Deviation Reporting.

Common Mistakes

• Using round(x, n) as if it rounded to n significant figures.
• Confusing stored values with formatted strings.
• Rounding intermediate MATLAB variables and propagating the error.
• Assuming MATLAB uses banker’s rounding; it does not by default.
• Dropping significant trailing zeros when the number is displayed or exported.
• Using the sig-fig formula on zero without a guard.

MATLAB precision is not the same as measurement precision. A double can hold 15–17 significant decimal digits, but a reported result should carry only the digits justified by the measurement.

Sources & Further Reading

• MathWorks. round, sprintf, and num2str documentation. mathworks.com/help/matlab/ref/round.html
• ASTM E29-22. Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications. ASTM International.
• ISO 80000-1:2009. Quantities and units — Part 1: General, Clause 6.4.
• NIST SP 811. Guide for the Use of the International System of Units (SI), Section 8.1.
• JCGM 100:2008. Evaluation of measurement data — Guide to the expression of uncertainty in measurement (GUM), Clause 7.2.6.

The post How to Round to Significant Figures in MATLAB: Precision Control for Engineers appeared first on SignificantFiguresCalculator.