Description
Compare two supplied timestamp envelopes, including touching endpoints as possible overlap.
Training and research event times need synchronized origins, explicit clock corrections and stated boundary precision. A numeric response delay or overlap describes the supplied records and does not assess the quality or timing of emergency care.
Compare two supplied timestamp envelopes, including touching endpoints as possible overlap.
When to use this tool
Use Deidentified Event Precision Overlap when checking a supplied simulation or research event-time convention.
How to use the tool and how it works
- Enter firstTime, firstHalfwidth, secondTime, secondHalfwidth. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read overlapWidth, mayOverlap. Inspect mayOverlap before interpreting the associated values.
Require nonnegative firstHalfwidth and secondHalfwidth. overlapWidth is the nonnegative intersection length of the two symmetric time intervals. mayOverlap uses abs(firstTime-secondTime) <= firstHalfwidth+secondHalfwidth.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| firstTime | First Time | Required. Finite number. |
| firstHalfwidth | First Halfwidth | Required. Finite number; minimum 0. |
| secondTime | Second Time | Required. Finite number. |
| secondHalfwidth | Second Halfwidth | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| overlapWidth | Overlap Width | Required. Finite number. |
| mayOverlap | True even when the supplied intervals merely touch and overlapWidth is zero. | Required. Boolean. |
{
"input": {
"firstTime": 10,
"firstHalfwidth": 2,
"secondTime": 13,
"secondHalfwidth": 2
},
"output": {
"overlapWidth": 1,
"mayOverlap": true
}
}Limitations and assumptions
- Touching intervals have mayOverlap = true but overlapWidth = 0. The bounds are supplied, not confidence intervals or proof two deidentified events are the same event.
- 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 original synchronized event records and appropriate professional protocols for clinical interpretation or live decisions.
References
Similar or alternative tools
- Research Arrival Clock Precision Gap
width = latestArrival-earliestArrival; earliestOffset and latestOffset subtract referenceTime from the respective endpoints.
- Research Arrival Event Time Gap
Return signedGap = eventTime-suppliedEventOffset-arrivalTime and eventBeforeArrival when the offset-corrected event is strictly earlier than arrivalTime.