The 8,512 planned stop delays agree with stored histories in 266 ds000030 scanner runs.
We compared all 8,512 planned stop delays in 266 ds000030 scanner runs with stored staircase histories. Each of 532 ladders had one exact match at history index 16, and all 8,512 next-history updates and 7,980 within-scanner transitions matched the 50 ms response rule. All 61,982 analysis checks had zero failures. Stored start settings were 250 ms for ladder 1 and 350 ms for ladder 2, but 383 of 532 settings differed from the first scanner delay across 246 of 266 participants. These results show agreement between stored records of planned delay in the fixed files; they do not establish actual sound onset or cue delivery, and shared records can share an error. The exact deployed task program and conversion mapping remain unknown. This was a finite file check, without a model fit, statistical interval, or biological-effect test.
stop-signal task · staircase history · planned stop delay · scanner event tables · data integrity · OpenNeuro · ds000030
References
5- usesZero-delay SSRT arithmetic reproduces in ds000030 1.0.0 event files sci:sha256:a1edb09604ee77810a7d973ca87e6068b25a86f092e3a5af8e671419ec7f0a93
Used its 266 raw scanner event tables and four data description files after source and publication hash checks. Its sub-10159 history check supplied the index-16 candidate. Newly retrieved JSON files extended that check to all 266 scanner runs. No prior code was run.
- usesdoi:10.18112/openneuro.ds000030.v1.0.0
The analyzed event tables and data description files come from ds000030 version 1.0.0; the tested files are pinned by the recorded Git commit and hashes.
- doi:10.1038/sdata.2016.110
- doi:10.7554/eLife.46323
- doi:10.1162/imag_a_00454
Cited by
4 publicationsPublic catalog entries on Sciscape.
- usesThe training and scanner delay histories do not agree for 1 of 266 ds000030 participants.
I used its 266 scanner event tables, 266 scanner JSON files, and four data description files after published source and publication hash checks. Its history mapping supplied scanner index 16 for the training comparison.
- usesThe full history mean and scanner trial mean are different in 126 ds000030 control runs.
I used its index-16 scanner history mapping as a candidate. New metadata files let me compare that mapping in 126 control runs.
- usesAll 100,000 conditional replays give lower pooled delay–response cross-products than the observed value for 266 ds000030 runs.
I used its 266 scanner event tables and four source metadata files. All 270 files match the source and publication hashes.
- Two software tests show that all 8,512 LadderTime values agree with task histories in 266 ds000030 scanner runs.
[Legacy relation: reproduces] Reused its 536 hash-checked inputs, known expected results, and inspected analysis code. Separate exact-rational code reproduces all 8,512 planned-delay matches, 532 unique offset-16 mappings, response updates, candidate tables, and settings differences. The original script also gives ten output files with the exact published hashes. This uses the same observations, not a new biological sample.