Skip to content

DWI_Preprocessing

Alexandre Routier edited this page Jun 10, 2020 · 8 revisions

dwi-preprocessing-* – Preprocessing of raw diffusion weighted imaging (DWI) datasets

This pipeline corrects DWI datasets for motion, eddy current, magnetic susceptibility and bias field distortions, assuming that the data have been acquired using an EPI sequence.

The pipeline is mainly based on FSL [Jenkinson et al., 2012]. Head-motion and eddy current corrections are performed with the FSL eddy tool [Andersson et al., 2016a; Andersson et al., 2016b]. Depending on the data available (see below), the magnetic susceptibility correction can also be performed with the eddy tool or as a separate step. Finally, bias field correction is performed using the N4 algorithm [Tustison et al., 2010] implemented in ANTs.

!!! note "Notes regarding the fieldmaps for the magnetic susceptibility correction" Depending on the type of extra acquisition available (see details in the 'Fieldmap data' section of the BIDS specifications), different magnetic susceptibility corrections are performed. Two approaches are currently implemented in Clinica:

- No extra data: this is the case with the public [Alzheimer’s Disease Neuroimaging Initiative (ADNI)](http://adni.loni.usc.edu/) dataset for instance. The phase unwrapping is simulated thanks to a non-linear registration towards the T1-weighted image, which does not suffer from these artifacts.

- Phase difference image and at least one magnitude image (case 1 in the [BIDS specifications](https://bids-specification.readthedocs.io/en/stable/04-modality-specific-files/01-magnetic-resonance-imaging-data.html#phase-difference-image-and-at-least-one-magnitude-image)).

The cases 2, 3 and 4 of the [BIDS specifications](https://bids-specification.readthedocs.io/en/stable/04-modality-specific-files/01-magnetic-resonance-imaging-data.html#fieldmap-data) aka the “two phase images and two magnitude images”, the “single, real fieldmap image” (showing the field inhomogeneity in each voxel) and the “multiple phase encoded directions” (`topup`) approaches are not currently implemented in Clinica.

Dependencies

If you only installed the core of Clinica, the dwi-preprocessing-using-fmap pipeline (resp. dwi-preprocessing-using-t1) needs the installation of FSL, ANTs and MRtrix3 (resp. FSL, ANTs and Convert3D) on your computer. You can find how to install these software packages on the third-party page.

Running the pipeline

The pipeline can be run with the following command lines depending on the data you have:

clinica run dwi-preprocessing-using-t1 <bids_directory> <caps_directory>
clinica run dwi-preprocessing-using-fmap <bids_directory> <caps_directory>

where:

  • bids_directory is the input folder containing the dataset in a BIDS hierarchy;
  • caps_directory is the output folder containing the results in a CAPS hierarchy.

Please note that you will need the PhaseEncodingDirection and TotalReadoutTime metadata fields in the JSON file associated to your DWI images (see BIDS specifications for more details). For the dwi-preprocessing-using-fmappipeline, you will also need the EchoTime1 and EchoTime2 metadata fields in the JSON file associated to your fieldmap images (see BIDS specifications). Without these metadata fields, the pipelines will not run.

If you want to run the pipeline on a subset of your BIDS dataset, you can use the -tsv flag to specify in a TSV file the participants belonging to your subset.

!!! tip "Decreasing computation time" By default, the eddy tool of FSL uses OpenMP for parallel computing. CUDA can be used instead to speed up processing. To do so, you need to install CUDA 8.0 or CUDA 9.1 and add the flag --use_cuda_8_0 (resp. --use_cuda_9_1) to the Clinica command line. To check that CUDA has been installed properly, type the eddy_cuda8.0 or eddy_cuda9.1 command. If this message appears: $ eddy_cuda9.1 eddy_cuda9.1: error while loading shared libraries: libcudart.so.9.1: cannot open shared object file: No such file or directory it means that something went wrong during the installation or configuration of CUDA. Otherwise, you should see the help of the command and you can now use the --use_cuda_8_0/--use_cuda_9_1 flag!

!!! tip If your b0 images are not identical to 0 (e.g. 5 or 10, you can check this information by opening your *.bval file), you can use the --low_bval flag to consider these images as b0s.

!!! note Please note that the dwi-preprocessing-using-t1 pipeline will generate many temporary files. It can generate up to 20 GB of data for a dataset with 45 volumes. The size of the working directory is proportional to the number of directions available in the DWI dataset.

Outputs

Results are stored in the following folder of the CAPS hierarchy: subjects/sub-<participant_label>/ses-<session_label>/dwi/preprocessing.

The main output files are:

  • <source_file>_space-[T1w|b0]_preproc.[bval|bvec|nii.gz]: corrected DWI dataset where the first volume of the dataset is the reference b0.

  • <source_file>_brainmask.nii.gz: brain extracted image based on the reference b0.

!!! note If you ran the preprocessing pipeline using the T1-weighted image, your DWI dataset will be registered with the T1w image. Otherwise, your DWI dataset will be registered with the reference b0 image.

Describing this pipeline in your paper

??? cite "Example of paragraph for the dwi-preprocessing-using-t1 pipeline" These results have been obtained using the dwi-preprocessing-using-t1 pipeline of Clinica [Routier et al]. For each subject, all the b0 images were rigidly registered to the first b0 image and averaged to create the b0 reference. Then, the raw DWIs were corrected for eddy current induced distortions and subject movements by simultaneously modelling the effects of diffusion eddy currents and movements on the image. This step was performed using the FSL eddy tool [Andersson et al., 2016a] from FSL [Jenkinson et al., 2012] with the replace outliers (--repol) option [Andersson et al., 2016b]. To correct for susceptibility induced distortions, the T1w MRI was used as fieldmap data. The reference b0 image was first skull-stripped. To obtain the transformation flow from the native diffusion space to the T1w MRI space, the skull-stripped b0 image was registered to the T1w MRI in two steps: first a rigid registration using the FSL flirt tool and then a non-linear registration using the SyN algorithm implemented in ANTs [Avants et al., 2008]. SyN is an inverse-consistent registration algorithm allowing EPI induced susceptibility artifact correction [Leow et al., 2007]. The resulting transformation was applied to the DWIs to correct for the susceptibility induced distortions and the diffusion weighting directions were appropriately updated [Leemans & Jones, 2009]. Lastly, the DWI volumes were corrected for nonuniform intensity using the ANTs N4 bias field correction algorithm [Tustison et al., 2010]. A single multiplicative bias field from the reference b0 image was estimated, as suggested in [Jeurissen et al., 2014].

??? cite "Example of paragraph for the dwi-preprocessing-using-fmap pipeline" These results have been obtained using the dwi-preprocessing-using-fmap pipeline of Clinica [Routier et al]. For each subject, a brain mask was estimated from the DWI volumes [Dhollander et al., 2016] and a first run of the eddy tool [Andersson et al., 2016a] from FSL [Jenkinson et al., 2012] with the replace outliers (--repol) option [Andersson et al., 2016b] was used to align all the b0 images, average them, and create the reference b0 image. The fieldmap image was calibrated with the FSL fugue/prelude tools [Jenkinson, 2002] and registered to the reference b0 image. Head motion, eddy current and magnetic susceptibility distortions were simultaneously estimated and corrected using a second run of eddy with the calibrated fieldmap. Lastly, the DWI volumes were corrected for nonuniform intensity using the ANTs N4 bias field correction algorithm [Tustison et al., 2010]. A single multiplicative bias field from the corrected reference b0 image was estimated, as suggested in [Jeurissen et al., 2014].

!!! tip Easily access the papers cited on this page on Zotero.

Support