The preprocessing of diffusion MRI (dMRI) involves numerous steps to clean and standardize the data before fitting a particular model. Generally, researchers create ad-hoc preprocessing workflows for each dataset, building upon a large inventory of available tools. The complexity of these workflows has snowballed with rapid advances in acquisition and processing. dMRIPrep is an analysis-agnostic tool that addresses the challenge of robust and reproducible preprocessing for whole-brain dMRI data. dMRIPrep automatically adapts a best-in-breed workflow to the idiosyncrasies of virtually any dataset, ensuring high-quality preprocessing without manual intervention. dMRIPrep equips neuroscientists with an easy-to-use and transparent preprocessing workflow, which can help ensure the validity of inference and the interpretability of results.
The workflow is based on Nipype and encompasses a large set of tools from other neuroimaging packages. This pipeline was designed to provide the best software implementation for each state of preprocessing, and will be updated as newer and better neuroimaging software becomes available.
dMRIPrep performs basic preprocessing steps such as head-motion correction, susceptibility-derived distortion correction, eddy current correction, etc. providing outputs that can be easily submitted to a variety of diffusion models.
We welcome all contributions! We'd like to ask you to familiarize yourself with our contributing guidelines. For ideas for contributing to dMRIPrep, please see the current list of issues. For making your contribution, we use the GitHub flow, which is nicely explained in the chapter Contributing to a Project in Pro Git by Scott Chacon and also in the Making a change section of our guidelines. If you're still not sure where to begin, feel free to pop into Mattermost and introduce yourself! Our project maintainers will do their best to answer any question or concerns and will be happy to help you find somewhere to get started.
We ask that all contributors to dMRIPrep across all project-related spaces (including but not limited to: GitHub, Mattermost, and project emails), adhere to our code of conduct.