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  June 2009

SPM June 2009

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Point normalisation in DARTEL

From:

Joao Pereira <[log in to unmask]>

Reply-To:

[log in to unmask][log in to unmask]

Date:

Fri, 5 Jun 2009 12:46:35 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (133 lines)

Dear Prof Ashburner,

A while ago we had an email exchange (below) about how to extract the  
position of a point in a DARTEL-registered scan given its initial  
position in a T1 native scan.

After recently revising the method, I would like to clear one question  
that occurred to me: do the y_*.nii deformation fields only contain  
DARTEL related deformations? If such is the case, as DARTEL works "on  
top" of the unified segmentation, in order to extract the final  
locations in DARTEL space (from T1 scan positions) won't it be  
necessary to include the composition with the previous registration  
field from the unified segmentation?

I'm probably just missing something in the proposed method, but it  
would be great if you could clarify this.

Thank you very much!

Best,

Joao Pereira

--------- Previous thread ------------------------------
I forgot about this.  The procedure needs another step, which can be achieved
in one of two ways:

   	5.1. Using Deformations -> Composition
   		5.1.1 Inverse -> Composition -> Imported _sn.mat -> chose template 6 and
   base inverse on native space scan of each subject
   		5.1.2 DARTEL flow -> u_rc1* files for each subject + *"Forward"*
                 5.1.2 Identity, with the image to base it on being the
original scan.

This is similar to the steps described in Section 1.4 of the DARTEL guide,
except that the mapping from Template_6 to MNI space is from the inverse of
the transform contained in the _sn.mat, rather than a DARTEL deformation.


The other way would be to use the matrix information in the headers, but I
won't elaborate on this.

Best regards,
-John

On Wednesday 08 October 2008 19:42, Joao Pereira wrote:
> Dear Prof Ashburner,
>
> Thank you very much for your reply. Just one more thing:
>
> When I try to apply these steps in the reverse order you suggested, the
> output y* file has 91x109x91 dimensions, whereas I need the original
> dimensions for it to be usable. Should then 5.1.2 be:
>
> Inverse -> Composition -> DARTEL flow -> u_rc1* files + (and now I get lost
> given I already have an inverse) Backwards/Forward? + native space image to
> use as basis for inverse
>
> Please let me know if this is correct.
>
> Thank you once again!
>
> Joao
>
> -----Original Message-----
> From: John Ashburner [mailto:[log in to unmask]]
> Sent: 08 October 2008 16:07
> To: Joao Pereira; [log in to unmask]
> Subject: Re: [SPM] DARTEL - voxel normalisation
>
>
> Section 1.2.2 of the DARTEL guide describes how to generate a mapping from
> MNI
> space to Template_6.nii to individual subject.  What you are after is the
> inverse of this, which is a mapping from individual subject to
> Template_6.nii
> to MNI space.  You therefore need to swap some of the operations around:
>
>  	5.1. Using Deformations -> Composition
>  		5.1.1 Inverse -> Composition -> Imported _sn.mat -> chose template 6 and
>  base inverse on native space scan of each subject
>  		5.1.2 DARTEL flow -> u_rc1* files for each subject + *"Forward"*
>
> The rest seems fine.  This stuff can be a bit tricky to get your head
> around -
> but it gets easier with practice.
>
> Best regards,
> -John
>
> On Wednesday 08 October 2008 14:33, Joao Pereira wrote:
> > Hello,
> >
> > I've been trying to extract the normalised positions (after DARTEL) of
> > points placed in native space.
> >
> > I've come up with a methodology for this purpose (for each cohort) which
> > I would like you to comment on if possible:
> >
> > 1. Normalise all scans and extract mwc* files, as well as the *seg_sn.mat
> > file for each scan
> > 2. DARTEL Tools -> Initial import, using all seg_sn files and setting
>
> voxel
>
> > size at NaN
> > 3. Create Template using rc1* and rc2* files
> > 4. Affine transform the DARTEL template (#6) to MNI and extract the
>
> *sn.mat
>
> > file (I need my coordinates in MNI)
> >  -- (New bit starts here) --
> > 5. Estimate the deformation field from initial (native) scan to DARTEL
> > output by:
> > 	5.1. Using Deformations -> Composition
> > 		5.1.1 DARTEL flow -> u_rc1* files for each subject + *"Forward"*
> > 		5.1.2 Inverse -> Composition -> Imported _sn.mat -> chose template 6
> > and base inverse on native space scan of each subject
> > 6. Use y_* output to locate normalised position of native point (x,y,z)
> > by using f = nifti(y_*); norm_pos = squeeze(f.dat(x,y,z,:,:));
> >
> > Please let me know if this is sensible. Thank you all very much for your
> > help!
> >
> > Best,
> >
> > Joao Pereira


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

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