History of AFNI updates  

|
December 14, 2018 09:46AM
Hi 2086,

1. Yes, map the volume registered time series to the
surface, as is done in in the surface analysis class
example with:
afni_proc.py command : s03.ap.surface
resulting proc script: s13.proc.FT.surf

Basically, do not even use the original surfaces.
Yes, the -surf_anat dataset is the same for original
surfaces as for standard mesh surfaces.

You would have to be careful mapping the stats, but it
should work, I think. If you view the results before
and after mapping, they should look almost identical.
Of course, this will add a small blur to the result
which is not accounted for.


2. In AFNI, surface analyses are run on each hemisphere,
not via the 'both' spec file. See the afni_proc.py
command linked to above.

You can use *any* standard mesh surface (of the same
resolution) to show the results. Node correspondence
comes via FreeSurfer's internal spherical registration.
Assuming that works, any corresponding standard mesh
surface is okay.

A good choice might be a template. If you can run
that MNI305 dataset through FreeSurfer and then import
it into AFNI (via @SUMA_Make_Spec_FS -NIFTI), then all
results can be shown there.

- rick
Subject Author Posted

Running into 3dVol2Surf Error

Dan October 09, 2018 01:29PM

Re: Running into 3dVol2Surf Error

rick reynolds October 09, 2018 04:43PM

Re: Running into 3dVol2Surf Error

Dan October 10, 2018 09:34AM

Re: Running into 3dVol2Surf Error

rick reynolds October 11, 2018 09:52AM

Re: Running into 3dVol2Surf Error

Dan October 11, 2018 10:34AM

Re: Running into 3dVol2Surf Error

rick reynolds October 15, 2018 10:13AM

Re: Running into 3dVol2Surf Error

EXP.2086 December 14, 2018 07:07AM

Re: Running into 3dVol2Surf Error

rick reynolds December 14, 2018 09:46AM