Description
Divide their gap by refresh rate and subtract supplied target seconds.
Experimental timing depends on clock origin, display refresh, exclusion rules and observation windows. Requested, quantized and actually measured times are different quantities, and a timing residual alone does not establish a psychological effect.
Divide their gap by refresh rate and subtract supplied target seconds.
When to use this tool
Use Stimulus Frame Interval Residual when you need an explicit experiment-timing or latency term.
How to use the tool and how it works
- Enter firstFrame, lastFrame, refreshHertz, suppliedTargetSeconds. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read intervalSeconds, residualSeconds. Use the output convention below.
Require positive refreshHertz and ordered frame indexes. Divide their gap by refresh rate and subtract supplied target seconds.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| firstFrame | First Frame | Required. Safe integer. |
| lastFrame | Last Frame | Required. Safe integer. |
| refreshHertz | Refresh Hertz | Required. Finite number; strictly above 0. |
| suppliedTargetSeconds | Supplied Target Seconds | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| intervalSeconds | Interval Seconds | Required. Finite number. |
| residualSeconds | Residual Seconds | Required. Finite number. |
{
"input": {
"firstFrame": 10,
"lastFrame": 40,
"refreshHertz": 60,
"suppliedTargetSeconds": 0.4
},
"output": {
"intervalSeconds": 0.5,
"residualSeconds": 0.09999999999999998
}
} Limitations and assumptions
- The gap is between frame positions, not an inclusive frame count. Actual dropped frames, variable refresh and display latency are not measured.
- 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 calibrated presentation and response hardware and the study's analysis protocol. Check raw timestamps, censoring, exclusion policy and uncertainty before interpreting timing contrasts.
References
Similar or alternative tools
- Experimental Psychology: Stimulus Frame Duration Rounding
Floor, ceil or nearest-half-up to whole frames and return realized duration and residual.
- Stimulus Frame Quantization Error
Use JavaScript Math.round(timeSeconds×frameRate), divide back into seconds and return quantized-minus-requested error.