Description
Bound a reported rounded result before applying an explicit one-sided decision limit.
Quality records separate measured results, reference values, acceptance rules, and supporting evidence. Arithmetic consistency and record coverage can be checked against supplied criteria without establishing traceability, approving a method, or deciding product conformity.
Bound a reported rounded result before applying an explicit one-sided decision limit.
When to use this tool
Use it for qc rounding decision boundary envelope when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter reported, increment, limit, upperLimit. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read minimum, maximum, definitelyPass, definitelyFail. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require positive increment and form minimum=reported-increment/2 and maximum=reported+increment/2. For an upper limit, definitelyPass tests maximum<=limit and definitelyFail tests minimum>limit; reverse the envelope ends and directions for a lower limit.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| reported | Reported | Required. Finite number. |
| increment | Increment | Required. Finite number; strictly above 0. |
| limit | Limit | Required. Finite number. |
| upperLimit | Upper Limit | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| minimum | Minimum | Required. Finite number. |
| maximum | Maximum | Required. Finite number. |
| definitelyPass | Definitely Pass | Required. Boolean. |
| definitelyFail | Definitely Fail | Required. Boolean. |
{
"input": {
"reported": 10,
"increment": 1,
"limit": 10,
"upperLimit": true
},
"output": {
"minimum": 9.5,
"maximum": 10.5,
"definitelyPass": false,
"definitelyFail": false
}
}Limitations and assumptions
- These are closed-envelope arithmetic tests, not a reconstruction of every rounding convention. Both flags may be false when the envelope straddles the decision boundary.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For qc rounding decision boundary envelope, check the source records and the supplied rule before comparing the result with another method. Use a separate evidence or method review when arithmetic consistency alone cannot establish the required conclusion.
References
Similar or alternative tools
- QC Result Rounding Closure Token
Inspect a supplied nearest-rounding interval and tie endpoint convention without rerounding an assay result.
- QC Specification Open Closed Boundary Token
Parse a finite decimal interval token with explicit open/closed endpoints.