The order in which the image intensities from the input image are written to stdout / text file should be predictable. A quick look at the code suggests that the image is being looped over with "default order". By default MRtrix behaviour that will be based on memory contiguity, ie. strides. I think this command should actually be looping over image axes strictly in sequential positive order.
The order in which the image intensities from the input image are written to stdout / text file should be predictable. A quick look at the code suggests that the image is being looped over with "default order". By default MRtrix behaviour that will be based on memory contiguity, ie. strides. I think this command should actually be looping over image axes strictly in sequential positive order.