Skip to content

Main content

QC Result Rounding Boundary

Compare explicit raw and reported values against the same supplied boundary without rounding either value.

Loading tool…

Description

Compare raw and reported results against the same supplied boundary.

Quality-control results depend on measurement basis, calibration reference, rounding, limit inclusion and decision rules. A raw result can lie on a different side of a boundary from its reported value. Guard bands and relative differences must retain their exact definitions; a local comparison does not select a valid specification or establish conformance.

Compare raw and reported results against the same supplied boundary.

When to use this tool

Use QC Result Rounding Boundary when you already have rawResult, reportedResult, suppliedBoundary and need to compare raw and reported results against the same supplied boundary.

How to use the tool and how it works

  1. Enter rawResult, reportedResult, suppliedBoundary. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read rawAtOrAbove, reportedAtOrAbove, crossesBoundary. Inspect rawAtOrAbove, reportedAtOrAbove, crossesBoundary before interpreting the associated values.

Return raw>=boundary and reported>=boundary; crossesBoundary is inequality of those two Boolean results.1

Input fieldMeaning and unitsAccepted input
rawResultRaw ResultRequired. Finite number.
reportedResultAlready reported value; this tool performs no rounding.Required. Finite number.
suppliedBoundarySupplied BoundaryRequired. Finite number.
Output fieldInterpretationReturned shape
rawAtOrAboveRaw At Or AboveRequired. Boolean.
reportedAtOrAboveReported At Or AboveRequired. Boolean.
crossesBoundaryCrosses BoundaryRequired. Boolean.
json
{
  "input": {
    "rawResult": 9.96,
    "reportedResult": 10,
    "suppliedBoundary": 10
  },
  "output": {
    "rawAtOrAbove": false,
    "reportedAtOrAbove": true,
    "crossesBoundary": true
  }
}

Limitations and assumptions

  • The reported value is supplied, not rounded by this tool; no rounding policy, uncertainty or actual acceptance criterion is inferred.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Apply the documented measurement method, calibration records and complete decision rule when judging a result. Keep raw values, reported values, uncertainty and endpoint inclusion visible; a supplied guard band or replicate term does not select that rule.

References

  1. Calculation and input contract: quality-control/qc-result-rounding-boundary — tool.io

Similar or alternative tools