Really…? What exactly did they mean by that? I’m pretty sure everything works better in MRtrix3, if there’s something that isn’t up to standard, please let us know so we can fix that - or more likely suggest a better way within MRtrix3.
Simply invoke the command with the -version
option:
$ mrconvert -version
== mrconvert 0.3.13-920-g45673184 ==
64 bit release version, built Apr 7 2016, using Eigen 3.2.8
...
And if you want a mixed workflow, I recommend you don’t add the MRtrix 0.2 folder to your PATH. That way you know that any command you invoke can only be the MRtrix3 version - unless you specifically asked for the MRtrix 0.2 version with something like this (assuming your MRtrix 0.2 installation is in ~/mrtrix2
:
$ mrconvert DICOM DWI.mif # <- invokes MRtrix3 version
$ ~/mrtrix2/bin/mrconvert DICOM/ DWI.mif # <- invokes MRtrix 0.2 version
If you’ve installed MRtrix 0.2 via e.g. NeuroDebian, and it’s therefore already in your default PATH, just make sure the MRtrix3 folder is listed first in your PATH - i.e. it would look something like:
$ echo $PATH
/home/jdt13/mrtrix3/release/bin:/home/jdt13/mrtrix3/scripts:/usr/local/sbin:/usr/local/bin:/usr/bin
This means if the command exists within MRtrix3, that version will be used. Those commands that only exist in MRtrix 0.2 will also be directly accessible. Any MRtrix 0.2 commands you want to invoke directly can be accessed using the same trick as above, but since they’ll now reside in /usr/bin
(most likely), you’d need to type:
$ /usr/bin/mrconvert ...
Again, you can always verify which version is actually invoked using the -version
option. Another command that comes in handy is which
: this tells you the exact location of the executable that would be invoked if you typed it, e.g.:
$ which mrconvert
/home/jdt13/mrtrix3/release/bin/mrconvert
This can be handy to figure out any issues with your PATH, etc.