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  2000

SPM 2000

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Spatial normalisation of data for fMRI

From:

John Ashburner <[log in to unmask]>

Reply-To:

John Ashburner <[log in to unmask]>

Date:

Wed, 8 Mar 2000 11:17:37 +0000 (GMT)

Content-Type:

TEXT/plain

Parts/Attachments:

Parts/Attachments

TEXT/plain (132 lines)

Every method has its own advantages and disadvantages, and the ones you
list are only the tip of the iceberg when it comes to devising optimal
registration schemes.

Spatial normalisation within SPM estimates warps based on only about
1000 parameters.  Although this is enough represent the overall brain
shape reasonably well, there are a number of relatively small structures
with high contrast edges that require higher frequency deformations to
model them accurately.  A prime example of these is the effect of skull
thickness when spatially normalising T1 weighted images.  Scalp has very
high intensity in these images.  If the registration is based purely
on minimising the sum of squared difference between image and template,
then getting the scalp right will be very important to the algorithm
in terms of minimising the cost function.  However, if the subject has
a thick or thin skull, then getting the scalp right will mean that the
brain surface is not right (because the low frequency warps can not
model high frequency differences in skull thickness).  This is why the
brain masking step was introduced in order to make the cost function
the weighted sum of squares difference.  Voxels outside the brain have
lower (or zero) weight in the registration.  The disadvantage of this
is that it is not always as stable as the unweighted registration,
because less information is used.  Therefore, the bottom line is that
you should probably use the brain masking if the scalp has high intensity
in your images, but don't use it if the scalp is hardly visible (as in
EPI and most PET images).

Some people choose to skull strip their images (and templates) before
spatially normalising them.  This removes the confounding information
from the scalp, but retains the information about the edge of the brain.
This is not the default action within SPM, as skull stripping is either
very tedious to do manually, or difficult to do automatically on images
with a wide range of different contrasts.

A related issue is to do with the ventricles.  Again, these are small
structures, with a high contrast between CSF and white matter (on T1
weighted images).  Getting the edge of the ventricles correct is
important to the spatial normalisation algorithm.  However, for
functional imaging you are only interested in getting the grey matter
as correct as possible.  One possible option is therefore to spatially
normalise based on segmented grey matter, matching it to the grey matter
probability map in the apriori subdirectory.  We have tried this, and it
gives better grey matter registration for the cerebral cortex. However,
for some reason that I will need to look into more closely, the registration
is not quite as good around the cerebellum.  Also, for our data it produced
a small systematic difference in the shape of the spatially normalised
images.

I think that distortions of the functional images is probably one of the
bigger problems.  Because the functional images are a different shape
to the structurals, it is not possible to get an extremely accurate
rigid body registration between them using the current methodology in SPM.
If this mapping is not accurate, then estimating spatial normalisation
parameters from a structural image, and applying it to the functionals
will also not be very accurate.  For these cases, it is probably better to
estimate the warps from the functional images themselves.

There are also issues about FOV, image quality, same contrast in images
and templates etc that I am sure I have mentioned many times.  I realise
that this waffle hasn't directly answered your question, but it may have
increased understanding of what the brain masking option does, and
highlighted a few things to think about if anyone is planning to do
some comparisons.

Although not about fMRI, there is one paper out there (that I know about)
that compares spatial normalisation using structural MRI versus that using
functional images.  It is by Meyer et al, in NeuroImage 9:545-663 (1999).


All the best,
-John



| I have a question about how one should normalise EPI fMRI datasets.
| There seems to be (at least) three possible approaches, and I wonder if
| there is a consensus on which is best (or least worst....)
| 
| 1) Take a set of high-resolution T1 weighted slices in the same plane
| and with the same FOV as the EPI slices. Normalise this to the T1
| template and then apply the normalisation parameters to each EPI volume.
| 
| 2) Take a high-resolution multi-shot EPI image, again with exactly the
| same parameters as the single -shot functional EPIs, normalise this to
| the EPI Template and then apply the normalisation parameters to the
| single-shot functional EPIs
| 
| 3) Simply normalise the single-shot functional EPI (usually the mean
| image from the realignment) to the EPI template.
| 
| In spm99b, option (3) appears to work really well, so long as the
| spm_defaults are modified so that the BrainOnly option is disabled, and
| it has the advantage of not requiring any other acquistions. It also has
| the advantage that the spatial distortions inherent in single shot GE
| EPI are corrected for. However, there is an assumption here that those
| distortions *should* be corrected. Surely there are some artefacts on
| such images which are dropouts and so that particular region should not
| be pulled out to match the edge of the template.
| 
| We have done a quick comparison of (1) and (3) on two of our group
| studies. On one of our studies we obtained more significant activations
| in the final statistical analysis if we used option (3) (i.e.
| normalising the single shot EPIs directly) compared to (1). This was
| initially a surprise as we naively expected only the location of the
| clusters to change. We then came up with the idea that probably option
| (3) was bringing the group data into better register with each other -
| hence the better statistics.
| 
| Of course, it had to happen, in the other study we looked at, Option (1)
| gave better final statistical results than Option (3).
| 
| Any thoughts? I'd be really interested to know what other groups are
| doing, and whether anybody has done a more rigorous comparison of the
| various methods.
| 
| Thanks in advance,
| 
| krish
| 
| 
| --
| Dr Krish Singh, ([log in to unmask])
| Magnetic Resonance and Image Analysis Research Centre, Liverpool
| University
| Pembroke Place, Liverpool, L69 3BX, UK. Tel 0151 7945645. Fax 0151 794
| 5635
| 
| 



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

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