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 10, 2014 06:13PM
Hi,

I'm trying to prepare a go/nogo task for the scanner and I want to make sure my go's and nogo's are not collinear. At first, using the -nodata option in the following command and a TR of 2.5 seconds, I get a good result:

bash-3.2$ 3dDeconvolve -nodata 1098 2.5 -polort A -num_stimts 2 -stim_file 1 'go.txt' -stim_label 1 'GO' -stim_file 2 'go.txt' -stim_label 2 'NOGO'

However I am considering reducing the TR length, and wanted to see if they would remain collinear. I noticed that the output didn't change with a smaller TR, and then I tried drastically reducing the TR and even with 0.005s TRs the output is almost the same and tells me that the conditions are not collinear (see below). This seems impossible, since with an HRF peaking at ~5 seconds, and a full task length of 5.5s I cannot imagine that the go's and nogo's could be resolvable here.

How can I include some idea of HRF length (like GAM?) so that I can test if these are collinear and not just if the matrix itself is solvable?

Thanks!
Michael



bash-3.2$ 3dDeconvolve -nodata 1098 0.005 -polort A -num_stimts 2 -stim_file 1 'go.txt' -stim_label 1 'GO' -stim_file 2 'nogo.txt' -stim_label 2 'NOGO
'
++ 3dDeconvolve: AFNI version=AFNI_2011_12_21_1014 (Jul 30 2013) [64-bit]
++ Authored by: B. Douglas Ward, et al.
++ using NT=1098 time points for -nodata
++ Imaging duration=5.5 s; Automatic polort=1
++ Number of time points: 1098 (no censoring)
+ Number of parameters: 4 [2 baseline ; 2 signal]
++ Wrote matrix values to file nodata.xmat.1D
++ ----- Signal+Baseline matrix condition [X] (1098x4): 1.70702 ++ VERY GOOD ++
++ ----- Signal-only matrix condition [X] (1098x2): 1 ++ VERY GOOD ++
++ ----- Baseline-only matrix condition [X] (1098x2): 1 ++ VERY GOOD ++
++ ----- polort-only matrix condition [X] (1098x2): 1 ++ VERY GOOD ++
++ Wrote matrix values to file nodata_XtXinv.xmat.1D
++ +++++ Matrix inverse average error = 5.57179e-16 ++ VERY GOOD ++
++ Matrix setup time = 0.01 s

Stimulus: GO
h[ 0] norm. std. dev. = 0.0663

Stimulus: NOGO

h[ 0] norm. std. dev. = 0.0893
Subject Author Posted

Including HRF in nodata

3dFoodie September 10, 2014 06:13PM

Re: Including HRF in nodata

rick reynolds September 10, 2014 09:08PM

Re: Including HRF in nodata

3dFoodie September 11, 2014 10:54AM

Re: Including HRF in nodata

rick reynolds September 11, 2014 04:36PM

Re: Including HRF in nodata

3dFoodie September 11, 2014 05:42PM

Re: Including HRF in nodata

rick reynolds September 11, 2014 09:17PM

Re: Including HRF in nodata

3dFoodie September 12, 2014 01:46PM

fMRI power caculation

Juan September 12, 2014 08:32PM