Description
Compare supplied reaction time with an anticipation cutoff.
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.
Compare supplied reaction time with an anticipation cutoff.
When to use this tool
Use Reaction Time Anticipation Threshold Flag when you already have reactionTimeMilliseconds, anticipationThresholdMilliseconds and need to compare supplied reaction time with an anticipation cutoff.
How to use the tool and how it works
- Enter reactionTimeMilliseconds, anticipationThresholdMilliseconds. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read flagged, marginMilliseconds. Inspect flagged before interpreting the associated values.
Require both millisecond quantities>=0; flag reactionTime<threshold and return reactionTime-threshold.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| reactionTimeMilliseconds | Reaction Time Milliseconds | Required. Finite number; minimum 0. |
| anticipationThresholdMilliseconds | Anticipation Threshold Milliseconds | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| flagged | True only strictly below the supplied millisecond threshold; equality is false. | Required. Boolean. |
| marginMilliseconds | Margin Milliseconds | Required. Finite number. |
{
"input": {
"reactionTimeMilliseconds": 80,
"anticipationThresholdMilliseconds": 100
},
"output": {
"flagged": true,
"marginMilliseconds": -20
}
}Limitations and assumptions
- Equality is not flagged. The threshold is supplied, not a validated universal criterion; no anticipatory behavior, response validity or diagnosis is determined.
- 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.