Description
Return max(0,endLower-startUpper) and endUpper-startLower.
A time-window check needs explicit endpoints, inclusion rules and a common clock. Caller-supplied holding limits and temperature flags are model inputs; passing a local check does not establish a safe handling process.
Return max(0,endLower-startUpper) and endUpper-startLower.
When to use this tool
Use Cold Chain Clock Uncertainty Term when you need an explicit holding-window, clock or sampled-duration calculation.
How to use the tool and how it works
- Enter startLower, startUpper, endLower, endUpper. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read durationLower, durationUpper. Use the output convention below.
Require ordered start/end uncertainty bounds with some possible nonnegative duration. Return max(0,endLower-startUpper) and endUpper-startLower.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| startLower | Start Lower | Required. Finite number. |
| startUpper | Start Upper | Required. Finite number. |
| endLower | End Lower | Required. Finite number. |
| endUpper | End Upper | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| durationLower | Duration Lower | Required. Finite number. |
| durationUpper | Duration Upper | Required. Finite number. |
{
"input": {
"startLower": 0,
"startUpper": 2,
"endLower": 10,
"endUpper": 12
},
"output": {
"durationLower": 8,
"durationUpper": 12
}
}Limitations and assumptions
- These are possible elapsed-time bounds, not probability limits. Source clock uncertainty and handling safety are not established.
- 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
Use the applicable validated food-safety procedure and complete temperature/time history. Resolve sensor calibration, sampling gaps and product-specific limits before making handling decisions.
References
Similar or alternative tools
- Food Temperature Logger Time Offset Term
Add offsetSeconds to recordedTime, then subtract referenceTime for correctedGap.
- Food Sample Holding Time Caller Margin
Subtract endpoints, compute limit-minus-elapsed margin and compare inclusively.