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: inverting the normalization parameters in spm5

From:

Volkmar Glauche <[log in to unmask]>

Reply-To:

Volkmar Glauche <[log in to unmask]>

Date:

Wed, 15 Mar 2006 22:34:12 +0100

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (141 lines)

Stefano,

I am afraid, no. In SPM5, segmentation involves the procedure previously
called "optimised VBM" and thus is able to create both transformations. In
general, segmentation in SPM5 seems to be superior to the old-style
normalisation method.

Volkmar

On Wed, 15 Mar 2006, Marenco, Stefano (NIH/NIMH) [E] wrote:

> Is it possible to automatically save the inverse normalization
> transformation matrix using the normalization button (rather than the
> segmentation button) in spm5?
>
> Stefano Marenco, MD
> GCAP, Clinical Brain Disorders Branch,
> NIMH
> 10 Center Drive, room 4S235
> Bethesda, MD 20892
> tel. (301) 435-8964
> fax. (301) 480-7795
> email: [log in to unmask]
>
>
> -----Original Message-----
> From: Volkmar Glauche [mailto:[log in to unmask]]
> Sent: Thursday, March 09, 2006 7:23 AM
> To: [log in to unmask]
> Subject: Re: [SPM] contrast coregistration to a (wfu_pickatlas) mask
>
> If you use SPM5s "segment" to create the normalisation parameters, you
> will also get the inverse parameter set which will map from MNI to
> individual coordinates. The only thing to to is then to "write
> normalised"
> the MNI space ROI using the *_inv_sn.mat file from each individual
> subject.
>
> On Wed, 8 Mar 2006, Joseph Maldjian wrote:
>
> > Kelly,
> >
> > The pickatlas generates ROIs in MNI space. If you want to use the
> > pickatlas ROIs in native space, you need to be able to apply an
> > appropriate transformation matrix defining MNI -> native space.
> > Although the information for this transformation exists in your
> > normalization sn.mat file combined with your coregistration
> > transformation matrix, SPM will not directly perform the reverse
> > normalization procedure. There has been code posted by John Ashburner
> > that allows you to compute the reverse normalization transformation
> that
> > takes into account any deformation fields in the normalization.
> > You would have to apply this "inverse" normalization matrix to the
> > pickatlas ROI, and then apply the inverse coregistration matrix from
> > your step 5 to the ROI.
> >
> > Sounds bad, but that's part of the price for trying to use native
> space
> > with normalized ROIs. Someone out there may already have some useful
> > code that does all this. We have a program that does the reverse
> > normalization based on only Affine transformations (ignores
> deformation
> > fields).
> >
> > Hope this helps
> >
> >
> ------------------------------------------------------------------------
> > ----------
> > Joseph A. Maldjian, MD
> > Professor, Dept. of Radiology and Biomedical Engineering
> > Director Advanced Neuroscience Imaging Research Core (ANSIR)
> > Wake Forest University School of Medicine
> > Office: 336 716-2815
> > fax: 336 716-2870
> > email: [log in to unmask]
> > website: www.ansir.wfubmc.edu/maldjian.htm
> > <http://www.ansir.wfubmc.edu/maldjian.htm>
> >
> ------------------------------------------------------------------------
> > ----------
> >
> >
> >
> > -----Original Message-----
> > From: SPM (Statistical Parametric Mapping)
> > [mailto:[log in to unmask]] On Behalf Of Kelly Diederen
> > Sent: Wednesday, March 08, 2006 8:51 AM
> > To: [log in to unmask]
> > Subject: [SPM] contrast coregistration to a (wfu_pickatlas) mask
> >
> >
> > Dear researchers,
> >
> > I analyzed my data using the following procedure:
> >
> > 1 realignment
> > 2 statistics
> > 3 estimation
> > 4 results
> > 5 coresgistration of the contrasts to the anatomical image
> > 6 normalization of the coregistered contrasts to the T1
> > template.
> >
> > I decided to normalize the contrasts at the end of the procedure
> > to enable myzelf to look both at the normalized and non-normalized
> data
> > without doing two separate analysis'.
> >
> > Next to this I made a mask with the WFU_pickatlas in order to
> > visualize the ROI's for further analysis. Since the pickatlas
> generates
> > normalized masks I can't use in the results section since my data
> aren't
> > normalized yet. Thats why I tried to coregister the masks with the
> > contrasts after step 6.
> > However this doesn't work, whichever way I tried it.
> > Is there a way to do this with the pickatlas without normalizing
> > the scans before the estimation (and without coregistration of the
> mask
> > with the functional scans before the estimation part)?
> >
> > Thank you in advance,
> >
> > Kelly Diederen
> >
> >
> >
> >
> >
>
>

--
Volkmar Glauche
-
Department of Neurology [log in to unmask]
Universitaetsklinikum Freiburg Phone 49(0)761-270-5331
Breisacher Str. 64 Fax 49(0)761-270-5416
79106 Freiburg

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