zeigar / smriprep

Structural MRI PREProcessing (sMRIPrep) workflows for NIPreps (NeuroImaging PREProcessing tools)

sMRIPrep: Structural MRI PREProcessing pipeline

sMRIPrep is a structural magnetic resonance imaging (sMRI) data preprocessing pipeline that is designed to provide an easily accessible, state-of-the-art interface that is robust to variations in scan acquisition protocols and that requires minimal user input, while providing easily interpretable and comprehensive error and output reporting. It performs basic processing steps (subject-wise averaging, B1 field correction, spatial normalization, segmentation, skullstripping etc.) providing outputs that can be easily connected to subsequent tools such as fMRIPrep or dMRIPrep.

The workflow is based on Nipype and encompases a combination of tools from well-known software packages, including FSL, ANTs, FreeSurfer, and AFNI.

More information and documentation can be found at https://poldracklab.github.io/smriprep/. Support is provided on neurostars.org.

Principles

sMRIPrep is built around three principles:

1. Robustness - The pipeline adapts the preprocessing steps depending on the input dataset and should provide results as good as possible independently of scanner make, scanning parameters or presence of additional correction scans (such as fieldmaps).
2. Ease of use - Thanks to dependence on the BIDS standard, manual parameter input is reduced to a minimum, allowing the pipeline to run in an automatic fashion.
3. "Glass box" philosophy - Automation should not mean that one should not visually inspect the results or understand the methods. Thus, sMRIPrep provides visual reports for each subject, detailing the accuracy of the most important processing steps. This, combined with the documentation, can help researchers to understand the process and decide which subjects should be kept for the group level analysis.

Acknowledgements

Please acknowledge this work by mentioning explicitly the name of this software (sMRIPrep) and the version, along with a link to the GitHub repository or the Zenodo reference (doi:10.5281/zenodo.2650521).