I've been wrapping mri_convert for use with some of my lab's scripts.
I appreciate the work that's been done with this utility and its
flexibility in regard to wide support for many formats...the main
incentive for moving over to it.
However, recently I've been getting reports of my conversions not
behaving well with fsl. I've read the freesurfer archives and am sure
the issue is not with mri_convert itself, but with the way I'm using it.
I'll use dcm2nii as a comparison as another lab is using this utility
are reports everything appears to work fine.
Example mri_convert:
$ mri_convert mprage.dcm mprage.nii.gz
This command very faithfully converts the dicom to nifti. Inspecting
the headers shows that nothing is changed whatsoever.
$ dcm2nii mprage.dcm
This command changes the Patient Orientation header field. In the case
of a MPRAGE scan, it is changed from an orientation of PIL (posterior,
inferior, left) to PAL. These PAL oriented images are said to be the
ones desired.
I can replicate this by using:
$ mri_convert --out_orientation PAL mprage.dcm mprage.nii.gz
Of course, the flip made by dcm2nii for different scan types are
themselves different.
The dcm2nii script performs patient orientation changes on all of the
scan types I've checked so far (3-5 or so). What I am somewhat
perplexed over (and what no one in my lab has been able to answer) is
by what "rule" and why are these conversions made? If I knew this, I
could ensure mri_convert did them when appropriate.
Would this be the "flipping" from radiological to neurological? Or is
this a question I should be posing to the FSL team on the requirements
of their images?
Many thanks for any input, and thank you for patience with my newness
to this area.
Cheers,
James A. Kyle
_______________________________________________
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
