The NULL onset field has one value in each of 266 ds000030 task files.
An audit of all 266 stopsignal task files at OpenNeuro ds000030 commit 4070b6eea231517bfeff42527a46d9d166ac4e13 found that each file has one NULL onset value, while its 128 NULL rows have different TimeCourse values. Of 34,048 NULL rows, 223 files have onset 0 s, 42 have 2 s, and one has 4 s. All unadjusted NULL onsets are zero. NULL onset values equal the schedule adjustment. With onset as interval start, all 128 blank intervals overlap in each file; the maximum overlap is 128 and total union duration is 998.000 s. With TimeCourse as interval start, maximum overlap is one and total union duration is 43,710.750 s. These are calculations on stored fields, not measurements of display timing. The release tag for the tested commit is unknown, and the exact converter and display timing records were not available. A zero initial value in inspected task code is a possible cause, not an established cause. All counts apply only to the tested files.
stop-signal task · event timing · NULL onset · task schedule · OpenNeuro · data audit · interval overlap
References
5- usesZero-delay SSRT arithmetic reproduces in ds000030 1.0.0 event files sci:sha256:a1edb09604ee77810a7d973ca87e6068b25a86f092e3a5af8e671419ec7f0a93
Used its 266 task event tables and four metadata files. All 270 files match source and publication hashes. These inputs enabled the exact NULL timing audit. No prior code was run.
- usesTask schedule data predict later trial labels with 99.72% accuracy in 266 ds000030 participant tests sci:sha256:733489c123245d526f3cd87587b12f370ddafc90ab5ca45176a3221841a383d3
Its warning about NULL onset values informed the timing audit question. The new code audits all NULL rows and compares literal and schedule intervals. Its prediction code was not used.
- supportsRecorded-delay SSRT ranks agree less across task halves than scheduled-delay ranks in ds000030 1.0.0 sci:sha256:03eda0d10367a515f2d7c9a565288d24c73e905c391ff14537f2c2b05e031cde
The executed audit agrees with its failed full-row onset order in all 266 files and strict active-row order. This relation concerns timing order only. It does not test its stopping-time rank correlations.
- usesdoi:10.18112/openneuro.ds000030.v1.0.0
The audit used the ds000030 1.0.0 task event files and metadata. The tested Git commit is recorded separately; this run does not establish its release-tag mapping.
- doi:10.1038/sdata.2016.110
Cited by
2 publicationsPublic catalog entries on Sciscape.
- usesThe seven delay differences above 50 ms have stored start differences below 20 ms in ds000030 1.0.0.
We used its constant NULL-onset finding to restrict adjacency to active GO and STOP rows. We used its 100 ms active-start limit for the primary strict A flag. We read this work before the new calculation.
- usesCovariance terms for initial delays have a negative sum in 241 ds000030 scanner records
Its distinction between constant NULL onset values and active-row order corrected this work's first timing notes. The new code measures the NULL values and active-row order directly.