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

FSL February 2011

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: image orientation and img2imgcoord

From:

Mark Jenkinson <[log in to unmask]>

Reply-To:

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

Date:

Sun, 6 Feb 2011 20:44:17 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (66 lines)

Hi,

You don't have to worry about this within FSL - everything is taken
care of correctly.  The coordinates used in FSLView and tools like
img2imgcoord are completely consistent.  The FLIRT transforms
work internally with a mm coordinate system (not the voxels) and
so flip the handedness of the voxel coordinate system as needed.
However, the FLIRT internal coordinates are *not* the same as
the FSLView mm coordinates.

As for the resulting image after running FLIRT, it is the reference
image that determines the qform and sform, and consequently
the handedness.

So the big problem you have would be the method in your lab
that ignores the hdr information.  In this case you need to work
out what your software assumes and then make sure the images
that you use as input are in the correctly format.  Essentially, 
getting the reference volume in FLIRT setup with the right
information will do the trick.  You can also covert the handedness
of an image with the following commands (although I do not
generally recommend this, in exceptional circumstances like
this it can be useful):
  fslswapdim origim -x y z swappedim
  fslorient -swaporient swapeddim
Note that it is necessary to use both commands.
Also, this will not work if both the qform and sform codes
are both zero.  If that is the case then things are trickier and
the best thing is to use: fslorient -setsformcode
in order to set the sform code to a non-zero value and then
deal with it from then on (checking carefully the left-right
status, as the setting of the sform codes can alter the
left-right status).

I hope this fixes your problems.
All the best,
	Mark




On 5 Feb 2011, at 23:29, Yan wrote:

> Hi,
> 
> I really hope that someone can help me with this. I just cannot figure out the correct way to do it. I have some DTI data and I am trying to align them up to an white matter atlas. The data set (FA image) didn't have the same orientation with MNI152 (labeling is correct, but the orientation was 180 degree different), so I used "fslreorient2std" to reorient it with MNI152. After that, "fslhd" showed both qform_xorient and sform_xorient changed to "Left-to-Right" (Neurological orientation, it was Right-to-Left before). When I used "fslview" to see the volume, labeling was fine and x=0 is on the most right of the image (patient's left). 
> 
> Now the atlas (also an FA image) is an analyze image with radiological orientation. So I used some converter tool (Jimmy Chen's Nifti toolkit in Matlab) to convert it into a Nifti file. Then I also used "fsllreorient2std" to reorient it with MNI152. It actually didn't matter. The orientation and labeling was correct before this (I checked it with "fslview"). But this time, "fslhd" showed both qform_xorient and sform_xorient "Right-to-Left" (radiological). "fslview" showed x=0 on the most left of the image (patient's right).
> 
> Then I used "flirt" to register my DTI FA to this template FA and I got a transformation matrix.
> 
> Now I am starting to be confused:
> 
> 1. why did "fslreorient2std" change my data's orientation from LAS to RAS? Why not keep the same as MNI152, which is LAS?
> 
> 2. Does "Flirt" work properly in this situation with two nifti files of different orientation? What does this transformation matrix mean, to map an RAS image to an LAS image? What if I have a LAS image, can I apply this transformation matrix on it (it relates to the third question I have about the LAS fiber coordinates). 
> 
> 3. I actually assume Flirt will work properly. But then I had the fiber coordinates from TrackVis. They are in LAS (radiological), which means x=0 (in voxel) on the patient's right. I wanted to use "img2imgcoord" to convert those coordinates onto the atlas coordinate (in voxel) by applying the transformation matrix. But I don't know how "img2imgcoord" defines voxel dimension. Does voxel x=0 start at the left corner of the image (right of the patient) no matter what, or is it consistent with "fslview" that voxel x=0 is at the right corner of the image (patient's left)? Does it read the header information of the image (the reference image) to decide the definition?
> 
> 4. The next step I do is non-linear registration with the software in my lab. It only takes .img images without reading the .hdr file. So after "flirt", the resliced DTI FA image has the same orientation with the atlas FA (LAS). I was wondering how the resliced DTI data is stored in .img after "Flirt". Is it LAS then?
> 
> Sorry, the orientation really gives me  problems... However, it is very crucial for fiber alignment. I am trying to be very cautious here. So if anyone who can kindly answer my questions, I will deeply appreciate it! Thank you for your time and help!
> 
> Yan
> 

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