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  

|
January 21, 2016 02:01PM
Hello,

I have some questions regarding the new option -acf both for 3dFWHMx and 3dClustSim. To estimate the blurring across all subjects to determine acceptable cluster size at .005, I ran 3dFWHMx on each subject’s residuals (errts+tlrc). I averaged the three parameters across subjects to get the mean radius (r) and two fitted parameters (a & b). I entered these parameters into the 3dClustSim using the acf option fully expecting more conservative cluster size values but instead acceptable cluster were more liberal. When I estimated blur size using the old method acceptable cluster size was 71 voxels but with the new method (acf) it was 44 voxels.

1) Since acf is supposed to make clusters more conservative, is it possible to see this kind of decrease in acceptable cluster size when switching between methods for estimating the blur?

Looking into this further, a colleague noticed that when running afni_proc when 3dFWHMx is called the data is detrended (option –detrend). Since when I ran 3dFWHMx originally, I did not use the detrend option we thought this might be why cluster size became more liberal. So we reran 3dFWHMx on each subject using the same command adding the detrend option. The only other difference is that we fed 3dFWHMx the list of uncensored volumes. Results here showed a more conservative cluster size of 104 voxels.

2) Does it make senses that the difference in cluster size is due to detrending when calling 3dFWHMx? If so, would it be wise to make sure this option is called when estimating effective blur when getting the parameters for the –acf method?

Thanks for your help

Steve
Subject Author Posted

ACF, 3dFWHMx, 3dClustSim and Cluster Size

sgreen January 21, 2016 02:01PM

Re: ACF, 3dFWHMx, 3dClustSim and Cluster Size

Emperor Zhark January 21, 2016 04:10PM

Re: ACF, 3dFWHMx, 3dClustSim and Cluster Size

rick reynolds January 21, 2016 04:22PM

Re: ACF, 3dFWHMx, 3dClustSim and Cluster Size

sgreen January 21, 2016 04:39PM

Re: ACF, 3dFWHMx, 3dClustSim and Cluster Size

rick reynolds January 21, 2016 08:38PM

Re: ACF, 3dFWHMx, 3dClustSim and Cluster Size

SI January 25, 2016 07:09AM