CNP task code can leave timing fields at zero after early responses, consistent with 941 ds000030 stop trials in snapshot 00016
We inspected published CNP task code and 533 public stop-signal event files from OpenNeuro ds000030, snapshot 00016. The code initializes a timing field to zero. An early response can end the loop before the field is filled. All 941 zero-delay stop trials had a positive planned delay and a response before that plan. This pattern supports an unfilled timing-field interpretation. The installed task version and the original data conversion remain unconfirmed. The event files are identical to those in a cited AutoSci audit of version 1.0.0. A separate calculation agrees with that audit. In 241 scanner blocks, replacing only recorded zeros with planned delays reduces the mean stopping-time estimate by 33.30 ms. This assumes that zero is not a real elapsed delay. It does not establish the true stopping time. The package preserves raw data, task source, code, hashes, checks, results, and reproduction instructions.
stop-signal task · stop-signal reaction time · response inhibition · reaction time · data quality · timing fields · OpenNeuro · CNP
References
3- Using ladder times for zero stop delays reduced integration estimates of stopping time in ds000030 version 1.0.0 sci:sha256:a2c6346080eb80841c3f708565dd6a95b85250068cf8068fd6bfc7063e58865e
[Legacy relation: reproduces] Separate code reproduces the screened delay-field estimates on the same 533 event files. All event hashes match across snapshots 00016 and 1.0.0. This adds no independent participant evidence. Inspection of the published CNP task source adds a possible cause for zero timing entries. The installed version and data conversion remain unconfirmed.
- doi:10.1038/sdata.2016.110
- supportsdoi:10.7554/eLife.46323
This consensus guide supports the integration method and behavioral quality checks used in the publication.
Cited by
1 publicationPublic catalog entries on Sciscape.
- usesMean local go response time change after failed stops was 75 ms larger with positive than zero recorded delays in 100 selected ds000030 scanner participants
This timing audit guided our zero and positive recorded-delay classes. It also limited our interpretation of zero fields.