Description
Parse a finite decimal interval token with explicit open/closed endpoints.
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.
Parse a finite decimal interval token with explicit open/closed endpoints.
When to use this tool
Use it for qc specification open closed boundary token when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter token. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read lowerClosed, upperClosed, lower, upper. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Parse a complete interval token containing bracket or parenthesis endpoints and two signed decimal numerals separated by a comma. Require finite ordered bounds, then return the bounds and independent lowerClosed and upperClosed flags.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| lowerClosed | Lower Closed | Required. Boolean. |
| upperClosed | Upper Closed | Required. Boolean. |
| lower | Lower | Required. Finite number. |
| upper | Upper | Required. Finite number. |
{
"input": {
"token": "[1,5)"
},
"output": {
"lowerClosed": true,
"upperClosed": false,
"lower": 1,
"upper": 5
}
}Limitations and assumptions
- Spaces, exponent notation, and omitted endpoints are not supported. A syntactically valid open interval with equal bounds may be empty; the tool reports its token rather than judging specification adequacy.
- 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 specification open closed boundary token, 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 Rounding Decision Boundary Envelope
Bound a reported rounded result before applying an explicit one-sided decision limit.
- QC Specification One Sided Margin
Evaluate one explicitly supplied specification side and equality convention.