OSCR

Orchestrating neuroimaging data processing using the 'Snakemake' workflow manager.

Code ↔ Paper

The paper beside its authors' code: matches between them have not been computed for this paper yet.

Paper

Loaded from Europe PMC by your browser; OSCR does not store it: doi.org · Europe PMC

The paper is loaded when this pane is shown.

The authors' code

Shell · 43 lines · 982 B · MIT

  1. #!/bin/sh
  2. set -eu
  3. method="$1"
  4. script_name="$2"
  5. cp -r /app/* /work
  6. cp -r /snakebids /src
  7. script="'${script_name}' tests/data tests/result participant -c1 --skip-bids-validation"
  8. case "$method" in
  9. "setuptools" )
  10. python -m venv .venv
  11. .venv/bin/python -m pip install --no-color .
  12. PATH=".venv/bin:$PATH" eval "$script"
  13. ;;
  14. "poetry" )
  15. poetry install --no-ansi
  16. eval "poetry run $script"
  17. ;;
  18. "uv" )
  19. uv pip install --system .
  20. eval "uv run $script"
  21. ;;
  22. "hatch" )
  23. hatch env create
  24. eval "hatch env run -- $script"
  25. ;;
  26. "pdm" )
  27. pdm install
  28. eval "pdm run $script"
  29. ;;
  30. "docs" )
  31. python -m venv .venv
  32. .venv/bin/python -m pip install .
  33. .venv/bin/python -m pip install -r docs/requirements.txt
  34. .venv/bin/sphinx-build docs build/docs -W
  35. ;;
  36. * )
  37. >&2 echo "Invalid method"
  38. exit 1
  39. ;;
  40. esac

test-template.sh at commit 1d97fee, under MIT · at the source

Overview

  1. Melbourne Data Analytics Platform (MDAP), The University of Melbourne, Parkville, Australia
  2. Melbourne School of Psychological Sciences, The University of Melbourne, Parkville, Australia
  3. Graeme Clark Institute for Biomedical Engineering, The University of Melbourne, Parkville, Australia
Institutions: The University of Melbourne (Australia)
Journal: Brain structure & function, volume 231, issue 8, article 131
Dates: received 13 May 2026; accepted 20 August 2026; published online 4 September 2026; in print 2026
Type: Research article · Language: English
License: CC BY
Identifiers: DOI 10.1007/s00429-026-03189-3 · PMID 42696207 · PMCID PMC13545037 · OpenAlex W7128988335
Open access: hybrid, a free copy (OpenAlex)
Status: code verified (how the code is found and verified)
Categories: human (organism), methods / tools (subfield)
Methods: Connectivity, fMRI & imaging
Keywords: Workflow, Data processing, Data analysis, Infrastructure, Computing
MeSH: Image Processing, Computer-Assisted*, Neuroimaging*, Software*, Workflow*, Humans (* major topic)
Topic: Scientific Computing and Data Management (Information Systems and Management, Decision Sciences), according to OpenAlex
Funding: University of Melbourne
Citations: not cited yet (Europe PMC); 25 references in the paper

Abstract

The processing of neuroimaging data typically involves a complicated set of operations, which often require different software packages and have intensive computational and storage demands. Although there are many options available for the neuroimaging researcher to establish their preferred set of processing operations, there is relatively little guidance on how to orchestrate such operations within a coherent data processing workflow. Here, by describing the construction of a simplified neuroimaging processing workflow, we demonstrate how the established general-purpose workflow manager ‘Snakemake’ can be used to facilitate neuroimaging data processing. Snakemake allows researchers to use a Python-based markup language to describe how input files are transformed into output files. Snakemake then uses these rules to schedule and execute the computational jobs that are required to generate the output files, without unnecessary recreation of existing output files. This allows the complete processing workflow to be executed with a single command and creates workflows that are interpretable, efficient, and reproducible.

Reproduced under the paper's license (CC BY), from the paper cited above.

Repositories

Its files are read in the Code ↔ Paper reader above.

unimelbmdap/neuroimaging_containers

License: none: the authors keep all their rights
State: the link answers, verified on 26 September 2026
Evidence: files inventoried
Commit: 99380e076a3d62ce7025f8770f2cf9d7880f114e, 12 February 2026
Size: 23 files, 0 scripts
Software Heritage: not checked
Found in: the text, “Footnotes”
Holds: README, environment (definitions/afni.def, definitions/ants.def, definitions/bids_validator.def, definitions/bidsphysio.def, definitions/dcm2niix.def, definitions/deepret.def, definitions/fsl.def, definitions/fsl5.def, definitions/laynii.def, definitions/matlab.def, definitions/mb.def, definitions/neuropythy.def)
Not found: license file, CITATION.cff, tests, continuous integration, documentation
Availability: 1 check, the latest on 26 September 2026: the link answers
  • 26 September 2026: the link answers
1 file

khanlab/snakebids

License: MIT
State: the link answers, verified on 26 September 2026
Evidence: files inventoried
Commit: 1d97feeb39fde9e47b4a403c8f277bd0e8781eef, 13 March 2026
Languages: Python (93), Shell (1)
Size: 277 files, 94 scripts
Software Heritage: archived
Found in: the text, “Footnotes”
Holds: README, license file, environment (pyproject.toml, uv.lock, containers/test-template/Dockerfile), tests, continuous integration, documentation
Not found: CITATION.cff
Tools: PyBIDS (7 files), BIDS Validator (1 file), Snakemake (1 file)
Availability: 1 check, the latest on 26 September 2026: the link answers
  • 26 September 2026: the link answers
96 files

The paper's code and data availability statement is in the Data section.

Tracing map

Proposed by the machine: these links were found in the paper and verified at the source, without human review. The map will receive a Zenodo DOI once one of the paper's authors has validated it with their ORCID.

What the map holds:

  • 2 repositories of the authors' code, each at its verified commit, with its license and how the link was found in the paper;
  • 94 scripts, each with its path and the digest of its content;
  • no match between paragraphs and code yet;
  • neither the text of the paper nor the code itself.

Its JSON (tracing-map.json) is deposited on Zenodo with its DOI once the map is validated.

Data

Datasets cited

Data availability

The example workflow is available at https://github.com/unimelbmdap/snakemake_paper_demo_workflow. The raw data that is used in the workflow can be obtained via the workflow available at https://github.com/unimelbmdap/snakemake_paper_demo_workflow_data.

Reproduced under the paper's license (CC BY), from the paper cited above.

Versions

The history of this record: each version stored by the harvester or made by a correction of its authors or of the maintainers of its code, and what changed in its facts. The texts of the paper (its abstract, its availability statements) are not part of it; versions that changed only those are not listed.

Version 3, 28 September 2026

  • Publisher: n/a → Springer Science+Business Media

Version 1, 27 September 2026: the first record

Recorded: type, language, journal, volume, issue, pages, dates, 4 authors, 5 keywords, 5 MeSH terms, 1 funder, 21 references.

Cite

This paper

Mannion, D. J., Quiroga, M. d. M., Paul, J. M., & Garrido, M. I. (2026). Orchestrating neuroimaging data processing using the 'Snakemake' workflow manager. Brain structure & function, 231(8), 131. https://doi.org/10.1007/s00429-026-03189-3

BibTeX

@article{mannion2026orchestrating,
author = {Mannion, Damien J and Quiroga, Maria del Mar and Paul, Jacob M and Garrido, Marta I},
title = {{Orchestrating neuroimaging data processing using the 'Snakemake' workflow manager}},
journal = {Brain structure \& function},
year = {2026},
month = sep,
volume = {231},
number = {8},
pages = {131},
publisher = {Springer Science+Business Media},
issn = {1863-2653},
doi = {10.1007/s00429-026-03189-3},
url = {https://doi.org/10.1007/s00429-026-03189-3},
pmid = {42696207},
pmcid = {PMC13545037}
}

RIS

TY - JOUR
AU - Mannion, Damien J
AU - Quiroga, Maria del Mar
AU - Paul, Jacob M
AU - Garrido, Marta I
TI - Orchestrating neuroimaging data processing using the 'Snakemake' workflow manager
T2 - Brain structure & function
J2 - Brain Struct Funct
PY - 2026
DA - 2026/09/04
VL - 231
IS - 8
SP - 131
SN - 1863-2653
PB - Springer Science+Business Media
DO - 10.1007/s00429-026-03189-3
UR - https://doi.org/10.1007/s00429-026-03189-3
LA - en
ER -

CSL-JSON

{
"id": "10.1007/s00429-026-03189-3",
"type": "article-journal",
"title": "Orchestrating neuroimaging data processing using the 'Snakemake' workflow manager",
"container-title": "Brain structure & function",
"author": [
{
"family": "Mannion",
"given": "Damien J"
},
{
"family": "Quiroga",
"given": "Maria del Mar"
},
{
"family": "Paul",
"given": "Jacob M"
},
{
"family": "Garrido",
"given": "Marta I"
}
],
"container-title-short": "Brain Struct Funct",
"volume": "231",
"issue": "8",
"page": "131",
"DOI": "10.1007/s00429-026-03189-3",
"PMID": "42696207",
"PMCID": "PMC13545037",
"ISSN": "1863-2653",
"publisher": "Springer Science+Business Media",
"URL": "https://doi.org/10.1007/s00429-026-03189-3",
"language": "en",
"issued": {
"date-parts": [
[
2026,
9,
4
]
]
}
}

The tracing map gets a citation of its own once an author has validated it and it has a DOI.

Similar papers

The papers with a page that share the most with this one: the tools found in their code, their categories, datasets, cited references and authors, the rarest counting most.

[1] doi:10.1093/scan/nsag053
Safety-relevant experience reshapes neural codes for ambiguous threat in adolescents.
Journal: Social cognitive and affective neuroscience
In common: 1 reference, 2 authors
[2] doi:10.1016/j.neuroimage.2022.119623 [code]
Open and reproducible neuroimaging: From study inception to publication.
Journal: NeuroImage
In common: BIDS Validator, PyBIDS, 5 references
[3] doi:10.7554/elife.79277 [code]
Neuroscout, a unified platform for generalizable and reproducible fMRI research.
Journal: eLife
In common: BIDS Validator, PyBIDS, methods / tools, 3 references
[4] doi:10.1093/schizbullopen/sgae010 [code]
Cortical Network Disruption Is Minimal in Early Stages of Psychosis.
Journal: Schizophrenia bulletin open
In common: BIDS Validator, Snakemake, PyBIDS, 1 reference
[5] doi:10.1162/imag.a.79 [code]
Open-source platforms to investigate analytical flexibility in neuroimaging.
Journal: Imaging neuroscience (Cambridge, Mass.)
In common: PyBIDS, methods / tools, 5 references
[6] doi:10.1002/hbm.25829 [code]
ENIGMA HALFpipe: Interactive, reproducible, and efficient analysis for resting-state and task-based fMRI data.
Journal: Human brain mapping
In common: PyBIDS, methods / tools, 5 references
[7] doi:10.1162/netn_a_00322 [code]
A pattern of cognitive resource disruptions in childhood psychopathology.
Journal: Network neuroscience (Cambridge, Mass.)
In common: BIDS Validator, PyBIDS, 3 references
[8] doi:10.1038/s41467-024-50826-8 [code]
A standardized image processing and data quality platform for rodent fMRI.
Journal: Nature communications
In common: PyBIDS, methods / tools, 5 references
[9] doi:10.1162/imag.a.1274 [code]
QuNex recipes: Executable, human-readable workflows for reproducible neuroimaging research.
Journal: Imaging neuroscience (Cambridge, Mass.)
In common: methods / tools, 6 references
[10] doi:10.7554/elife.71774 [code]
The OpenNeuro resource for sharing of neuroscience data.
Journal: eLife
In common: PyBIDS, methods / tools, 4 references

Contribute

The authors of this paper can claim it, correct its record and validate its tracing map, and the maintainers of its code (its owner, or a public member of its organization) correct what it says of their repository; anyone signed in can ask for its removal. Every request goes to OSCR's own machine, which answers it; your account page follows them.

Sign in with ORCID to claim this paper as one of its authors, correct its record or validate its tracing map: when the paper's metadata lists your ORCID iD, you are recognized at once. Maintainers of its code: sign in with GitHub, then claim the repository on your account page.

Add the badge to the code's README

OSCR: the badge of this paper

If you are an author or a maintainer of this paper's code, you can add this badge. It says what OSCR knows of the paper (its code, its validated tracing map) and links the code to this page. Paste one of these snippets under the README's title. Keep the two marks around it, so that the badge can be replaced in place and is never added twice. OSCR changes nothing in your repository.

Markdown
<!-- oscr-badge:start -->
[![OSCR](https://openscicode.org/badge/doi/10.1007/s00429-026-03189-3.svg)](https://openscicode.org/badge/doi/10.1007/s00429-026-03189-3)
<!-- oscr-badge:end -->
reStructuredText
.. oscr-badge:start

.. image:: https://openscicode.org/badge/doi/10.1007/s00429-026-03189-3.svg
   :target: https://openscicode.org/badge/doi/10.1007/s00429-026-03189-3
   :alt: OSCR

.. oscr-badge:end
HTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1007/s00429-026-03189-3"><img src="https://openscicode.org/badge/doi/10.1007/s00429-026-03189-3.svg" alt="OSCR"></a>
<!-- oscr-badge:end -->

On GitHub, open the README, choose Edit (the pencil), paste the snippet under the title, then "Commit changes".

If you choose to, you can have the badge kept up to date for you, with oscr badge --write from the command line or with the GitHub Action in your repository's workflows. Every other form and option (a card, AsciiDoc, LaTeX, shields.io) is on the badge page.

Request its removal

To ask OSCR to remove this record, the copies of its authors' scripts or its tracing map, use the removal request page: signed in, you say who you are, what to remove and why, then review and confirm the request. Published rules decide every request (how).

Discussion, reproductions, activity

Discussion: code errors and mismatches between the code and the paper about this paper and its code, from readers and its authors, beside the paper and its tracing map.

Report a mismatch between the code and the paper · Report a code error (signed in)

Reproductions: reports from readers who ran the authors' code and did not get the paper's result, what they ran, with which environment, commit and data.

Report a reproduction failure (signed in)

Versions of its code: the releases of its code tied to a version of this paper (the preprint, the accepted manuscript, the version of record…), each with the tracing map versioned with it.

Activity: what happens around this paper: new versions of its record, its map's validation, discussions and reproductions. It opens with sign-in.