questions > EPI y-flipped during conversion
Showing 1-3 of 3 posts
Jun 27, 2018 10:06 AM | Richard Binney - Bangor University
EPI y-flipped during conversion
Dear colleagues,
I'm using the very latest release of dcm2niix.
I have found it works well with my Phillips system (old Gen Achieva, June18 software upgrade).
For one dual-echo EPI sequence the software flipped just one the time series of only one of the echoes of only one of 5 EPI acquisitions. It did so in the y-plane.
Rerunning the conversion with SPM12's DICOM import threw out the usual errors I see but handled the orientation fine.
Has anyone anyu similar experience and/or any explanations?
Much obliged
Richard
I'm using the very latest release of dcm2niix.
I have found it works well with my Phillips system (old Gen Achieva, June18 software upgrade).
For one dual-echo EPI sequence the software flipped just one the time series of only one of the echoes of only one of 5 EPI acquisitions. It did so in the y-plane.
Rerunning the conversion with SPM12's DICOM import threw out the usual errors I see but handled the orientation fine.
Has anyone anyu similar experience and/or any explanations?
Much obliged
Richard
Jul 19, 2018 01:07 PM | Chris Rorden
RE: EPI y-flipped during conversion
Can you confirm you are using the current v1.0.20180622. Philips has been moving to enhanced DICOM, so you will need to
update your conversion software to be aware of this new format. If
the problem persists with the latest version, post a new issue on
the dcm2niix github issues page.
Jul 23, 2018 11:07 AM | Richard Binney - Bangor University
RE: EPI y-flipped during conversion
Hi everybody,
My issue was resolved by upgrading the version of DCM2niiX.exe that I was using. I suggest that if you detect an error in the conversion, your first attempt at a solution should be to upgrade to the very latest release.
Happy Scanning!
R
My issue was resolved by upgrading the version of DCM2niiX.exe that I was using. I suggest that if you detect an error in the conversion, your first attempt at a solution should be to upgrade to the very latest release.
Happy Scanning!
R