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  

|
Daniel Glen
February 20, 2009 11:31AM
I think this all looks okay. The script will align the anat to the epi dataset by default including matching the epi dataset's obliquity. If the input time series has slice timing information, the script will use that info. 3dTshift can be used to supply slice timing info to the dataset if it's missing for some reason, but that should be a relatively rare occurrence (but it looks like it could be a problem for you). Likewise, the script will check for obliquity, and if it exists, it will use that. You can always call the align_epi_anat.py script from another script that fixes the input files. This previous thread discusses a couple ways to supply slice timing information for a dataset:
[afni.nimh.nih.gov]
Subject Author Posted

bug in 3dAttribute?

Colm Connolly February 19, 2009 06:32AM

Re: bug in 3dAttribute?

Daniel Glen February 19, 2009 09:58AM

Re: bug in 3dAttribute?

Colm Connolly February 20, 2009 11:09AM

Re: bug in 3dAttribute?

Daniel Glen February 20, 2009 11:31AM

Re: bug in 3dAttribute?

Colm Connolly February 20, 2009 11:45AM

Re: bug in 3dAttribute?

Daniel Glen February 20, 2009 12:11PM