Description
Measure a supplied diary-response timestamp lag.
Behavioral records distinguish observed outcomes, missing observations, response deadlines, code conflicts and sampling opportunities. Unobserved trials differ from observed wrong responses, while time coverage differs from event probability. Supplied observations and cutoff values do not by themselves validate a task or identify a behavioral mechanism.
Measure a supplied diary-response timestamp lag.
When to use this tool
Use Diary Prompt Response Lag when you already have promptTimestampSeconds, responseTimestampSeconds and need to measure a supplied diary-response timestamp lag.
How to use the tool and how it works
- Enter promptTimestampSeconds, responseTimestampSeconds. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read lagSeconds, precedesPrompt. Inspect precedesPrompt before interpreting the associated values.
Return response-prompt seconds and a flag for response<prompt.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| promptTimestampSeconds | Prompt Timestamp Seconds | Required. Finite number. |
| responseTimestampSeconds | Response Timestamp Seconds | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| lagSeconds | Lag Seconds | Required. Finite number. |
| precedesPrompt | Precedes Prompt | Required. Boolean. |
{
"input": {
"promptTimestampSeconds": 1000,
"responseTimestampSeconds": 1120
},
"output": {
"lagSeconds": 120,
"precedesPrompt": false
}
} Limitations and assumptions
- Negative lags are retained rather than rejected. Clock alignment, actual prompt receipt, response validity and participant compliance 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 the complete protocol, observation records and analysis plan. Check missingness, coding rules, timing and sampling design before interpreting local counts, labels or interval fractions as research outcomes or appropriate interventions.
References
Similar or alternative tools
- Response Omission Versus Late Tag
Distinguish supplied omitted, late and within-window responses.
- Observer Onset Tolerance Match
Compare supplied observer-onset disagreement with a tolerance.