As shown in MRtrix3/mrtrix3#3275, labels that commence with a numeric character can cause problems in certain contexts. There the interface of the MRtrix3 command peaksconvert, which is intended to facilitate conversions between the various orientation encodings in BEP016, had its command-line interface altered to use "cartesian" in place of "3vector". Could consider a similar change here.
It's maybe more ambiguous in this context however. For peaksconvert, it is implicit within the context of the data on which the command operates ("peaks") that the encoding of fixel orientations is in either spherical or cartesian coordinates. Whereas here, there are other orientation encodings---eg. tensor, SH, amplitudes---that are arguably also "cartesian".
As shown in MRtrix3/mrtrix3#3275, labels that commence with a numeric character can cause problems in certain contexts. There the interface of the MRtrix3 command
peaksconvert, which is intended to facilitate conversions between the various orientation encodings in BEP016, had its command-line interface altered to use "cartesian" in place of "3vector". Could consider a similar change here.It's maybe more ambiguous in this context however. For
peaksconvert, it is implicit within the context of the data on which the command operates ("peaks") that the encoding of fixel orientations is in either spherical or cartesian coordinates. Whereas here, there are other orientation encodings---eg. tensor, SH, amplitudes---that are arguably also "cartesian".