# Eddy's estimate move by susceptibility option causing crash on denoised data?

**URL:** <https://community.mrtrix.org/t/eddys-estimate-move-by-susceptibility-option-causing-crash-on-denoised-data/2754>\
**Category:** Uncategorized\
**Tags:** preprocessing\
**Created:** [August 15, 2019, 5:58pm UTC](https://community.mrtrix.org/t/eddys-estimate-move-by-susceptibility-option-causing-crash-on-denoised-data/2754 "2019-08-15T17:58:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![maxpietsch](https://community.mrtrix.org/user_avatar/community.mrtrix.org/maxpietsch/32/25_2.png) [@maxpietsch](https://community.mrtrix.org/u/maxpietsch)\
**Post date:** [August 15, 2019, 7:14pm UTC](https://community.mrtrix.org/t/eddys-estimate-move-by-susceptibility-option-causing-crash-on-denoised-data/2754/2 "2019-08-15T19:14:27Z")

</div>

Hi Mark,

Congratulations, your data might be too clean to be processed by eddy 🎆 Eddy’s Gaussian process expects some degree of noise in the data and if denoising works well, eddy might not – [(discussion here)](https://community.mrtrix.org/t/dwidenoise-with-dwipreproc/2358/4). As far as I can tell, the error message and dependency on `estimate_move_by_susceptibility` are different from those reported so far though so there might be a problem with the denoised data or `dwipreproc`.

Might be worth going into the temporary directories created by `dwipreproc -nocleanup` and checking the input data to eddy and the exact commands. In particular, are there any differences in image dimensions and voxel sizes (`mrinfo`)? You could also try to verify if eddy works on denoised data to which you added some Gaussian noise (`mrcalc denoised.mif randn $(mrmath 1.mif max -axis 3 - | mrstats - -output mean) -mult 0.5 -mult -add - | mrview - denoised.mif` or similar).

---

_[View the full topic](https://community.mrtrix.org/t/eddys-estimate-move-by-susceptibility-option-causing-crash-on-denoised-data/2754)._