There is a newer version of the record available.

Published September 18, 2026 | Version v1

STAMPED in Practice: Reproducing a Scientific Result Using ABCD Neuroimaging Data

Description

Research software engineers routinely encounter computational analyses whose code is available but whose data, parameters, software environments, execution context, and provenance are difficult to reconstruct. This missing context makes analyses harder to review, maintain, transfer, and extend. AI-assisted tools can accelerate development, testing, and documentation, but their high output volume and nondeterministic behavior further complicate these tasks and heighten the need for explicit context and reviewable intermediate states. STAMPED (https://stamped-principles.org) defines seven properties for organizing these materials as a durable and more useful research object [1]. The framework complements the established FAIR (Findable, Accessible, Interoperable, and Reusable) principles by focusing on the organization and execution of computational research objects [7].

This poster presents our application of STAMPED to an existing analysis presented at OHBM 2025 on age-dependent bias in cortical morphometry tools using Adolescent Brain Cognitive Development (ABCD) Studydata [3]. We apply STAMPED, developed in our prior work [1] and introduced in a companion poster, to guide improvements to the research object surrounding the analysis [2]. We use AI extensively in development, testing, and documentation, making the reconstruction a practical test of the STAMPED vision for AI-assisted research.

Following a review of the original analysis, we use a coordinated set of tools to improve the research object across the seven properties:

Property Implementation and tools
Self-containment Explicit research-object boundaries using DataLadand git-annex [4]
Tracking Versioned state and provenance using Git, DataLad run records, con-duct, NIDM, and PROV [4,6]
Actionability Executable interfaces using tested BIDS Apps and Pixi tasks [5]
Modularity Independently versioned components composed using DataLad [4]
Portability Explicit execution environments using Apptainercontainers [5]
Ephemerality Fresh execution using Apptainer, BABS, and Slurm[5]
Distributability Persistent git-annex remotes with separate access boundaries [4]

We show how these tools work in concert to make the data, environments, operations, and results more FAIR and STAMPED. ABCD access restrictions introduce a practical tension between distributability and controlled access that we examine in applying the principles.

Collectively, the decisions on how to implement the principles provide a worked example of how to use STAMPED to guide choices about research-object boundaries, provenance, execution, validation, and distribution. We report the practical details of this process: the effort and judgment required, problems encountered, tradeoffs made, evidence produced, interactions among principles and tools, and cases where satisfying one property complicates another. Although we demonstrate the approach through a scientific reproduction, it is easier and more scientifically valuable when integrated from the start of the analysis [8]. The poster invites RSEs to consider which parts apply to their own shared or domain-specific challenges.

Files

stamped-abcd-poster-for-zenodo.pdf

Files (59.5 kB)

Name Size
md5:ab9ec02538e0595f8d9fa53c03d2c1c6
25.2 kB Download
md5:39976b86b6b0c3258376a59975d13ece
34.3 kB Preview Download

Additional details

Funding

National Institutes of Health
ReproNim: A Center for Reproducible Neuroimaging Computation 5P41EB019936-09

Software