Hello,
I’m trying to use the gltsym command with 3dDeconvolve to run linear tests between my conditions in different time points.
I don’t understand in the output matrix the order and the numbers of the lags. By defining the lags [2…4] I expected to get 3 time points for each variable, and not 4 (as the output suggests).
That means you should only have 4 parameters per
class, not 6, meaning 2…4 is actually out of range.
I hope you are getting more warnings out of this,
but it looks like 3dDeconvolve is actually applying
“+violence -disgust” (meaning [0…3] for each).
What is the complete text output?
In any case, think about that you really want, as
there are only 4 betas to begin with.
Hmmmm. But the IRF output for CSPLINzero has 6 parameters: the 1st and 6th are 0 and then the are betas are at 1,2,3,4. So- are you saying that in 3dDeconvolve when we specify the “lag” (see below), we are supposed to change from 2…4 to 1…3? That seems OK, but is that documented anywhere do you know? thanks, nicola
So, for instance, following the -gltsym command, we were putting the lags of the STIM we wanted to use in the test.
Stim[2…7] = means put +1 in the matrix for lags 2…7 of Stim
This is just a little confusing because the iresp options
have slightly different behavior than the betas, and it is
the betas that correspond to the gltsym indices.
The -iresp option shows a TR-locked time series (unless you
specify otherwise) for the duration of the CSPLIN. But the
betas (and regressors), which correspond to the stim class
indices in the GLTs, are as you specify with the parameters.
In this case I will assume your TR = 3s, since you say the
iresp output has 6 time points. But there are still only
4 regressors in the design matrix, because you used the
‘zero’ version of the basis function name. And since there
are only 4 regressors, the index of 4 is out of range, and
should give you an error message probably like:
** ERROR: selector index 4 is out of range 0…3
Though the command will still run (that is probably a
mistake, it should probably fail).
Yes, you should change 2…4 to 1…3 because the actual
basis function that you are using is CSPLIN(3,12,4). This
sort of confusion is why I suggest not using ‘zero’
versions of these basis functions. They are just a
programming convenience to assume the end points
are zero, rather than estimating them.
Forget +1 and such. I suggest not using CSPLINzero,
but using CSPLIN the way your really want to. Do you
want CSPLIN(3,12,4)? If so, use that instead.
One more question, if you don’t mind. Let’s say we use CSPLIN (3,12,4) and then do a contrast between 2 conditions at one lag. e.g:
+cond1[1] -cond2[1]
Will the coefficient that is printed for the glt at each voxel be the DIFFERENCE of the IRF’s for each condition for this at this timepoint?
i.e. will the coefficient = IRF.cond1[1]-IRF.cond2[1]?
In the 3dDeconvolve documentation, it indicates that the coefficient will be equal to hr[1] - he[1]
(see pg. 45, example 1.4.4.3)
Yes, that contrast should be the difference in lag 1
values (offset 6 seconds from the event times in this
case) between the cond1 and cond2 classes.
rick
The
National Institute of Mental Health (NIMH) is part of the National Institutes of
Health (NIH), a component of the U.S. Department of Health and Human
Services.