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  

|
September 23, 2014 03:49PM
To followup on Gang. In your case, the answer is C.

Since each participant is contributing a single value for each voxel, 3dttest++ has no way of knowing that it was a "dead voxel" for a particular participant. I imagine it would be hard to identify a "dead" voxel by the stats files alone going into a group analysis program as 1) zero is a valid number and 2) I suspect that the value of those dead voxels after preprocessing ends up being something other than zero given the certain level of interpolation related to preprocessing (slice timing, motion correction, alignment, smoothing).

I suspect that you could use the entire time series and some interesting masking procedures to try and identify "dead voxels" and interpolate a value into them from neighboring voxels.



Edited 2 time(s). Last edit at 09/23/2014 03:51PM by Peter Molfese.
Subject Author Posted

3dttest++, masks, and constant values

shanusmagnus September 23, 2014 02:06PM

Re: 3dttest++, masks, and constant values

gang September 23, 2014 03:37PM

Re: 3dttest++, masks, and constant values

shanusmagnus September 23, 2014 09:10PM

Re: 3dttest++, masks, and constant values

Peter Molfese September 23, 2014 03:49PM