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  March 2017

SPM March 2017

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Fw: CAT/SPM Dartel registration pipeline-resend

From:

MRI More <[log in to unmask]>

Reply-To:

MRI More <[log in to unmask]>

Date:

Tue, 21 Mar 2017 13:54:40 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (17 lines)

Dear Robin,

Regarding your last question, 'Normalise to MNI space' adds an affine component, while 'Population to ICBM Registration' reflects a non-linear registration. The second difference is that 'Normalise to MNI space' refers to MNI space as represented in the TPM.nii, which is very close to the asymmetric version of the MNI ICBM 152 non-linear 6th Generation atlas (its symmetric version is available at http://nist.mni.mcgill.ca/?p=858 ), whereas the non-linear registration is conducted onto (a smoothed version of) the ICBM 152 Nonlinear atlas version 2009 http://nist.mni.mcgill.ca/?p=904 . Funnily, without modifying the scripts the target space is coupled with the type of registration, although these two aspects are unrelated in terms of content.

Whether to prefer the 6th gen or the 2009 ICBM version is one issue. The 2009 version is certainly the newer (and latest) official version, created with a more complex registration technique. However, it has not become a common target space so far; SPM and FSL continue relying on an asymmetric version of the 6th gen version as represented e.g. by the TPM.nii in SPM. I would stick with the 6th gen space as long as the 2009 space has not become a common space, as it eases comparisons with other studies.

The other issue is complexity of the registration. Whether an affine registration onto a template is sufficient to bring your data in good alignment depends on your data and your personal demands. It might work well on a global level, but on a local level, there might still be rather strong spatial deviations from the template.

For your ROI analyses you should ensure that the space of the atlas corresponds well to the space of your final data, be it 6th gen, 2009 or another MNI version. Therefore I would go with an atlas in which the raw structural volumes are available, so that you can re-segment them and bring them into the corresponding space. Some of those have been created several years ago, relying on older MNI versions, so they might be unnecessarily imprecise and in any case, differ from "your" space. One option would be the Hammersmith n30r83 atlas http://brain-development.org/brain-atlases/ , another would be the LPBA40 http://loni.usc.edu/atlases/Atlas_Detail.php?atlas_id=12 .
1) Working with the n30r83 should be very easy, just segment the files, determine the flow fields necessary to warp onto your template (or template plus additional transformation into "MNI" or "ICBM"), apply these onto the individual label images, either create probabilistic maps for the relevant regions or go with an MPM (can be constructed with Imcalc, select the 30 normalised label images and go with mod(X) ).
2) It would be more complicated with the LPBA40, as the volumes with the individual labels have been reoriented into what they call "delination space" (the file is called "LPBA40 Subjects Delineation Space: MRI and label files in delineation space"). Within this space they only provide structural volumes that have already been skull-stripped, with cerebellum and brainstem removed. The raw structural volumes are stored in "native space" still ("LPBA40 Subjects Native Space: MRI data and brain masks in native space"), with necessary reorientation parameters from native to delination space stored in .air format, for which you will probably need some of the LONI software. Maybe it is sufficient to coregister the skull-stripped structure in native space onto the skull-stripped cerebrum-only structure in delination space and apply this onto the raw structural volume. Then segment those structures, apply the deformations and so on like in 1)
For atlases with unavailable raw volumes but known preprocessing space one could at least try to warp from the corresponding template volume into your space. E.g. if a certain atlas represents 6th gen MNI space and you want it in 2009 MNI space you could segment the 6th gen T1 template (or take GM, WM, ... files if available, this is going to depend on the templates) and then go with a 'Population to ICBM Registration'. With spm_norm_population.m you could warp into other spaces as well, you just have to replace the icbm152.nii in line 13 by some other volume.

Hope this helps

Helmut

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