FIX: Set input model to bedpostx for camino.TrackBedpostxProba

[mick-d]

Summary

Fix command line generated to run probability tracking on bedpostx output with Camino

List of changes proposed in this PR (pull-request)

Acknowledgment

• [x ] (Mandatory) I acknowledge that this contribution will be available under the Apache 2 license.

[codecov-io]

Codecov Report

Merging #2947 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2947      +/-   ##
==========================================
- Coverage   67.59%   67.59%   -0.01%     
==========================================
  Files         344      344              
  Lines       43747    43747              
  Branches     5456     5456              
==========================================
- Hits        29572    29570       -2     
+ Misses      13466    13461       -5     
- Partials      709      716       +7

Flag	Coverage Δ
#smoketests	50.37% <ø> (ø)	⬆️
#unittests	65.03% <100%> (-0.01%)	⬇️

Impacted Files	Coverage Δ
nipype/interfaces/camino/dti.py	77.91% <100%> (ø)	⬆️
nipype/pipeline/plugins/legacymultiproc.py	66.5% <0%> (-1%)	⬇️
nipype/interfaces/io.py	55.07% <0%> (ø)	⬆️
nipype/interfaces/freesurfer/preprocess.py	66.11% <0%> (ø)	⬆️
nipype/interfaces/dynamic_slicer.py	17.47% <0%> (ø)	⬆️
nipype/interfaces/nipy/preprocess.py	45.79% <0%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7fbc7cb...f473b39. Read the comment docs.

[effigies]

What changed in the last four years? Has this always been a bug, or has there been an update in the underlying tool, and this is moving to be consistent with the latest version?

[mick-d]

What changed in the last four years?

I used for the first time bedpostx + camino's probabilistic tractography for a project. Camino's code itself did not change in the last four years.

Has this always been a bug, or has there been an update in the underlying tool, and this is moving to be consistent with the latest version?

It has always been a bug (results were the same as deterministic tractography, and not much different from probabilistic tractography with a high connectivty threshold in terms of streamline count or the metric of interest). It is now consistent with the latest version of Camino (and Camino's version from 4 years ago).