# Default algorithm for dwi2response in 0.3.12?

**URL:** <https://community.mrtrix.org/t/default-algorithm-for-dwi2response-in-0-3-12/2855>\
**Category:** Uncategorized\
**Created:** [September 26, 2019, 9:37pm UTC](https://community.mrtrix.org/t/default-algorithm-for-dwi2response-in-0-3-12/2855 "2019-09-26T21:37:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kjamison](https://community.mrtrix.org/letter_avatar_proxy/v4/letter/k/848f3c/32.png) [@kjamison](https://community.mrtrix.org/u/kjamison)\
**Post date:** [September 26, 2019, 9:37pm UTC](https://community.mrtrix.org/t/default-algorithm-for-dwi2response-in-0-3-12/2855/1 "2019-09-26T21:37:54Z")

</div>

I’m trying to process some data to match an older dataset we have that was generated using 0.3.12. In that original pipeline, the dwi2response command was:

`dwi2response ${diffdir}/data.nii.gz ./CSD10_b3000_response.txt -lmax 10 -fslgrad ${diffdir}/bvecs ${diffdir}/bvals -mask ./eromask.nii.gz -sf ./sf_mask.nii.gz -nthreads 8`

When I try to run this on the latest mrtrix, I need to specify an algorithm, and I can’t figure out which algorithm is equivalent to whatever was used in that older version. There doesn’t appear to be documentation up for that version either. I don’t see the `-sf` flag in any of the new docs. Is that equivalent to `-voxels` now?

---

<div class="post-metadata">

**Author:** ![jdtournier](https://community.mrtrix.org/user_avatar/community.mrtrix.org/jdtournier/32/2594_2.png) [@jdtournier](https://community.mrtrix.org/u/jdtournier)\
**Post date:** [September 27, 2019, 10:56am UTC](https://community.mrtrix.org/t/default-algorithm-for-dwi2response-in-0-3-12/2855/2 "2019-09-27T10:56:12Z")

</div>

That would have used the `tax` algorithm – as originally proposed in [this paper](https://www.ncbi.nlm.nih.gov/pubmed/23927905). It’s [still available](https://mrtrix.readthedocs.io/en/3.0_rc3/reference/scripts/dwi2response.html#dwi2response-tax) in more recent versions of _MRtrix3_, but there are differences in the implementation so the output is unlikely to be exactly identical – so I definitely wouldn’t combine data analysed with 0.3.12 and more recent versions in the same analysis.

We decided to move away from that approach to the [`dwi2reponse tournier`](https://mrtrix.readthedocs.io/en/3.0_rc3/reference/scripts/dwi2response.html#dwi2response-tournier) algorithm after [quite a bit of discussion](https://github.com/MRtrix3/mrtrix3/issues/422). Nowadays the recommended approach is the [`dwi2response dhollander`](https://mrtrix.readthedocs.io/en/3.0_rc3/reference/scripts/dwi2response.html#dwi2response-dhollander) algorithm, which seems to perform well both single and multi-shell data.

---

<div class="post-metadata">

**Author:** ![rsmith](https://community.mrtrix.org/user_avatar/community.mrtrix.org/rsmith/32/2672_2.png) [@rsmith](https://community.mrtrix.org/u/rsmith)\
**Post date:** [October 7, 2019, 11:51am UTC](https://community.mrtrix.org/t/default-algorithm-for-dwi2response-in-0-3-12/2855/3 "2019-10-07T11:51:13Z")

</div>

> There doesn’t appear to be documentation up for that version either. I don’t see the `-sf` flag in any of the new docs. Is that equivalent to `-voxels` now?

Correct. The interface is different in part because the implementation has been re-done from scratch: back in `0.3.12`, `dwi2response` was a C++ binary command, whereas now the `dwi2response` wrapper and all of the individual algorithms are written in Python.
