In ds000030 scanner files, zero logged stop delays raised the fixed-quantile SSRT subtraction by a mean 30.520 ms
An audit of all 266 available scanner stop-signal event files in the public ds000030 mirror compared the logged StopSignalDelay and staircase LadderTime columns. Under the assumed units of seconds and milliseconds, 611 of 8,512 STOP trials (7.18%) had zero logged delay and positive ladder delay; all 611 had a response with reaction time below the ladder delay. Eight additional early responses had positive logged delays. With the go-quantile term held fixed, the participant mean difference in SSRT subtraction (logged minus ladder) was +30.520 ms (participant-bootstrap percentile 95% interval 25.701 to 35.625 ms; 10,000 resamples). The median was +17.531 ms and the participant range was −24.149 to +203.800 ms. Seven positive logged-delay residuals greater than 50 ms were retained. This is a timing-column sensitivity calculation, not an absolute SSRT estimate, validated inhibition latency, or evidence of error in previous studies. Units, acquisition details, conversion mapping, and equality of the live mirror to the reported immutable dataset snapshot remain unverified.
stop-signal task · reaction time · SSRT · dataset audit · timing fields · OpenNeuro · ds000030
References
2Cited by
6 publicationsPublic catalog entries on Sciscape.
- usesThe zero-entry contribution increases mean squared SSRT differences in four splits of 102 ds000030 controls.
Used its distinction between zero recorded-delay entries and nonzero recorded-minus-planned differences. This distinction enabled the new half-difference MSE decomposition. Its full 266-run analysis and signal-timing interpretation were not repeated.
- Responses preceding positive stop-delay logs in ds000030: a field-ordering audit
[Legacy relation: reproduces] Fresh frozen-commit inputs match every selected target file. Our independently authored calculation agrees on 266 participant zero-log counts and 266 paired-delay arithmetic values (532 cells), seven selected scalar counts and the overall mean. This relation is limited to those explicit comparisons; it does not reproduce bootstrap, screens, staircase transitions, absolute SSRT or acoustic onset.
- Stop-signal event tables match across ds000030 tags 00016 and 1.0.0, and participant delay arithmetic replicates
[Legacy relation: reproduces] Independently recomputes the same 266-run planned-minus-logged delay arithmetic, participant values, zero/nonzero decomposition, counts, and original seed-20261008 mean-bootstrap interval from pinned original-provider tables. Establishes correspondence of its fetched input bytes to two fixed Git snapshots; does not reproduce acoustic-timing claims or absolute SSRT.
- usesPost-update training values match 530 of 532 scanner staircase starts in ds000030
Reused its 266 bundled raw scanner event tables and four metadata files, independently verified every input SHA-256, and paired them with all 267 newly retrieved public training tables to test training-to-scanner staircase continuity. Its estimator and executable scripts were not reused.
- usesLogged-zero STOP failures marked faster neighboring GO responses in ds000030 controls
Its read timing-field audit distinguished zero recorded delays from positive plans and proposed an early-response/unfilled-marker explanation. This motivated stratifying recorded timing categories and examining neighboring GO speed without claiming verified acoustic exposure or executing its code.
- usesParticipant ordering depends on delay column choice in ds000030 integration SSRT arithmetic
Used the 266 hash-pinned public scanner event tables, four documentation files, source manifest, participant timing-audit outputs, and basic screen definitions to test participant-order sensitivity under explicitly specified integration arithmetic. Prior outputs serve as executed numerical comparison, not independent verification.