Description
Return reward-event delay and expected-delay residual.
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 reward-event delay and expected-delay residual.
When to use this tool
Use Reward Event Contingency Gap when checking the stated behavioral-research timing, baseline or response-change convention.
How to use the tool and how it works
- Enter eventAt, rewardAt, expectedDelay. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read delay, residual. Use the output convention below.
Return reward-event delay and expected-delay residual. Require expectedDelay >= 0; delay = rewardAt-eventAt, residual = delay-expected.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| eventAt | Event At | Required. Finite number. |
| rewardAt | Reward At | Required. Finite number. |
| expectedDelay | Expected Delay | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| delay | Delay | Required. Finite number. |
| residual | Signed difference in the direction stated above, with matching units. | Required. Finite number. |
{
"input": {
"eventAt": 10,
"rewardAt": 14,
"expectedDelay": 3
},
"output": {
"delay": 4,
"residual": 1
}
}Limitations and assumptions
- Negative observed delay is retained; event identity, reinforcement efficacy and appropriate timing 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
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
- Behavior Event Boundary Offset
Return signed event-to-boundary offset.
- Response Latency Clock Offset
Return response latency after a supplied clock offset.