Description
Return maximum paired prompt timing jitter and a bound flag.
Behavioral timing and response summaries need compatible clocks, exposure bases, baseline definitions and observation methods. A latency correction or rate change is descriptive arithmetic rather than a demonstration of learning, habituation, extinction or causal intervention benefit.
Return maximum paired prompt timing jitter and a bound flag.
When to use this tool
Use Prompt Time Jitter Bound when checking the stated behavioral-research timing, baseline or response-change convention.
How to use the tool and how it works
- Enter plannedTimes, observedTimes, suppliedBound. Follow any array-alignment requirements below. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read maximumAbsoluteJitter, exceedsBound. Inspect exceedsBound before interpreting the associated values.
Return maximum paired prompt timing jitter and a bound flag. Require aligned planned/observed times and nonnegative suppliedBound; take max absolute difference, zero for empty input, exceeds uses strict >.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| plannedTimes | Planned Times | Required. Array of finite number; maximum items 256. |
| observedTimes | Observed Times | Required. Array of finite number; maximum items 256. |
| suppliedBound | Supplied Bound | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| maximumAbsoluteJitter | Largest absolute paired timing gap; zero on an empty input is a bookkeeping identity. | Required. Finite number. |
| exceedsBound | Exceeds Bound | Required. Boolean. |
{
"input": {
"plannedTimes": [
1,
2
],
"observedTimes": [
1.1,
1.8
],
"suppliedBound": 0.15
},
"output": {
"maximumAbsoluteJitter": 0.19999999999999996,
"exceedsBound": true
}
}Limitations and assumptions
- An empty zero is not a verified stable schedule; no prompt generation, synchronization or appropriate bound is provided.
- 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
Inspect the actual study design, records and calibration; use an appropriate complete causal/statistical analysis and qualified interpretation for substantive conclusions.
References
Similar or alternative tools
- Prompt Response Latency Ratio
Return second/first response-latency ratio.
- Reinforcement Delivery Clock Gap
Return raw and clock-corrected reinforcement lag.