When writing bvec files, the vectors all need to be normalized to unit length. For this format, the magnitude of the bval is encoded separately from the directions. (in the NRRD files they are combined).
Could you make this change quickly?
Thanks,
Hans
hi martin and hans,
indeed the place where the issue is in the conversion. i would like to note that even with single b-values, scanners cannot always hit the right target, so when q is estimated from the B matrix, you can often see values that are around the target but not exactly equal to it.
so far a bmax of 1000, you might see values as seen in this scan: 995, 974, etc.,. depending on the gradient direction and the gradients that came before it.
martin: there is no standard. but i think if we wrote out fsl style, then doing bvecs as unit norm and bvals reflecting magnitude makes sense.
cheers,
satra
On Wed, Jan 22, 2014 at 11:12 AM, Johnson, Hans J hans-johnson@uiowa.edu wrote:
Martin’s comments are a good guess that it is a bug in DWIConvert for nrrd files.
It should be a very easy fix. We have always been working with single b-value DWI’s so we probably missed the norming step.
Hans
From: Martin Styner martin_styner@me.com
Date: Wednesday, January 22, 2014 at 10:08 AM
To: Satrajit Ghosh satra@mit.edu
Cc: Francois Budin francois.budin@gmail.com, Hans Johnson hans.j.johnson@gmail.com, Kent Williams norman-k-williams@uiowa.edu
Subject: Re: vector norms from DTIPrep
Hi Satra
Not 100% where the problem is, but likely in NRRD to FSL conversion. In NRRD, the bvecs are NOT unit norm, but rather the norm scales the single b-value recorded in the header. For FSL, you have a bval file with different bvalues per DWI (different to NRRD), so my expectation is an imperfect conversion from NRRD to FSL, where all the bvals are the same and the bvecs scale the ovals (rather than all the bvals should be slightly different and the bvecs should be unit norm).
If the unit norm requirement on the bvecs a “standard” for the nifti DWI format, or does FSL simply assume so?
Martin
Martin Styner, PhD. MS ETH
Associate Professor
Neuro Image Analysis and Research Lab
Carolina Institute of Developmental Disabilities
Departments of Psychiatry and Computer Science
CB 7160, University of North Carolina at Chapel Hill
Chapel Hill, NC 27599-7160
Cell: 919 260 6674
Fax: 919 962 1799
On Jan 22, 2014, at 11:01 AM, Satrajit Ghosh satra@mit.edu wrote:
update:
the norm of the bvecs are representing the percentage of bmax, i.e. the bvals. i think if we are writing out bvecs and bvals, the bvecs should be unit norm, no?
cheers,
satra
On Wed, Jan 22, 2014 at 10:48 AM, Satrajit Ghosh satra@mit.edu wrote:
hi folks,
i'm seeing the following from an older version of DTIprep.
ps. i'm trying to compile the latest - running into some qt issues - but that's my problem.
Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you.
Kent,
When writing bvec files, the vectors all need to be normalized to unit length. For this format, the magnitude of the bval is encoded separately from the directions. (in the NRRD files they are combined).
Could you make this change quickly?
Thanks, Hans
hi martin and hans,
indeed the place where the issue is in the conversion. i would like to note that even with single b-values, scanners cannot always hit the right target, so when q is estimated from the B matrix, you can often see values that are around the target but not exactly equal to it.
so far a bmax of 1000, you might see values as seen in this scan: 995, 974, etc.,. depending on the gradient direction and the gradients that came before it.
martin: there is no standard. but i think if we wrote out fsl style, then doing bvecs as unit norm and bvals reflecting magnitude makes sense.
cheers,
satra
On Wed, Jan 22, 2014 at 11:12 AM, Johnson, Hans J hans-johnson@uiowa.edu wrote: Martin’s comments are a good guess that it is a bug in DWIConvert for nrrd files.
It should be a very easy fix. We have always been working with single b-value DWI’s so we probably missed the norming step.
Hans
From: Martin Styner martin_styner@me.com Date: Wednesday, January 22, 2014 at 10:08 AM To: Satrajit Ghosh satra@mit.edu Cc: Francois Budin francois.budin@gmail.com, Hans Johnson hans.j.johnson@gmail.com, Kent Williams norman-k-williams@uiowa.edu
Subject: Re: vector norms from DTIPrep
Hi Satra
Not 100% where the problem is, but likely in NRRD to FSL conversion. In NRRD, the bvecs are NOT unit norm, but rather the norm scales the single b-value recorded in the header. For FSL, you have a bval file with different bvalues per DWI (different to NRRD), so my expectation is an imperfect conversion from NRRD to FSL, where all the bvals are the same and the bvecs scale the ovals (rather than all the bvals should be slightly different and the bvecs should be unit norm).
If the unit norm requirement on the bvecs a “standard” for the nifti DWI format, or does FSL simply assume so?
Martin
Martin Styner, PhD. MS ETH Associate Professor Neuro Image Analysis and Research Lab Carolina Institute of Developmental Disabilities Departments of Psychiatry and Computer Science CB 7160, University of North Carolina at Chapel Hill Chapel Hill, NC 27599-7160 Cell: 919 260 6674 Fax: 919 962 1799
On Jan 22, 2014, at 11:01 AM, Satrajit Ghosh satra@mit.edu wrote:
update:
the norm of the bvecs are representing the percentage of bmax, i.e. the bvals. i think if we are writing out bvecs and bvals, the bvecs should be unit norm, no?
cheers,
satra
On Wed, Jan 22, 2014 at 10:48 AM, Satrajit Ghosh satra@mit.edu wrote: hi folks,
i'm seeing the following from an older version of DTIprep.
as you can see many of the vector norms are not that close to 1 and is therefore throwing off some tools i am using.
just checking if this is something you have come across and fixed in more recent versions.
processing route: dicoms -> nrrd -> dtiprep -> fsl
cheers,
satra
ps. i'm trying to compile the latest - running into some qt issues - but that's my problem.
Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you.