JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for FSL Archives


FSL Archives

FSL Archives


FSL@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

FSL Home

FSL Home

FSL  July 2007

FSL July 2007

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: coregistration of FA maps

From:

Steve Smith <[log in to unmask]>

Reply-To:

FSL - FMRIB's Software Library <[log in to unmask]>

Date:

Fri, 27 Jul 2007 09:11:50 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (141 lines)

Hi,

On 26 Jul 2007, at 19:42, Ryan Muetzel wrote:

> Hello,
> This is a question similar to post# 010866, from April 2007 (text  
> pasted below).
>
> We have collected cross-sectional and longitudinal DTI data and  
> would like to coregister the data.
>
> In the post below, from what I can tell, it was recommended that  
> the half xfm's be used with flirt. In the siena_flirt src code, it  
> seems things are done slightly different than that(average the full  
> xfm's first, then take the halfway's). Would you recommend one way  
> over the other for DTI data (substituting flirt for the pairreg  
> steps in siena_flirt, I'm guessing)?
>
> Do you recommend starting with raw data (say the b=0, and apply the  
> xfm's to the 4D data), or starting with FA maps?

If you are just trying to compare a single subject's two timepoint FA  
images then you can just take the FA images and register them into  
their halfway point. (On the other hand, if this is to be part of a  
multi-subject longitudinal analysis in TBSS I wouldn't worry about  
this, just feed everything into TBSS as normal). However, siena_flirt  
isn't quite appropriate as it also uses the skull images as well as  
the brain images - you will need to edit this and simplify it to only  
use the FA images.

> I have been working on coregistering two DTI scans, collected at  
> the same time-point. These scans have slightly different echo  
> spacings and thus slightly different susceptibility artifact. The  
> differences in susceptibility artifact seem to be causing  
> misalignments between two data sets. I get a similar registration  
> whether or not I unwarp the data with a fieldmap. I am able to get  
> considerably better registration if I:
>
> 1) apply the half xfm to the 4D data based on the b=0 images.
> 2) choose 1 b=0 image and apply eddy_correct to both 4D data sets  
> based on that single b=0
> 3) run fugue/dtifit/bedpost from here.
>
> Are there any major flaws to this method? The two DTI scans are  
> identical other than the echo spacing and number of directions.

That sounds ok, as long as you make sure in step 3 that each dataset  
is properly being aligned to the appropriate fieldmap for the unwarping.

Cheers.



>
> Any help/suggestions is much appreciated!!
>
> -Ryan
>
>
>
>
>
>
>
>
> Date:         Wed, 4 Apr 2007 12:22:21 +0200
> Reply-To:     FSL - FMRIB's Software Library <[log in to unmask]>
> Sender:       FSL - FMRIB's Software Library <[log in to unmask]>
> From:         Oliver Singer <[log in to unmask]>
> Subject:      Re: Coregistration of FA-maps
> In-Reply-To:   
> <[log in to unmask]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Dear Mark, thanks for your help concerning the realignment of the  
> FA-maps using the half-transformation matrices. Seems the best  
> option to me. However, I have some "technical" questions concerning  
> the way to do this: I ran FLIRT on the two FA-images. Using avscale  
> I get the matrices for forward and backward half transform as  
> follows: Forward half transform = 0.999691 -0.024777 -0.002129  
> 4.972743 0.024866 0.997103 0.071886 0.730804 0.000342 -0.071916  
> 0.997410 3.274879 0.000000 0.000000 0.000000 1.000000 Backward half  
> transform = 0.999691 0.024866 0.000342 -4.990497 -0.024777 0.997103  
> -0.071916 -0.369960 -0.002129 0.071885 0.997411 -3.308346 0.000000  
> 0.000000 0.000000 1.000000 My question now is how to apply these  
> matrices to receive the halfway-FA-images? Is it using the  
> convert_xfm option or the img2imgcoord option? Sorry for this  
> probably basic question..... Yours Oliver Mark Jenkinson schrieb: >  
> Hi, > > There are other interpolation schemes such as nearest  
> neighbour > or sinc, but they each have some disadvantages too, and  
> will > make one image qualitatively different from the other. The >  
> smoothing is inherent in trilinear interpolation, some rather >  
> ugly discontinuities occur with nearest neighbour and some >  
> ringing and/or variable smoothing can occur with sinc. > > An  
> alternative is to transform both images to a half-way > point, this  
> equalising the interpolation effects. This is > what is done in  
> SIENA, and you can do the same by extracting > the forward and  
> backward half-transformation matrices from > the output of  
> "avscale" as run on your original transformation > matrices. > >  
> That's what I would recommend. > > All the best, > Mark > > >
>>> Hi, >> You can change the interpolation scheme to nearest  
>>> neighbour. >>
> (Advanced options in the gui) >> >> Saad. >> >> >> On 2 Apr 2007,  
> at 14:28, Oliver Singer wrote: >> >> >>> Hi, >>> >>> I am trying to  
> realign FA-maps of one subject, who was scanned at >>> two  
> different time points. After running BET I am using FLIRT for >>>  
> realigning (rigid body transform, 6D OF) the B0 images (extracted  
> >>> from the DTI data set) of the second measurement to the B0  
> images of >>> the first measurement and as secondary images to  
> apply the >>> transform to I take the FA maps of the second  
> measurement. >>> The realignment works fine, but the FA-map of the  
> second
>>>> measuresment (the realigned one) was "smoothed" during the  
>>>> process. >>>
> Since the first FA-map was not processed, the two maps differ in  
> >>> terms of their "resolution / smootheness". >>> Is there a way  
> either to turn off the "smoothing" during the >>> realignment or to  
> smoothe the first FA-map (which was not >>> transformed) in a  
> similar way? (I do not want to realign all images >>> to a  
> "standard brain" due to gross pathology) >>> Any help is  
> appreciated, >>> >>> Yours , Oliver >>> >>  
> ---------------------------------------------------------------------- 
> -- >> --- >> Saad Jbabdi, >> Postdoctoral Research Assistant, >>  
> Oxford University FMRIB Centre >> >> FMRIB, JR Hospital,  
> Headington, Oxford OX3 9DU, UK >> +44 (0) 1865 222545 (fax 222717)  
> >> [log in to unmask] http://www.fmrib.ox.ac.uk/~saad >>  
> ---------------------------------------------------------------------- 
> -- >>


------------------------------------------------------------------------ 
---
Stephen M. Smith, Professor of Biomedical Engineering
Associate Director,  Oxford University FMRIB Centre

FMRIB, JR Hospital, Headington, Oxford  OX3 9DU, UK
+44 (0) 1865 222726  (fax 222717)
[log in to unmask]    http://www.fmrib.ox.ac.uk/~steve
------------------------------------------------------------------------ 
---

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


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