# Preprocessing Steps
**URL:** https://community.mrtrix.org/t/preprocessing-steps/2385
**Category:** Uncategorized
**Created:** [March 21, 2019, 3:49pm UTC](https://community.mrtrix.org/t/preprocessing-steps/2385 "2019-03-21T15:49:51Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@hastotes](https://community.mrtrix.org/u/hastotes)
#### Post date: [March 21, 2019, 3:49pm UTC](https://community.mrtrix.org/t/preprocessing-steps/2385/1 "2019-03-21T15:49:51Z")
Hi,
I am just updating our diffusion processing pipeline to include the dwidenoise and mrdegibbs steps. Our raw data is organised in two DICOM directories, one containing the main diffusion-weighted data, and one containing reversed phase-encode data. I am wondering whether I am ok to perform the dwidenoise and mrdegibbs steps only on the main diffusion volume only? Or should I also run the steps on the reversed phase-encode series?
Many thanks,
Hanne Stotesbury
---
### Author:  [@mblesac](https://community.mrtrix.org/u/mblesac)
#### Post date: [March 21, 2019, 4:39pm UTC](https://community.mrtrix.org/t/preprocessing-steps/2385/2 "2019-03-21T16:39:24Z")
Hi,
My data is in a similar format as yours, and the first thing I always do is to create the file with 2 B0s, one in each phase encoding direction, to use it in dwipreproc (topup), then I apply dwidenoise and mrdegibbs to the actual data. But you could also concatenate everything at the beginning and run dwidenoise and mrdegibbs all together, and then split it again. Both approaches seem reasonable to me. I hope this helps.
Best regards,
Manuel
---
### Author:  [@hastotes](https://community.mrtrix.org/u/hastotes)
#### Post date: [March 22, 2019, 11:52am UTC](https://community.mrtrix.org/t/preprocessing-steps/2385/3 "2019-03-22T11:52:34Z")
Thanks for the swift reply @mblesac. That’s really helpful. I will try the latter approach.
Hanne 🙂
---
### Author:  [@hastotes](https://community.mrtrix.org/u/hastotes)
#### Post date: [March 26, 2019, 6:31pm UTC](https://community.mrtrix.org/t/preprocessing-steps/2385/4 "2019-03-26T18:31:12Z")
Just to follow up on this, I’ve run the preprocessing steps (dwidenoise & mrdegibbs) on;
- the concatenated data, including b0s in both phase-encoded directions
- the main data, including b0s in the phase-encoded direction only
The residuals look better when the steps are run on the main data only. I’ve seen other threads where concatenating is advised e.g. [here](https://community.mrtrix.org/t/preprocessing-questions/995/2)
I’m struggling to see why though. Would the distortions not be in the opposite directions and could this not result in anatomical details being mapped differently?
Hanne
---
### Author:  [@rsmith](https://community.mrtrix.org/u/rsmith)
#### Post date: [April 6, 2019, 4:48pm UTC](https://community.mrtrix.org/t/preprocessing-steps/2385/5 "2019-04-06T16:48:39Z")
My personal intuition with regards to use of concatenated data with different phase encoding directions for `dwidenoise` is that as long as the absolute noise level does not differ “substantially” between _the anatomical locations from which the image intensities in a particular voxel originated_, then the mechanism should work fine.
However I’m reconsidering the point now having been going through the process of determining new DWI protocols: with the gravitation toward high MB factors and disabling of in-plane acceleration, the resulting more severe distortions may bring this into question.
Certainly if you have empirical observations from your own data that the concatenation approach may be somehow problematic, I’d be curious to see it.