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  

|
March 04, 2022 11:49AM
Adding on to Bob's good advice, you can use 3dAllineate to compute the "in-between" space too. cat_matvec can compute this with from the affine transformation with the -S (square root) option. We have a script here that does something similar for a single subject across two sessions:

https://sscc.nimh.nih.gov/sscc/dglen/alignmentacross2sessions

That in-between volume is meant to remove bias from either of the source sessions. This part only concerns the affine part of the alignment. For the nonlinear part, as Bob noted, you will need to use 3dQwarp.

Another important consideration is to make the data intensity values similar if you are computing a mean "template" with 3dUnifize. Most of this kind of thing is done in make_template_dask.py (a successor for the similar scripts you mentioned), but that's not distributed in our standard AFNI distribution yet, and it's probably overkill for this similar but somewhat simpler situation.

If sizes are very similar, you might consider using a rigid_body or rigid_equiv version of the affine transformation. These are both options for align_epi_anat.py that includes calls to 3dAllineate. The rigid_body limits the alignment by using 3dAllineate's "-shift_rotate" option. The rigid equivalent also produces a transformation that does not scale or shear the dataset, but it's derived from the full affine transformation (compute with cat_matvec -P or use align_epi_anat.py). With data from different subjects, it's likely this would be preferable.

Twins, even "identical" twins, aren't really identical, so it's hard to say if their brains would be a very close match. Monochorionic twins, for example, can have very different anatomical characteristics.
Subject Author Posted

Custom Study-Specific Template for Case Study

prasadee March 01, 2022 02:40PM

Re: Custom Study-Specific Template for Case Study

RWCox March 04, 2022 08:14AM

Re: Custom Study-Specific Template for Case Study

Daniel Glen March 04, 2022 11:49AM

Re: Custom Study-Specific Template for Case Study

RWCox March 04, 2022 09:22PM