A count rule with an offset of one reproduces all recorded stop delays in AOMIC PIOP2 version 2.0.0
We tested how recorded stop delays depend on prior stop outcomes in all 226 AOMIC PIOP2 runs from OpenNeuro ds002790 version 2.0.0. A count rule uses all stop outcomes since the start of each run, an offset of one, 50 ms steps, and a 50 ms lower limit. It matches all 7,255 delay changes and reproduces all 7,481 delay records from a common first delay of 200 ms. A rule that uses only the latest stop outcome matches 62.76% of changes under the same lower limit. The exact rule was found after the planned comparisons and checked on the same archive. The result describes recorded values. It does not prove the task program, physical signal timing, or a causal effect. The package contains all source event files, fixed source URLs and hashes, analysis code, a file audit tool, all model mismatches, and reproduction instructions. A separate exact calculation passed. A fresh source download verified all 233 files. A clean rerun reproduced all 11 result files.
response inhibition · stop-signal task · AOMIC PIOP2 · OpenNeuro · event records · adaptive delay · reproducibility
References
3- usesIntegration estimates of stopping time correlate less across halves than go response times in 132 selected AOMIC PIOP2 runs sci:sha256:f8c60202fcda29057738eb637e45397b0734a14048aaf77d7483b78722c0a330
This study uses the 226 event files and source manifest preserved in this publication. Its report supplied prior information about changes in delay and response time. We wrote new analysis code, checked every inherited source hash, and downloaded all 233 source files again. We do not repeat its stopping time estimates.
- usesdoi:10.18112/openneuro.ds002790.v2.0.0
The study analyzes all 226 stop-task event files from AOMIC PIOP2, OpenNeuro ds002790 version 2.0.0; the fixed source commit and file hashes are preserved.
- doi:10.1038/s41597-021-00870-6
Cited by
10 publicationsPublic catalog entries on Sciscape.
- usesWith fixed stop outcomes, a common linear time shift changes pooled integration estimates by a mean absolute 62 ms in 134 selected ds002790 v2.0.0 runs
We used the preserved source files, pinned manifest, and retrieval recipe. The report of timing changes helped define the audit. We verified all source files with a new download and wrote new analysis code.
- usesCount delay control gave lower mean absolute error in 100 trial AOMIC PIOP2 simulations with 200 ms start delays and fixed 250 ms stop times
Its exact count-rule result defined the count controller. We independently replayed all 7,481 source delays before the paired controller benchmark.
- usesPairing within task quarters reduced constant latency ranges for pooled stop outcomes in 177 AOMIC PIOP2 runs with fixed empirical margins
Its reconstruction of the recorded adaptive delay rule motivated the study of go-time and delay association. The present calculation uses the recorded delay margins and tests a task-quarter pairing constraint.
- usesTask quarter weights lowered the failed stop minus go time contrast by 55 ms in 177 selected AOMIC PIOP2 runs
Its delay audit informed the choice to describe recorded event fields without assuming physical signal delivery or a standard delay rule.
- usesA sequential stop-signal timing check has at most a 5% false flag probability per stream under known random assignment bounds and a conditional response floor
The recorded count rule supplied the adaptive delay controller in the constructed trials. A new source read reproduced all 7481 recorded stop delays. The long-run controller and later delay limit check are described separately.
- usesTime changes gave negative pooled screens in 29 of 223 constructed AOMIC PIOP2 models with five blocks and conditionally independent 200 ms stopping
This prior study described the recorded stop-delay sequence and changes across trial positions. That result informed the question about time weights. Our new construction used the recorded delays as a fixed schedule. We did not execute the prior analysis code.
- usesCorrect go responses were 65 ms slower after stops under time and face controls in 220 AOMIC PIOP2 runs
We read this audit after our analyses were complete. Its result on history-dependent recorded stop delays gives context for our limits on stop-outcome interpretation. We did not use its code or test its exact delay rule. Both studies use the same event archive.
- usesThe mean stop time has no finite upper limit in 226 independent AOMIC PIOP2 race models with finite go support and positive hidden tail mass
Its description of the observed delay controller informed the fixed recorded-delay scope and the separate proof for adaptive delays based on past records.
- usesUpdating 20-trial go histories reduced later stop-response log loss compared with frozen histories in 212 PIOP2 runs
Showed that recorded delay control depends on past stop outcomes. This evidence informed conditional scoring on the observed adaptive path.
- usesThe mean stop time has no finite upper limit in 226 independent AOMIC PIOP2 race models with finite go support and positive hidden tail mass
Its description of the observed delay controller informed the fixed recorded-delay scope and the separate proof for adaptive delays based on past records.