AFNI Message Board

Dear AFNI users-

We are very pleased to announce that the new AFNI Message Board framework is up! Please join us at:

https://discuss.afni.nimh.nih.gov

Existing user accounts have been migrated, so returning users can login by requesting a password reset. New users can create accounts, as well, through a standard account creation process. Please note that these setup emails might initially go to spam folders (esp. for NIH users!), so please check those locations in the beginning.

The current Message Board discussion threads have been migrated to the new framework. The current Message Board will remain visible, but read-only, for a little while.

Sincerely, AFNI HQ

History of AFNI updates  

Previous Message Next Message
Message List New Topic Print View
|
Daniel Glen
March 17, 2010 08:20AM
I think you're right. The feature is the obliquity support that are responsible for both your issues. In the AFNI format, the obliquity only affects one AFNI attribute, the IJK_TO_DICOM_REAL. For NIFTI, that field is used to define the s-form of the NIFTI format to define the coordinate system. Your workaround of using an AFNI format would work, but you would have to reset the IJK_TO_DICOM_REAL to the cardinal equivalent with "3drefit -deoblique" before copying to NIFTI.
Reply Quote
RSS
Subject Author Posted

to3d ignores -zFOV for NIFTI output but not BRIK

Fred Tam March 17, 2010 01:45AM

Re: to3d ignores -zFOV for NIFTI output but not BRIK

Daniel Glen March 17, 2010 08:20AM

Re: to3d ignores -zFOV for NIFTI output but not BRIK

Fred Tam March 17, 2010 11:08PM