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  

|
February 17, 2023 02:48PM
Hi Angelika,

EDIT: Oh my, Paul has gotten me back... maybe this post is moot.

Different software has created NIFTI datasets with different intentions in the sform/qform_code fields, making a value of 2 there ambiguous. It is generally applied incorrectly even.

To be sure, what is the output of:

nifti_tool -infiles 1002002_V001_DMSRun1.nii -disp_hdr -field sform_code -field qform_code

If those fields are equal to 2 AND if the EPI has not been registered to anything (in which case they should not be 2), then set the AFNI_NIFTI_VIEW environment variable to orig. This can be done in your $HOME/.afnirc file, in your shell environment or just in the script, as you prefer. For example, edit your ~/.afnirc file to have a line like:

AFNI_NIFTI_VIEW = orig

Please let me know how that goes.

Thanks,

- rick



Edited 1 time(s). Last edit at 02/17/2023 02:49PM by rick reynolds.
Subject Author Posted

** already in tlrc space: -volreg_tlrc_* is not allowed

angelika February 17, 2023 02:04PM

Re: ** already in tlrc space: -volreg_tlrc_* is not allowed

ptaylor February 17, 2023 02:40PM

Re: ** already in tlrc space: -volreg_tlrc_* is not allowed

rick reynolds February 17, 2023 02:48PM

Re: ** already in tlrc space: -volreg_tlrc_* is not allowed

angelika February 23, 2023 02:06PM

Re: ** already in tlrc space: -volreg_tlrc_* is not allowed

rick reynolds February 23, 2023 02:46PM

Re: ** already in tlrc space: -volreg_tlrc_* is not allowed

angelika February 23, 2023 05:14PM

Re: ** already in tlrc space: -volreg_tlrc_* is not allowed

rick reynolds February 23, 2023 05:54PM

Re: ** already in tlrc space: -volreg_tlrc_* is not allowed

angelika February 24, 2023 09:45AM

Re: ** already in tlrc space: -volreg_tlrc_* is not allowed

rick reynolds February 24, 2023 09:59AM