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  2005

SPM 2005

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Conjunction Analysis

From:

Karl Friston <[log in to unmask]>

Reply-To:

Karl Friston <[log in to unmask]>

Date:

Thu, 19 May 2005 16:55:03 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (90 lines)

Dear Uwe,

>We measured 12 subjects in an event-related fMRI study
>(1) on a perceptual cueing task in one session and
>(2) on a motor cueing task in another session.
>Both tasks used the same stimuli, responses, and
>stimulus-response mappings. Cues were valid in 150 trials
>and invalid on 50 trials. The only difference between
>tasks consisted in the meaning of the cues.
>
>On the first level we looked in each subject at the
>contrast *invalid cues > valid cues* in each task.
>Now, we want to know whether there are regions that
>are common to the processing of invalidly cued trials
>in each task. Therefore we want to perform a conjunction
>analysis with the contrast *invalid > valid* in the
>motor cueing task and the contrast *invalid > valid*
>in the perceptual cueing task.
>
>As far as I understand your paper, we would use the
>minimum statistic if we could assume that the contrasts are
>congruent. However, I think, we have incongruent contrasts
>because we compare different cognitive tasks.
>Therefore, we might have a case for the supremum
>P value approach (conjunction null). The result of this
>conservative test is that we have 7 small clusters
>(5 with one or two voxels) - a result that is worrying the
>reviewers (saying, *your findings rest on thin ice*).


This speaks to the first of two important points: Your reviewers should
not be making anecdotal inferences like "resting on thin ice" on the
basis of the number of clusters, or voxels per cluster, unless they know
the null distribution of these quantities.  You should tell the Handling
Editor this.
  The NUMBER OF SIGNIFCANT VOXELS (or clusters) is not a useful
quantity. It is not equivalent to a "SIGNFICANT NUMBER OF VOXELS"
(or clusters above some threshold).  This inference would require a
further random field theory analysis at the cluster- or set-level
(see Friston et al 1996).
For example, 7 clusters at a p<0.05 level (corrected) means that you
found 7 x 20 = 140 times the number expected under the null hypothesis.
This is probably extremely significant.  Likewise, obtaining a cluster
of 2 voxels by chance could be extremely unlikely.
  I am not sure where the practice of reporting or discussing the number
of significant voxels came from but you should avoid it when reporting your
results and discourage its practice when reviewing other peoples papers. In
terms of reporting your results, simply show the SPM at an uncorrected
level of p=0.001 (uncorrected) and report, in the text and tables, maxima
that survive a correction for the search volume.  This allows the reader to
see the profile of the SPM that is used for inference and to read about the
inferences per se (in terms of significant maxima).
This inclusive reporting of the SPM precludes complaints that you should
have got more significant voxels!


>As I read your paper, I conclude that we should rather test
>for k > 1. Then the question arises, how to do this in the
>available version of SPM2?

Yes, you want to infer that k = 2 > 1, namely that effects were
present in both contrasts.  This is the conjunction null.  As we
tried to convey in our paper, simply thresholding both contrasts at
p<0.05 (corrected) and reporting the conjunction is valid but extremely
conservative (insensitive).  There are a number of ways you could
proceed.  However, given you have 7 maxima that survive this procedure
I do not think you really need to worry - just lower the threshold on
the SPMs that are reported graphically as described above.

If you wanted to pursue a more sensitive analysis you could try the
following procedure:  At the second-(between subject)-level you have
two contrasts C1 and C2.  Threshold C1 at p=0.001 (uncorrected) and
form a mask.  Apply this mask to the images and threshold C2 at p=0.05
(corrected for the [masked] search volume).  Save the resulting SPM{T},
which contains voxels that are significant for C2 at p=0.05 corrected.
Now repeat the procedure but swap C1 and C2.  Voxels that are found in
both SPM{T} are significant at p=0.05 corrected in both contrasts and
constitute voxels where you can infer k = 2.

I will leave it as a challenge to see if anyone can spot a flaw in this
procedure :)

I hope this helps - Karl

PS  There are updates for SPM2 that allow tests of the conjunction null:
Tom - can you comment on this?

Friston KJ, Holmes A, Poline JB, Price CJ, Frith CD. Detecting activations
in PET and fMRI: levels of inference and power. NeuroImage. 1996 4:223-35.

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