The 126 selected control event tables match across four OpenNeuro ds000030 tags
A fixed set of 126 control scanner stop-signal event tables was compared across OpenNeuro ds000030 Git tags 00001, 00002, 00016, and 1.0.0. All 378 nonbaseline comparisons were byte-identical, with no missing or changed selected table; dataset-description hashes differed. In 4,032 STOP trials, 274 rows across 84 participants had zero recorded delay and positive planned delay, and all had a response before the planned delay. Across 126 participants, mean integration estimates were 225.176 ms using recorded delays, 197.839 ms using planned delays, and 195.116 ms using a hybrid sensitivity rule. The recorded-minus-planned contrast was 27.337 ms; the target behavioral screen retained 102 participants and had a 27.849 ms contrast. A separate Decimal implementation passed 29 specified reference comparisons. This is a version-scoped comparison and arithmetic reproduction, not validation of a timing correction, acoustic onset, biological effect, or complete archive equivalence. Original acquisition and conversion causes remain unresolved.
stop-signal task · stop-signal reaction time · OpenNeuro · ds000030 · snapshot comparison · event tables · data provenance · computational reproduction · reaction time · timing fields
References
6- Literal recorded stop delays increase fixed-integration SSRT estimates in ds000030 controls sci:sha256:7a066009ca96d094daa61267daf87c6624c3893851b2c480e640b3ff1927c1a7
[Legacy relation: reproduces] Used its cohort and anomaly definitions and authenticated published participant/summary outputs to computationally reproduce 29 specified count, rank, behavioral-screen and timing-arithmetic comparisons using a separately written Decimal implementation; its bootstrap intervals and separate staircase checks were not reproduced. Added an explicit fixed-cohort four-tag event-byte comparison.
- usesdoi:10.18112/openneuro.ds000030.v1.0.0
The 1.0.0 event tables and metadata are the fixed baseline used in this four-tag comparison; other tags are identified by their recorded Git commits, raw URLs, hashes, and licenses in original/data/manifest.json.
- doi:10.1038/sdata.2016.110
- doi:10.7554/eLife.46323
- doi:10.7554/eLife.88652
- doi:10.1162/imag_a_00454
Cited by
5 publicationsPublic catalog entries on Sciscape.
- usesAll STOP responses more than 5 ms before LadderTime have zero recorded delay in 126 CONTROL scanner runs.
We used the 126 CONTROL scanner event inputs and their source manifest. Their bytes agree with new downloads from the pinned public source.
- The 126 selected CONTROL event tables match across four ds000030 Git revisions
[Legacy relation: reproduces] Used the fixed sample, four commits, method definitions, and authenticated output files. New downloads and separate exact-fraction code agree with all 2,520 participant fields, the tested sample counts and means, and all 504 version-comparison rows. No bootstrap or staircase analysis was reproduced.
- usesFour ds000030 Git versions have the same 14 training and scanner delay history differences.
We used its four-version scope and its distinction between Git tags and legacy revision 1.0.5. These facts set the expanded audit of 1,066 participant task files.
- usesA code rule gives the recorded arrow for all 45 scanner responses in GO trials 49–96 of ds000030 sub-10527.
We used the source hashes and the 102-participant screen reference to fix the inputs and compare participant selection.
- usesSelection of correct GO trials changes 35 of 102 SSRT estimates with the ceiling rank in ds000030
I used its 126-run sample, source file manifest, and baseline SSRT table. These inputs enabled 504 checks of the source selection, screen membership, and baseline estimates.