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
|
Peter Molfese
February 20, 2018 10:47AM
I suspect that some of your input files are incorrectly labeled as being in standard space (+tlrc) in the NIFTI header. You can check this using 3dinfo.

I find it useful to explicitly define the blocks using a -blocks or -do_blocks command in afni_proc.py. Also if you want all of your data to end up in standard space, you likely want a -volreg_tlrc_warp in your command.

We usually suggest you start with one of the examples (like 6) for processing needs, these often have "best practices" built in. It's worth noting that bandpass filtering isn't usually used on task data.

-Peter
Reply Quote
RSS
Subject Author Posted

the same code run on different datasets -> +tlrc OR +orig produced

wo222 February 20, 2018 08:01AM

Re: the same code run on different datasets -> +tlrc OR +orig produced

Peter Molfese February 20, 2018 10:47AM

Re: the same code run on different datasets -> +tlrc OR +orig produced

wo222 February 21, 2018 09:09AM

Re: the same code run on different datasets -> +tlrc OR +orig produced

Peter Molfese February 21, 2018 10:29AM

Re: the same code run on different datasets -> +tlrc OR +orig produced

wo222 February 21, 2018 02:59PM