Description
Distinguish supplied omitted, late and within-window responses.
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.
Distinguish supplied omitted, late and within-window responses.
When to use this tool
Use Response Omission Versus Late Tag when you already have responded, responseElapsed, deadlineElapsed and need to distinguish supplied omitted, late and within-window responses.
How to use the tool and how it works
- Enter responded, responseElapsed, deadlineElapsed. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read status. Use the output convention below.
Require both elapsed times>=0; choose omitted when responded=false, otherwise late only for responseElapsed>deadlineElapsed.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| responded | Responded | Required. Boolean. |
| responseElapsed | Response Elapsed | Required. Finite number; minimum 0. |
| deadlineElapsed | Deadline Elapsed | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| status | Omitted overrides timing when responded=false; deadline equality is within-window. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"responded": false,
"responseElapsed": 0,
"deadlineElapsed": 5
},
"output": {
"status": "omitted"
}
}Limitations and assumptions
- Equality is within-window, and elapsed time is still validated for an omitted response. No response detection, task suitability or ability is assessed.
- 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
- Reaction Time Anticipation Threshold Flag
Compare supplied reaction time with an anticipation cutoff.
- Diary Prompt Response Lag
Measure a supplied diary-response timestamp lag.