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

FSL March 2007

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Co-registering multi-subject dataset for input into randomise

From:

Steve Smith <[log in to unmask]>

Reply-To:

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

Date:

Wed, 14 Mar 2007 15:07:22 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (106 lines)

Hi Kelly,

On 13 Mar 2007, at 14:00, Kelly wrote:

> I have another question that I would love your opinion on.  I am
> analyzing perfusion data from a multi subject project.  First, I
> ran my raw images through Soren Christensen's Matlab "pgui" program
> that calculated CBF, CBV, MTT, k1,k2 and delay.  My next task was to
> co-register these images to the highest degree of freedom while
> keeping the integrity of the images. I have tried many different
> methods. I came to the conclusion that my best output so far was to:
>
> 1. Create a mean image of my perfusion dataset (2x2x4 dimensions) and
> flirt with 12dof to (2x2x2) MNI_152 brain
>
> 2. Register each image, using nreg, to the mean and flirted template
> image by using CC and -ds 80 then subdivide (so -ds 40) and then
> subdivide again (-ds 20)

I doubt this is optimal. Do you not have a structural image? The  
normal FEAT approach would be best, for example a 7DOF affine to the  
betted structural and then 12DOF from structural to standard space.

I would not use any nonlinear reg for the within-perfusion data - do  
you think you have wildly varying distortions for example? Does  
mcflirt not work well for within-session analysis, and flirt (as  
above) for between session (fixed effects) analysis?

In general I would think you should be using FEAT for all of this....?

> My ultimate goal is to use randomise for the analysis.  But I am not
> sure what the best input is going to be for randomise.  I have
> uploaded (using the link you sent me) the 4-D dataset after step 2
> above was completed. The code is 310438. Would you have a look and  
> give
> me your thoughts?
>
> They still look quite different to me and when I ran this
> through randomise the first time I didn't really get any significant
> results; however, the project is looking at differences pre and post
> altitude.  I know that CBF should go up at altitude; so I know there
> should be a difference in this dataset.  (Paired t-test)
>
> randomise -i 4D_CBF_pre_post -o 4D_CBF_20 -v 10 -V -m min_4D.nii.gz -d
> 21pair.mat -t 21pair.con -c 3
>
> I used the minimum image of the dataset to mask the 4-D image so that
> they all have the same dimensions.
>
> Because the mean image is inherently smoothed and has less
> information, I have recently begun running the CBF image registration
> all to all using tbss_2_reg hoping that this might give me a more
> accurate result...but this takes a while=)
>
> I have read the paper on how tbss works for the FA data.  I think this
> methodology is brilliant and I am planning to use it for my diffusion
> dataset that corresponds with the perfusion data that I discussed
> above.  I understand why it works so well with the white matter
> tracts.
>
> I am a beginning masters student and have only recently begun to
> educate myself on MR imaging, so my knowledge is very limited in this
> subject.  This may be a stupid question but Have you ever explored
> trying to make a similar program that fine tunes the coregistration of
> perfusion (like CBF or MTT) data?  I understand that the real values
> that you find in FA data are not present in the perfusion data...but
> maybe normalizing to a certain value set depending on max and min or
> time would provide this?...

I would think generally that perfusion analysis would follow the same  
general ideas as FMRI analysis - along with various optional ways of  
solving correspondence such as using cortical modelling (e.g.  
FreeSurfer) etc. - do you think that perfusion should be treated  
fundamentally differently from FMRI?

Cheers, Steve.


>
> Thanks so much for your help.  I really am enjoying learning FSL and
> how robust a package it is!  I look forward to your reply.
>
> Kelly Brown
> University of Colorado HSC
> Altitude Research Center
>
>
> ______________________________________________________________________ 
> __
> Interested in getting caught up on today's news?
> Click here to checkout USA TODAY Headlines.
> http://track.juno.com/s/lc?s=198954&u=http://www.usatoday.com/news/ 
> front.htm?csp=24


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