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  

|
November 15, 2013 01:27PM
Thanks for the replies, but there is something that's still confusing me about this obliquity issue.

When I reconstruct my anatomical and EPI scans from DICOMs with the following commands

to3d -prefix 8101-T1 8101_DICOMs/*.dcm
to3d -skip_outliers -prefix 8101-EPI-01 -time:zt 27 273 2.0s alt+z EPI01_DICOMs/*.dcm

both are oblique.

If I then try to align the anatomical scan to the first volume in the EPI (after slice-time-correcting the EPI) with the following command

align_epi_anat.py -anat 8101-T1+orig -epi pb01.8101.r01.tshift+orig -epi_base 0 -volreg off -tshift off

the resulting alignment is *terrible* and when I look at it in the viewer, AFNI warns me about the datasets being oblique.

But, if before running align_epi_anat, I do the following to my scans

3drefit -deoblique -xorigin cen -yorigin cen -zorigin cen 8101-T1+orig
3drefit -deoblique -xorigin cen -yorigin cen -zorigin cen 8101-EPI-01+orig

the alignment is very good. This makes no sense to me, because 3drefit claims not to alter the .BRIK at all, but only to change information in the header. Furthermore, the 3drefit documentation says the "-deoblique" option should not be used "unless you really know what you're doing," and I don't.

I issued 3drefit in this way to the EPI before running 3dTshift, and I'm afraid I may be screwing up the slice-time information, but I can't find anything in the documentation that speaks to this.

Perhaps a better option for me is to leave the EPI alone before running align_epi_anat, and warp the anatomical scan so that it matches the obliquity of the EPI scan. Or maybe I should run 3dTshift, and then deoblique (with 3dWarp, as opposed to just changing the header with 3drefit) both the EPI and anatomy. After running 3dWarp, would it then be appropriate to change the header with the same 3drefit calls I have above?

What is my best option here? I want to preserve my EPI data as much as I can (warp it as little as possible).

Thanks,
Dan
Subject Author Posted

Dealing with oblique datasets

dbliss November 13, 2013 11:50PM

Re: Dealing with oblique datasets

Peter Molfese November 14, 2013 12:12AM

Re: Dealing with oblique datasets

dbliss November 14, 2013 01:24AM

Re: Dealing with oblique datasets

Peter Molfese November 14, 2013 09:06AM

Re: Dealing with oblique datasets

Daniel Glen November 14, 2013 03:39PM

Re: Dealing with oblique datasets

dbliss November 15, 2013 01:27PM

Re: Dealing with oblique datasets

dbliss November 15, 2013 01:40PM

Re: Dealing with oblique datasets

Daniel Glen November 15, 2013 01:52PM

Re: Dealing with oblique datasets

dbliss November 15, 2013 02:01PM

Re: Dealing with oblique datasets

Daniel Glen November 15, 2013 02:44PM

Re: Dealing with oblique datasets

dbliss November 15, 2013 03:10PM

Re: Dealing with oblique datasets

jbteves September 16, 2021 04:35PM

Re: Dealing with oblique datasets

Daniel Glen September 17, 2021 03:03PM