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

FSL November 2009

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Brain Space, etc.

From:

Mark Jenkinson <[log in to unmask]>

Reply-To:

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

Date:

Mon, 30 Nov 2009 08:24:23 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (133 lines)

Hello,

> 1.  To follow-up on "spaces," how does one know the appropriate  
> display range in FSLview for the different images?

Look at the intensities that are contained in the image.  Either click
around different voxels in FSLView and note the values in the
"intensity" box (near the coordinate displays) or use a tool like
"fslstats" with the -r (or -R) option.  When you have a feeling for
the range of intensity values, just set the display range (min and max)
in FSLView to cover this range (and not much more).

>
> 2.  To follow up on the registration --
>
> 	a.  Is it possible to register a FIRST hippcampus (already  
> segmented & boundary corrected) to standard space?
> 	e.g.,
>
> 	flirt -in [FIRST hippocampus; segmented & boundary corrected] -ref  
> [MNI152_T1_2mm] -out [name] ?

You should not do this.  You should only register images that look
like each other (e.g. the image of a whole brain and another image
of a whole brain, not of one isolated structure).  However, if you have
run FIRST then the registration has already been done and saved
in a file called something like *_to_std_sub.mat
You can *apply* this transformation (the result of a registration) to
any image in the original space using the -applyxfm flag in FLIRT.

> 	What is the appropriate display range for this image?

For a labeled image it will depend on the structure with the maximum
label number.  Typically if you set the range to be 0 to 40 then you
should see things fine.  But use the strategy I describe above to know
for sure.

> 	b.  Or must one perform the flirt registration to standard space  
> from the raw structural image with no brain extraction?  And then  
> use FIRST to segment the desired hippocampus?

If you use run_first_all then this is all done for you.  And yes, it  
is recommended
to use non-brain-extracted images with this.

All the best,
	Mark



>
> Thank you.  Very much.
>
>
> On Sat, Nov 28, 2009 at 3:35 PM, Mark Jenkinson  
> <[log in to unmask]> wrote:
> Hello,
>
> There is no real reference about "spaces" besides the documentation.
> I'll try to answer your questions:
>
> 1 - Outputs are in different spaces as the originally acquired images
>        are in different spaces.  That is, the Field Of View (FOV) and
>        resolution are different for the functional, structural and
>        standard/template images.  We try to keep things in the most
>        appropriate space, partly because moving between spaces
>        involves registration and resampling steps which can be  
> inaccurate
>        and the interpolation (in the resampling) will degrade the  
> image
>        quality by some amount.
>
> 2 - As examples:
>        Functional images might be 64x64x40 voxels with 3x3x4mm  
> resolution
>        Structural images might be 256x256x200 voxels with 1x1x1mm  
> resolution
>        Our standard space template images are 91x109x91 voxels with  
> 2x2x2mm resolution
>
> 3 - The spaces correspond to your different acquisition images - so  
> just check
>        by comparison with your original images.
>
> For your registration I'm not sure what your [FIRST INPUT] image  
> is.  Is it a
> structural image with no brain extraction?  If so, then you should  
> not register
> to the avg152T1_brain but use the non-brain extracted version.   
> Also, we
> recommend sticking with the MNI152 naming, so MNI152_T1_2mm would
> be the appropriate image in this case.  I am not sure what you mean by
> "appropriate brain region".  Also, check that the display range is  
> set appropriately
> in FSLView, as having this range set badly (which sometimes happens
> with the default settings) could make the whole image look white.
>
> All the best,
>        Mark
>
>
>
> On 28 Nov 2009, at 17:10, ACE . wrote:
>
> Hello.
>
> Could you please point me to a resource about different "brain  
> space" options? (e.g., high resolution space; standard space; native  
> space?)
>
> I have read the registration information on the FSL website, but I  
> have additional questions such as the following:
>
> 1.  Why are different FSL outputs in different spaces?
>
> 2.  Could you give me an example of a FSL image in each "space?"
>
> 3.  What is the best way to determine an image's "space?"  Is there  
> a list of which voxel dimensions signify which "space?"
>
> To register a FIRST brain area (with boundary correction) to  
> standard space -- I tried the following command:
>
>  flirt -in [FIRST INPUT] -ref avg152T1_brain -out [name]
>
> But I do not see the appropriate brain region in FSLview when I open  
> the output.  I see "white" throughout the entire brain.  Any thoughts?
>
> THANK YOU.
>
>
>

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