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  1998

SPM 1998

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Single-subjects vs. nl database [SPECT]

From:

[log in to unmask] (Karl Friston)

Reply-To:

[log in to unmask] (Karl Friston)

Date:

Tue, 1 Sep 1998 15:03:37 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (130 lines)

Dear Christopher,


> I am in the perhaps unenviable postion of identifying CBF deficits in a
> clinical group in which the location of these abnormalities is not
> uniform. Therefore, I cannot compare this group as a whole to a
> normative database, but need to assess the extent of abnormality in
> each individual.  In preparing to do this with SPM, several decisions
> arise:
> 
> These are SPECT [HMPAO] data using very high-resolution, fan beam
> collimated gamma cameras. We were careful to administer the same
> activity of tracer to every subject, and to acquire a comparable number
> of counts for each scan. The point resolution in air for this system is
> 7-8mm FWHM.  While this resolution is comparable to most PET systems
> for CBF imaging, my sense is that SPECT data are nevertheless
> considered inferior for the pruposes of modeling with SPM. The general
> recommendation is to use proportional scaling for SPECT-perfusion data.
> My understanding is that this reflects more "significant" global
> confounds with these data, which means a larger range of global mean
> values AND regional variance which is confounded with that global
> variability. I beleive I can test the degree to which this is the case
> in my dataset, but not in native SPM. I am not a matlab-maven, nor do I
> have one in my group [but I do know some]. Is there a relatively
> straightforward way for me to assess the  appropriateness of ANCOVA for
> my data?

I would stick to proportional scaling.  AnCova has only been validated for
parametric rCBF data.  There is no need to confirm or disconfirm the AnCova
model for SPECT if you use scaling normalization.

> Less esoteric are the following: this study is designed to test the
> recovery of flow deficits in treatment. We have three scans for each
> subject over the period of treatment. We thus designed a databse of
> controls scanning each three times, so as to atake into account normal
> within-subject variability over time with this scanning system.
>  
> The research questions are 1) how severe are the flow deficits for a
> given subject, and 2) how much do they change [if at all] over the
> course of treatment?
> 
> To answer the first, I had originally thought to use only the baseline
> scan[pre-treatment]. This however leaves me with the problem of
> comparison of a single measure to a databse which contains repeated
> measures within subjects.
> 
> My first option in SPM96 is, I believe, "compare groups:single scan per
> subject". My plan is to use all normal scans as one group, allowing
> that the repeated measures within some of these subjects will add to
> the population variance AS IF the normal database represented random
> sampling allowing for replacement of previously sampled subjects.
> However, this does not make the best use of the data as collected. If I
> am to account for as many confounds as possible, I would like to add in
> data regarding age, gender, perhaps extent of smoking, and model the
> within-subject variability separately from across-subjects.
> 	
> The next option would be "Multi-study: replication of conditions". In
> this, I would have two studies, one for each group. For all subjects
> with three scans, I am all set. Two questions:
> 
> I believe I am required to eliminate subjects who do not have all
> datapoints with this model; for the case of controls in which I have
> only two of three repeated measures, I would propose to use a mean
> image of these [or perhaps enter one twice]. Is this valid?
> Second, the problem of using all three scans from a patient, in which
> we predict there is a time- and/or treatment related change in regions
> which are abnormal at baseline.  One option is to use only the first
> scan, allowing the model to partition within-subject repeated
> variability differently from the comparison between these two groups.
> Another is to use all three time points, given that the change in
> abnormal regions, "normalization", is incomplete-- thus, even the last
> time point contains disease-related variance in some regions from the
> normal group. This appears to be an attractive option, *particularly*
> if the "plotting" option will, as it seems, allow me to discern the
> effect size at each timepoint separately for any region which is
> returned as significantly abnormal for the group of three scans. Can
> anyone tell me, a priori, if I am going to lose more in sensitivity by
> including all three scans [since the effect size, in some cases at
> least, will decrease with each scan], than I would gain in specificty
> by testing all three as opposed to a single, "diagnostic" image?

I think the crtical thing here is to ensure that the d.f. are less than
the number of subjects analyzed.  This ensures that you are not conflating
variance due to repeated measures with inter-subject variability.  In other
words it ensures you are using a proper random effects analysis.  The
best way to do this is for:

(i) [simple] main effect of group

Analyze the 1st scan per subject (or the sum of two scans per subject),
using - compare groups:single scan per subject

(i) group x time interaction (i.e. time- and/or treatment related change)

Analyze 2 scans per subject using 'Multi-subject: different conditions'
(i.e. 2 conditions).  Interactions would then be tested for using
contrasts like [-1 1 1 -1].  Note that here the subject or block effect
(i.e. effect of interest in the first analysis) is treated as a
confound so that each subject only contributes one 'difference'.


> The next order of complexity would be to include the covariates I
> mentioned. In the case of "Multi-study: conditions and covariates", I
> would again have two studies [normals and patient]. I would then
> include as covariates of no interest [confounds] age, gender, smoking,
> and time [1, 2, or 3], to specify regions which differ, as much as
> possible, only on the clinical status of interest.

This is absolutely right (although it would not model confound x time
interactions i.e. if you think age attenuates non-specific scan order
effects then you might want to include this interaction as another
confound)

> My question here to the framers of SPM, or anyone else who can tell
> me: how does this model differ from, for  example, using
> "Multi-subject:conditions and covariates" in which I enter the same
> covariates immediately above BUT include clinical status [control or
> patient] as a covariate of interest?

There is no difference - as you probably guessed (unless you are
looking at interations - see above).


With best wishes,

Karl


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

May 2024
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