Recorded response correctness differs from stopping accuracy in ds000030 controls
In the OpenNeuro ds000030 control scanner event files, `SubjectResponseCorrectness` records arrow-response correctness and does not identify successful stopping. Across 4,032 STOP rows from 126 controls, a hypothetical mapping of IncorrectResponse to stop failure and CorrectResponse to stop success misclassifies 3,950 rows (97.97%). A participant-weighted comparison of subsequent successful-GO response times found a failed-minus-successful STOP difference of −5.76 ms (n=124; 95% participant-bootstrap interval −18.55 to 7.12 ms). The matched comparison using the response-correctness flag was +5.54 ms (n=124; interval −7.12 to 18.15 ms). Neither comparison establishes a directional association. The audit covers one recorded control cohort; it cannot establish acoustic stimulus delivery, causality, clinical mechanisms, or equivalence of effects.
stop-signal task · response correctness · stopping accuracy · event data · OpenNeuro · post-stop response time · data reuse
References
6- usesdoi:10.18112/openneuro.ds000030.v1.0.0
This is the exact-version DOI for the OpenNeuro ds000030 1.0.0 event files analyzed in this contribution; its saved metadata record CC0.
- doi:10.1038/sdata.2016.110
- doi:10.1002/hbm.25347
- doi:10.1016/j.jmp.2012.04.001
- doi:10.3758/s13428-021-01631-4
- doi:10.1037/a0021800
Cited by
7 publicationsPublic catalog entries on Sciscape.
- usesNone of 126 ds000030 CONTROL runs has three selected triplets in each of four arrow and button history cells.
The response-label audit gives the distinction between no response, decoded button response, and nonzero unmapped response used in these history checks.
- Logged-zero STOP failures marked faster neighboring GO responses in ds000030 controls
[Legacy relation: reproduces] Independently reconstructed three reported post-stop RT means, sample sizes and bootstrap intervals on its exact source lock and selection; extended the same data with a fixed-ID mixture decomposition and zero-versus-positive GO context. Computational reproduction, not a new biological sample.
- usesDelay-field choice changes participant ranks and GO-speed associations in 126 ds000030 control runs
Its read response-coding audit informed STOP-response classification from raw button codes with RT/outcome concordance, and the explicit sensitivity excluding sub-10527 with no GO choices labeled correct.
- usesA code rule gives the recorded arrow for all 45 scanner responses in GO trials 49–96 of ds000030 sub-10527.
The missing-button result determined the selected participant and the question about arrow information in response codes.
- usesRemoval of one STOP record changes H SSRT by at least 10 ms in 37 of 122 selected ds000030 controls with the rank rule.
Its response-code audit informed interpretation of the known unmapped button codes in sub-10527 and the labeled later sample check. No prior code or behavioral comparison result was used.
- The post-STOP reaction-time difference was larger with arrow repetition in 125 ds000030 CONTROL runs
[Legacy relation: reproduces] This work uses the 131 source-file versions and sample rule from the earlier result. New code gives the same 125 participant identifiers, mean RT difference, and bootstrap interval bounds.
- usesMean GO reaction time is higher at the first three GO trials after STOP in 125 ds000030 control runs.
The 131-file source lock, public event tables, and TrialOutcome label audit enabled the three-position history analysis. The same data also give the reported 42.61 ms comparison to two decimals.