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  

|
April 23, 2018 02:43PM
Hi,

Thanks for your reply. Again, I'm still very new to AFNI but what we are trying to do is to simply analyze the resting state data (does not include the other runs). We are still in the initial stages of preprocessing the Oblique T1 MPRAGE (anat data) and the resting state Oblique Axial ep2d bold data (EPI data).

Currently our issue with the first 3 lines is that we have both an oblique anat and functional dataset. From my understanding, we have to fix the obliquity of our anat and create a straight anatomical reference to enable support for our oblique functional. The -rotyourself will rotate our oblique anatomical to *itself* rather than a straight anatomical since we don't have a straight anatomical reference (normally we would use -rotobrick). However, when we try to apply our oblique functional on this now "straight" anat (using the -rotobrick function to process the functional using the processed anatomical as the -rotobrick reference), an error occurs stating that: "ERROR: Failed to handle oblique (tolerance exceeded)."

We've already applied the maximum tolerance possible as stated, but still we are receiving these errors and preferably we would like not to use any tolerance at all.

This is all prior to performing slice timing, motion correction, spatial normalization, and smoothing. We tried experimenting with it by adding 3dWarp functions which ended up running with no problems. However, when we check for coregistration between our anat and epi, the alignment is very off so we think this issue is in regards to the obliquity at the start of our preprocessing and less to do with the slice timing, moco, normalization, etc.

Again, still very new to AFNI but I'll check out this DIMON program and see if there is anything there that can help us with this obliquity problem. Any other tips / helpful advice would be very much appreciated!

Thanks!!
Subject Author Posted

AFNI fMRI Preprocessing / 3dWarp

monarch April 20, 2018 09:26AM

Re: AFNI fMRI Preprocessing / 3dWarp

Peter Molfese April 20, 2018 09:51AM

Re: AFNI fMRI Preprocessing / 3dWarp

ptaylor April 21, 2018 09:15AM

Re: AFNI fMRI Preprocessing / 3dWarp

monarch April 23, 2018 02:43PM

Re: AFNI fMRI Preprocessing / 3dWarp

Peter Molfese April 24, 2018 04:22PM