help > How to go from FSL to gPPI (and back again)
Showing 1-2 of 2 posts
Nov 19, 2012 09:11 PM | Christopher Chatham
How to go from FSL to gPPI (and back again)
Hi - I am delighted to see this toolbox has been released and am
very excited to try it on my own data. I typically work within FSL
but there is no deconvolution algorithm of this kind available in
that package.
As an FSL user, how should I go about doing my deconvolution with this package, so that I can then actually conduct the gPPI analysis within FSL? Do I actually need to redo my first-level analyses in SPM, or is there a way for me to get the deconvolution step done without going to all that trouble? Short of switching to SPM altogether, what would you recommend?
Thanks for any help,
-Chris
As an FSL user, how should I go about doing my deconvolution with this package, so that I can then actually conduct the gPPI analysis within FSL? Do I actually need to redo my first-level analyses in SPM, or is there a way for me to get the deconvolution step done without going to all that trouble? Short of switching to SPM altogether, what would you recommend?
Thanks for any help,
-Chris
Apr 19, 2013 03:04 AM | Donald McLaren
RE: How to go from FSL to gPPI (and back again)
Chris,
Sorry for the delayed response. I'll also repost on the FSL/SPM lists.
As an FSL user you have 2 options:
(1) Form a series of interactions, 1 for each condition by multiplying the condition by the seed region. Then form the model using N interaction terms, N task regressors, the seed region regressor, and any covariates you had in the original task model.
(2) Redo the first-level analysis in SPM.
The issue isn't so much doing the deconvolution as much as that the deconvolution portion is heavily integrated into the code.
As far as I know, no one has looked at the effect of deconvolution on event-related PPI.
Hope this helps.
Sorry for the delayed response. I'll also repost on the FSL/SPM lists.
As an FSL user you have 2 options:
(1) Form a series of interactions, 1 for each condition by multiplying the condition by the seed region. Then form the model using N interaction terms, N task regressors, the seed region regressor, and any covariates you had in the original task model.
(2) Redo the first-level analysis in SPM.
The issue isn't so much doing the deconvolution as much as that the deconvolution portion is heavily integrated into the code.
As far as I know, no one has looked at the effect of deconvolution on event-related PPI.
Hope this helps.
