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

SPM September 2012

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: the problem of mapping VBM results to native space

From:

"Kong, Li" <[log in to unmask]>

Reply-To:

Kong, Li

Date:

Wed, 19 Sep 2012 16:42:16 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Hi Gabor,



Thanks for your idea!



You are right!  I just segment raw image directly and write *_seg_inv_sn.mat to my cluster. Warped cluster locates in the right position of the raw image. Thanks again!





The cluster is got from normal VBM analysis in SPM8. I run VBM with defaut setting and did statistical analysis for smoothed GM. However, I did not got any *_seg_inv_sn.mat files (Even I changed the setting of "Deformation Fields" in VBM Batch Editor into "Template--> Image (Inverse)", I still can't get *_seg_inv_sn.mat ). So rerun my subjects step by step to get the *_seg_inv_sn.mat files.



So I think this cluster is no problem.  Is it possible to get *_seg_nv_sn.mat files in VBM analysis??



Thanks for your help!



Regards



Li







________________________________

From: "Graf Öderland" [[log in to unmask]]

Sent: Wednesday, September 19, 2012 5:40 PM

To: Kong, Li

Cc: [log in to unmask]; [log in to unmask]

Subject: Re: RE: the problem of mapping VBM results to native space



Hello Li,





the normalization part is included in segmentation (for details, see Ashburner & Friston, 2005, Unified segmentation), so no prior normalization step is needed for your purpose. Based on the naming of the files and your description it seems you accidentally normalized the structural volume (getting a subject_sn.mat and a wsubject.img), and then entered the wsubject.img into segmentation, thus getting wsubject_seg_sn.mat and wsubject_seg_inv_sn.mat



Thus these parameters are the "normalization" parameters for an already normalized version of your structural volume. Therefore the back-projected cluster (using w*_seg_inv_sn.mat) will not match the structural volume s*.img of course, but it should go well with the normalized version ws*.img.



So just give a try and segment the subject.img, not the wsubject.img. You should then get subject_seg_sn.mat and subject_seg_inv_sn.mat (without the "w"), and this *inv*.mat should result in a nice back-projection from MNI space to subject space.





I wonder where you got the cluster from though. Is it from some analysis of your segmented structural volumes? This would probably mean that you have to define the clusters again based on the correct segmentation and up-dated analysis.





Best,



Gabor







-------- Original-Nachricht --------

Datum: Wed, 19 Sep 2012 13:41:51 +0000

Von: "Kong, Li" <[log in to unmask]><https://service.gmx.net/de/cgi/g.fcgi/mail/new?CUSTOMERNO=40619594&t=de424934924.1348066691.e9fc8b62&to=%26lt%3BLi.Kong%40med.uni-heidelberg.de>

An: Gabor Oederland <[log in to unmask]><https://service.gmx.net/de/cgi/g.fcgi/mail/new?CUSTOMERNO=40619594&t=de424934924.1348066691.e9fc8b62&to=%26lt%3Boederland%40gmx.ch>

CC: "John Ashburner ‎[[log in to unmask]]‎"<https://service.gmx.net/de/cgi/g.fcgi/mail/new?CUSTOMERNO=40619594&t=de424934924.1348066691.e9fc8b62&to=%26lrm%3B%5Bjashburner%40gmail.com> <[log in to unmask]><https://service.gmx.net/de/cgi/g.fcgi/mail/new?CUSTOMERNO=40619594&t=de424934924.1348066691.e9fc8b62&to=%26lt%3Bjashburner%40gmail.com>, "[log in to unmask]"<https://service.gmx.net/de/cgi/g.fcgi/mail/new?CUSTOMERNO=40619594&t=de424934924.1348066691.e9fc8b62&to=%26quot%3BSPM%40jiscmail.ac.uk> <[log in to unmask]><https://service.gmx.net/de/cgi/g.fcgi/mail/new?CUSTOMERNO=40619594&t=de424934924.1348066691.e9fc8b62&to=%26lt%3BSPM%40jiscmail.ac.uk>

Betreff: RE: the problem of mapping VBM results to native space





Hi John and Gabor,



Thanks for ideas!



Although I haven't got the right method to transform my mask from MNI space to native space, I think the "wsubject_seg_inv_sn.mat" I got is not right file. If this "wsubject_seg_inv_sn.mat" can bring the mask from MNI to native space, the file "wsubject_seg_sn.mat" should be able to bring my raw image "subject.img" to MNI space. I tested with spm_write_sn ('subject.img', 'wsubject_seg_sn.mat') and I expected warped subject (wsubject.img) should be in MNI space and similar to the "wsubject.img" I got from "Normalization". But it isn't.



So I am afraid I got this "wsubject_seg_inv_sn.mat" in wrong way. I first did VBM analysis with defaut setting and I did not got any *_seg_inv_sn.mat file. Therefore, I planned to re-run my subjects step by step. I first copied one subject to a folder for testing and did normalization and segmentation for this subject (first normalization and then segmentation). After normalization, I got one mat file "subject_sn.mat". "wsubject_seg_sn.mat" and "wsubject_seg_inv_sn.mat" were got from segmentation. Do you think this is the right way getting *_seg_inv_sn.mat???





My cluster.img locates in precentral gyrus. The peak of the cluster in in high GM density.The qualities of raw image, normalized and segmented image are OK, not bad.



I will enclose them (subject.img is the raw image; wsubject.img is warped image by normalization; L_precentral_t.img is the cluster from spm_T.img).



Thanks!



Li



















________________________________________

From: Gabor Oederland [[log in to unmask]]<https://service.gmx.net/de/cgi/g.fcgi/mail/new?CUSTOMERNO=40619594&t=de424934924.1348066691.e9fc8b62&to=oederland%40gmx.ch>

Sent: Wednesday, September 19, 2012 2:15 PM

To: Kong, Li

Subject: Re: the problem of mapping VBM results to native space



Hello Li,





maybe you could attach some pictures to get an idea of your data? As John said, one option would be that your structural volume was reoriented after segmentation or the segmentation/normalization has a poor quality.



Something different which came to my mind: did you smooth your segmented data? Sometimes you get clusters where the probability of GM is rather low. So, where is the cluster located in your VBM data? Is the peak of the cluster at some position with high GM volume/density or somewhere with rather low GM volume/density? In the latter case, it might actually be that when back-projected to the original volume (no smoothing), the cluster seems to be lying outside the brain (because it stems from smoothed data). Dunno, just another idea :-)





Best,



Gabor



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