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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

SPM Home

SPM Home

SPM  2006

SPM 2006

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Multi-step normalization

From:

Steve Smith <[log in to unmask]>

Reply-To:

Steve Smith <[log in to unmask]>

Date:

Thu, 21 Sep 2006 12:15:28 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (128 lines)

Hi John et al.,

First I'll clarify our terminology:
  - example_func = mid-timepoint image taken from the FMRI (normally
EPI) data
  - initial_highres (not normally used) = normally a full brain EPI,
when example_func is restricted FOV
  - highres = normally a brain-extracted whole-brain T1 structural
  - standard = normally the brain-extracted MNI152 T1 average

The normal usage in FEAT (FSL's FMRI GLM tool) is a two-stage
registration:
1 example_func -> highres (normally 6-9 DOF linear)
2 highres -> standard (normally 12 DOF linear)

The more advanced usage in question here is the three-stage:
1 example_func -> initial_highres (typically 3 or 6 DOF linear)
2 initial_highres -> highres (typically 6-9 DOF linear)
3 highres -> standard (typically 12 DOF linear)

We find that in both cases, using the subject-specific structural to
help the registration is a GOOD THING (e.g., see brief mention and
investigation of this in our NI variability paper). In all cases the
transforms are indeed concatenated mathematically, avoiding repeated
interpolation of the data.

We don't generally find that using a low-res/session-specific T1 as
the initial_highres is particularly useful. The main use is when the
FMRI data is just a few slices, and initial_highres is a single EPI
of the same specification, but covering the whole head.

The latest version of FEAT also includes the ability to unwarp the
EPI data using PRELUDE+FUGUE fieldmap unwarping: this is applied to
the EPI data before any registration begins, and can be really useful.

FEAT doesn't currently use nonlinear registration (apart from the
unwarping mentioned above). We are still evaluating the stability of
this....watch this space. What we are fairly sure about at this point
is that applying nonlinear registration to EPI data (as opposed to
the structural) is REALLY badly conditioned.

For other details on registration inside FEAT, see the FEAT manual:
    http://www.fmrib.ox.ac.uk/fsl/feat5/detail.html#reg
and also the relevant lecture from the FSL course:
    http://www.fmrib.ox.ac.uk/fslcourse/lectures/flirt_fugue/
flirt_fugue_slides.pdf

Cheers, Steve.

------------------------------------------------------------------------
---
Stephen M. Smith, Professor of Biomedical Engineering
Associate Director, Oxford University FMRIB Centre

FMRIB, JR Hospital, Headington, Oxford OX3 9DU, UK
+44 (0) 1865 222726 (fax 222717)
[log in to unmask] http://www.fmrib.ox.ac.uk/~steve
------------------------------------------------------------------------
---






On 21 Sep 2006, at 10:25, Ashburner John (PSYCHOLOGY) wrote:

> Steve, if you're reading this could you comment? Feel free to do some
> FSL sales pitch.
>
> I'm guessing that the low quality T1 has the same (phase encode
> direction) distortions as the EPI data, and that the additional
> step is
> in order to correct some of these distortions. It is easier to
> obtain a
> more accurate registration if the relationship between the intensities
> in one image are simply related to the intensities of the other - so
> nonlinear matching a T1 weighted to another T1 weighted image is
> easier
> than matching a T2* weighted to a T1.
>
> If the transformation is indeed a nonlinear one, then there is no easy
> way of doing this within SPM. If it is a rigid-body, then the
> Coregister button should do a reasonable job. Coregistration of
> the low
> quality T1 and the EPI may not be necessary if the images were
> acquired
> in the same session and there was no subject motion.
>
> Best regards,
> -John
>
>
> I have a question. I have seen papers and spoken with people using
> FSL,
> who do the normalization process in several steps. First, they
> coregister
> the low-quality T1 image (that is taken at the same time and in the
> same
> space as the functional data, and thus will coregister much better) to
> the
> functional image. Next, they determine the paramaters of the non-
> linear
> transformation from the low-quality T1 to the high-quality T1 (eg
> MPRAGE)
> and from the MPRAGE to the standard-space template. They then
> multiply
> those two transformation matrices (low quality T1 -> MPRAGE ->
> template)
> and
> apply the parameters to the functional images in order to normalize
> them
> to
> standard space. Hence, my question is: how would I do this in SPM? I
> can
> do each transformation and apply the parameters separately, but
> warping
> the
> functional data twice will create more opportunities for the data
> to be
> mishandled; I would prefer a single warp with the combined parameters.
> Thanks for the help!
>
> Daniel Simmonds
> Developmental Cognitive Neurology
> Kennedy Krieger Institute
> [log in to unmask]

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