Actually, just uploading the data for Tim would be easiest.
Peace,
Matt.
-----Original Message-----
From: FSL - FMRIB's Software Library [mailto:[log in to unmask]] On Behalf
Of Roderick McColl
Sent: Wednesday, August 22, 2007 12:41 PM
To: [log in to unmask]
Subject: Re: [FSL] FSLView 3.0 and DTI Data: Request
I tried to send screenshots yesterday but they exceeded the 50k limit so
were rejected.
I reorient my data to make sure it is LAS, but perhaps in truth its not?
-roddy
>>> Matt Glasser <[log in to unmask]> 8/22/2007 11:29 AM >>>
Is your data neurologically oriented? FSLView's behavior changed with
regard to neurologically oriented data. Also could you should some
screenshots to illustrate your problems?
Peace,
Matt.
-----Original Message-----
From: FSL - FMRIB's Software Library [mailto:[log in to unmask]] On Behalf
Of Roderick McColl
Sent: Wednesday, August 22, 2007 12:24 PM
To: [log in to unmask]
Subject: Re: [FSL] FSLView 3.0 and DTI Data: Request
Two other issues related to the new FSLVIEW, at least as it impacts my data.
In comparison to the FSLVIEW in FSL 3.3, when I look at DTI data using the
FSLVIEW in FSL 4.0
using V1 and FA, the axial and coronal images are displaced to the left of
the display box (to the right of the head) by about 40 per cent of the FOV,
and the lines don't "look right". Does this reflect some change in the
detection of orientation between the two versions?
-roddy
>>> Matt Glasser <[log in to unmask]> 8/21/2007 9:50 AM >>>
Hi,
The new version of FSLView has the annoying habit of taking the cal_max from
the NIFTI header of the FA and using it when displaying the FA modulated
color map no matter what the Max is set to inside FSLView. This means that
if a high cal_max value is set somewhere in the preprocessing chain, you
can't display an FA modulated color map in FSLView without manually editing
the header to change cal_max to 1. It would be better if FSLView used the
value in the Max box or assumed all FAs had a max of one.
Thanks,
Matt.
|