Description
Split a supplied send-read-reply timeline.
Communication measurements need an explicit event origin, clock correction, count unit and exposure denominator. Timing and coverage records can be summarized without detecting actual speech, verifying message delivery or determining readability, accessibility or communication quality.
Split a supplied send-read-reply timeline.
When to use this tool
Use Message Read Reply Latency Split when checking the stated communication timing, rate, representation or coverage convention.
How to use the tool and how it works
- Enter sent, read, replied. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read deliveryToRead, readToReply, total. Use the output convention below.
Split a supplied send-read-reply timeline. Require sent <= read <= replied; deliveryToRead = read-sent, readToReply = replied-read, total = replied-sent.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| sent | Sent | Required. Finite number. |
| read | Read | Required. Finite number. |
| replied | Replied | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| deliveryToRead | read-sent; includes the entire send-to-read span, not a separately observed delivery event. | Required. Finite number. |
| readToReply | Read To Reply | Required. Finite number. |
| total | Total | Required. Finite number. |
{
"input": {
"sent": 100,
"read": 130,
"replied": 180
},
"output": {
"deliveryToRead": 30,
"readToReply": 50,
"total": 80
}
}Limitations and assumptions
- The first interval includes all time from sending to reading, not separately measured delivery; event evidence and causality are not verified.
- 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 actual synchronized media/message records, appropriate text measurement and user evaluation for complete communication or accessibility assessment.
References
Similar or alternative tools
- Message Response Span
Return clock-corrected message response span.
- Interpretation Channel Delay Sign
Return interpretation delay after correcting both clocks.