JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for SPM Archives


SPM Archives

SPM Archives


SPM@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

SPM Home

SPM Home

SPM  November 2010

SPM November 2010

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: PPI question

From:

Darren Gitelman <[log in to unmask]>

Reply-To:

Darren Gitelman <[log in to unmask]>

Date:

Mon, 22 Nov 2010 10:36:31 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (144 lines)

Dear Ruth:

Your methods below bring up several issues.

1) I don't think it is a good idea to threshold your fmap at a
threshold of 0.999 since you will probably include voxels that have
nothing to do with your conditions of interest. This has been debated
before on the list (I don't have references) but I would generally
suggest a threshold of 0.001 uncorrected, although I should add that
this advice is mostly based on the recommendations of others and not
because I have studied different thresholds. The point of my quote
below was to emphasize 2 things: 1) That the contrast does not affect
the data that's extracted (assuming a voxel appeared in different
contrasts)- because SPM goes back to the raw data before adjusting it,
and more importantly 2) that the contrast you choose is a window to
the voxels in that it shows you voxels that are likely to have some
relationship to the conditions you are interested in. Indeed there is
no point in including voxels in your ROI that have no relationship to
the conditions of interest. This is a point that I think Klaas has
made in the past for DCM but applies equally well to PPI.

2) I disagree that one needs to include all voxels in a ROI,
especially for very large ROIs where differences in both an individual
subject's anatomy and function are likely to be influencing the
locations of activated voxels. This is likely to be true even if we
could normalize subjects perfectly, which we cannot do. Therefore
including all voxels in a ROI across your population would almost
certainly mean including voxels whose activity had nothing to do with
your task.

3) The 16 mm radius sphere is very large. I think you would have a
hard time convincing a reviewer (if not yourself) that all the voxels
in such a sphere would really be related to your task. In general
spheres of 4-8 mm radius are used depending on the amount of smoothing
and the location in the brain. I'm not sure what you mean that if you
use a sphere of smaller radius you couldn't find activated voxels in
all your subjects. Are you using a fixed location for the sphere?
Generally I recommend selecting ROI's in a subject specific manner.
One could do this by determining for the group the location of the
activation maxima for a particular contrast and then choosing the
activation for each subject that's "as close as possible" to the xyz
location of the group maxima. (Alternatively the group locus could be
specified based on anatomy or reports in the literature.) This allow
you to select the ROI for each subject so that it is located in the
proper area and contains voxels that are related to your contrast. In
general, depending on smoothing and location in the brain, one would
like the locations of the various subject specific ROI's to be within
1-1.5 cm of each other (or less).  If this means that some of your
subjects cannot be included in the PPI analysis, that's what you
should do since those subjects would not appear to have activations
related to the task.

4) I'm not sure I understand how you are extracting the time series
and calculating the PPI. Are you using the eigenvariate button to
extract the time series (in SPM8 or the VOI button in SPM5), followed
by clicking the PPI button which performs the deconvolution and sets
up the PPI interaction term for you? If not how are you deconvolving
the time series? Please note that the first eigenvariate is not a
deconvolved time series. It would be entirely incorrect to form the
PPI term by multiplying the first eigenvariate by the task effects and
reconvolving with an HRF (see Gitelman et al., Neuroimage, 19:200-207,
2003).

Darren


On Mon, Nov 22, 2010 at 6:32 AM, Ruth van Holst <[log in to unmask]> wrote:
> Dear PPI experts,
> I am currently working with Psychophysiological interaction (PPI) analyses
> and have some question about my applied method so far.
>
> I did the following:
>
> To identify the left IFG activation for each participant we examined the F
> contrast of all conditions at p<0.999 uncorrected, to obtain similar amount
> of voxels in or VOI across all subjects.  The deconvolved time series from a
> 16 mm radius sphere around the individually defined peak activated voxel
> within the left IFG was extracted (30 participants). The PPI was calculated
> as the element by element product of the left IFG time series (the first
> eigenvariate from all voxels' time series) and a vector coding for the
> effect of task. These products were subsequently re-convolved with the
> hemodynamic response function (HRF). The interaction term was then entered
> as a regressor in a first level model together with the time series of the
> left IFG and the vector coding for the task effect. The models were
> estimated and contrasts generated to test the effects of positive PPI. These
> contrast images for the PPI effects were then entered in a second level
> analysis.
>
>
> These choices were based on he SPM forum list, were I understood the following:
>
> “you should think of the contrast you use to display the activations as
> simply a window to which voxels will be extracted. SPM goes to the xyz
> locations of the active voxels in your VOI, gets the actual data from your
> processed images and then adjusts the data for any effects of interest you
> specify. The contrast you use to display activations merely identifies the
> voxels to extract data from it does not affect the data that are extracted.”
> By Darren Gitelman
>
> Therefore I used a absurdly low threshold of p<0.999 to capture all activity
> in the VOI and to make sure that the below mentioned advise could be
> assured.
>
>
>  “Always use ALL the voxels in the ROI. You don't want to compare a subset
> of voxels in one subject to a subset in other subjects, then you might be
> getting apples and oranges. This is of course a bigger issue if you were to
> use a larger ROI.” By Donald McLaren
>
>
>
> I do think that a sphere of 16 radius is quite large, but when using a
> smaller radius I could not detect activity in this region for each
> participant. This would be a problem because excluding participant form this
> analysis would be a waste as well.
>
>
>
> The results from this analyses look sensible, but I am unsure if my method
> is decent enough to pursue writing it down.
>
>
>
> I hope that you are able to give your opinion about my chosen PPI strategy.
>
> Thanks in advance for your time,
>
> Best wishes
>
> Ruth
>
>
>
>



-- 
Darren Gitelman, MD
710 N. Lake Shore Dr., 1122
Chicago, IL 60611
Ph: (312) 908-8614
Fax: (312) 908-5073

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager