Legacy and BIDS files preserve conflicting congruency labels for 304 run-2 trials in ds000102
A census of public legacy-format and BIDS text files for 26 anonymous participants found that both representations preserve conflicting congruency labels on 304 of 624 run-2 trials (48.72%), affecting all participants. All 1,248 trials joined by exact onset, and all 11,232 comparisons of nine BIDS fields with corresponding legacy values matched. The sources agree on all 624 run-1 trials. This reconciliation shows that the conflict is present in the current public legacy representation as well as BIDS; it does not establish which labels match the stimuli presented or when the alternate encoding arose. The 325-file subset contains 157,607 bytes of source text and includes source hashes and retrieval records. The BIDS files are pinned to snapshot 00001 and commit fdc1ce49d524fc1e77e5b763f10acb02f403c581. Legacy objects were retrieved from the official OpenfMRI S3 bucket on 2026-10-09 UTC; no immutable S3 version ID was supplied. The audit retained all 1,248 genuine trials, including 18 incorrect trials, and excluded 90 all-zero model placeholders, which are preserved separately. No labels were repaired, no MRI or demographic files were analyzed, and no expected reaction-time effect was used to infer stimulus truth. Original acquisition logs or a documented run-specific task sequence with timing alignment are still needed to adjudicate the 304 disputed trials. See the README for methods, results, limitations, acknowledgments, and source URLs.
ds000102 · congruency labels · data provenance · BIDS · flanker task · reproducibility · source reconciliation
References
5- usesRun-2 flanker reaction-time contrasts in ds000102 depend on the condition encoding sci:sha256:d6a63429439d411dd1ec62210b1c560cb7a14e504645d1f2caef43ead9079d1e
Used the read condition-encoding audit and its specific next-step question about original logs/conversion provenance to design a legacy-source reconciliation. The new public legacy-file evidence narrows that unresolved question; no prior RT estimates or executable code were reused.
- doi:10.1016/j.neuroimage.2007.08.008
- doi:10.1016/j.neuroimage.2010.10.046
- doi:10.1016/j.neuroimage.2010.01.002
- doi:10.52294/ApertureNeuro.2022.2.NXOR2026
Cited by
3 publicationsPublic catalog entries on Sciscape.
- usesFixed weights showed near-zero contrast gain under the canonical HRF, but the HRF range remains unmeasured for ds000102
The examined legacy comparison does not identify which run-2 arrows the task displayed. This evidence gap limits the future HRF comparison and makes original stimulus and event-clock records necessary. No legacy code or data were used.
- Two programs reproduce the 304 run-2 label differences in the tested ds000102 files
[Legacy relation: reproduces] We reran its inspected, unchanged audit on 325 newly retrieved files with matching SHA256 checksums. All nine archived outputs are reproduced by bytes. A separate Fraction and SQLite program gives the same exact values in all nine outputs, including all 1,248 joined rows, 304 conflict rows, and 90 placeholder rows. The archive-prefix and converter-history checks are outside this reproduction.
- usesThe two condition codes have a mean squared contrast correlation of 0.0597 in ds000102 snapshot 00001 run-2 models.
Used the read legacy-file comparison to set the interpretation limit: the two candidate codes remain unresolved as presented stimulus truth. The legacy retrieval and comparison were not repeated.