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  July 2012

SPM July 2012

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: VBM8 with a developmental sample: normalising to MNI space.

From:

Christian Gaser <[log in to unmask]>

Reply-To:

Christian Gaser <[log in to unmask]>

Date:

Fri, 20 Jul 2012 16:41:52 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (53 lines)

Dear Zoe,

On Tue, 17 Jul 2012 11:56:32 +0000, Hyde, Zoe <[log in to unmask]> wrote:

>Dear Christian and Marko,
>
>Thanks very much to both of you for your replies to our previous question.
>
>Christian, I hope you don't mind a couple of follow-up questions to clarify the pipeline, especially as yours and Marko's replies differed regarding MNI space. First, we were surprised to find (if we're reading your response correctly) that choosing 'DARTEL export - affine' for the initial segmentation using 'Estimate and Write' in VBM8 means that the segments are written in MNI space. Could you confirm whether this is indeed the case? The instructions and the manual don't mention this as a way of normalising into MNI space, so we would like to be absolutely sure before proceeding. Is this due to the fact that we used the default DARTEL template which is in MNI space as mentioned in the VBM8 manual (p.29)? And does it not make a difference that we have used our own custom TPMs?
Affine normalization also includes scaling to MNI space, that is separately applied in the Dartel toolbox. Thus, if you use the "export affine" option to write segmentations you don't need to additionally transform your Dartel results to MNI space. Furthermore, the Dartel template provided with VBM8 is in MNI space (as the name implies).
The custom TPM image is only used for the initial spatial normalization, but also influences the estimation of the affine transformation and therefore the exported affine transformed segmentations. Thus, it is especially recommended to use a customized TPM for children (via the Template-O-Matic toolbox). 

>
>Secondly, during this step, does it matter whether we choose the low dimensional or high dimensional option under 'Spatial normalization'. Marko's reply suggested that it wouldn't matter since we aren't actually normalising the data at this point in the pipeline, and that we should therefore use the low dimensional option for speed. But if the affine transformation is also normalising to MNI space, then perhaps it does matter after all.
The exported affine transformed segmentations are unaffected of the subsequent non-linear normalization. Thus, you can use the low-dimensional normalization to save time.
>
>Presumably after this step, we then use the 'DARTEL export - affine' segments to create our DARTEL template as we mentioned in our previous post. But previously we had thought the template would be written in study-specific space. Are you in fact saying that the template will be in MNI space?
As I mentioned above, affine transformation also scales images to MNI space...

>
>Finally, as a final step you suggest using 'the Dartel toolbox to apply the warpings with modulation but without additional MNI normalization.' Would this be using the 'Normalise to MNI space' option in DARTEL? If so, did you mean that we do not need to put the template in at this stage because the flow fields will already be what is required to transform our images into MNI space? And are you saying that once we've used the VBM8 toolbox for initial segmentation, that we then don't use it again during pre-processing? Our original plan was the following: After having created our DARTEL template, we were going to segment our original T1 scans using the Estimate and Write from VBM8 with our customized tissue probability maps and the customised DARTEL template. However, based on your email it seems that if VBM8 was used in the initial segmentation (to generate the DARTEL export - affine), there is no additional benefit of using it thereafter. Our rationale for using VBM8 at the final stage was due the additional cleaning options offered by VBM8 (i.e. MAP, PVE, SANLM and MRF) and the possibility of getting the normalised bias corrected T1 scan to create a mean T1 to overlay our results.
The flow fields can be applied to you affine transformed segmentations. In this case you can use the potential benefits of the VBM8 toolbox.

I hope that it's clearer now...

Best,

Christian

>
>Thanks very much in advance for your advice.
>
>Best wishes,
>
>Zoe
>
>Zoe Hyde
>Research Assistant
>
>Developmental Risk and Resilience Unit
>Clinical, Educational and Health Psychology
>Division of Psychology and Language Sciences
>
>University College London
>26 Bedford Way
>London WC1H 0AP
>
>[log in to unmask]<mailto:[log in to unmask]>
>Tel: +44(0)20 7679 5322<tel:%2B44%280%2920%207679%205322> (internal: 25322)
>http://www.drru-research.org/
>
>

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