Currently under development are two new MRtrix3 commands that will be utilised in the context of this tool.
peaksconvert: Converts between different formats used to encode one or more discrete fibre orientations per voxel.
Both input and output images could be represented using spherical coordinates (potentially mathematics or physics convention) or 3-vectors; and may or may not have additional amplitude information
Both input and output images could be defined using some reference coordinate set; this could be real / scanner space, image space, or the same convention as the bvecs format.
peakscheck: Performs a similar operation to the MRtrix3dwigradcheck command, except that instead of evaluating possible transformations / shuffling of the diffusion gradient table, it instead checks whether estimated fibre orientations may have been corrupted by some misinterpretation of orientation encoding.
I have a basic version working, which just does axis permutations and flips; I need to augment it to also consider different possible erroneous conversions from spherical to 3-vector encodings.
It may be some time before these commands get included in a tagged MRtrix3 release; so the tool container (#4) should clone and compile the specific feature branch necessary to access these tools.
Currently under development are two new MRtrix3 commands that will be utilised in the context of this tool.
peaksconvert
: Converts between different formats used to encode one or more discrete fibre orientations per voxel.bvecs
format.peakscheck
: Performs a similar operation to the MRtrix3dwigradcheck
command, except that instead of evaluating possible transformations / shuffling of the diffusion gradient table, it instead checks whether estimated fibre orientations may have been corrupted by some misinterpretation of orientation encoding.It may be some time before these commands get included in a tagged MRtrix3 release; so the tool container (#4) should clone and compile the specific feature branch necessary to access these tools.