Dear Suzanna,
Thanks a lot for your answer.
you are right .par .rec is this philips intern format. And that's true
that actually you can get the bvecs from the scanner but because of the angulation(I
hope that's the right word) the values are always slightly different
(as I understood just re-calculated in the patients plain).
In some later versions of the par the values of the bvecs are in it,
in mine not...
ok what about normalization of bvecs, is it alway needed? What for? Or
ist only a par/rec thing.
I thank you very much!
Sergiu
the
> Hi Sergiu,
> Are you using a Philips scanner for the par/rec files? If so you can
> get the bvecs from the scanner. I don't know if they're encoded in
> the par/rec files. You b values will relate to your images, so if
> you had 32 directions at b=10000 and 2 b=0 images, this forms your
> bvals file (obviously the order needs to match the bvecs). Also, as
> a reminder, don't forget to normalise your bvecs, it tells you how to
> do this in the FAQs on the FSL website.
> Suzanna
> On 28 Feb 2008, at 18:13, S. Groppa wrote:
>> Dear list,
>>
>> I apologize for this in a way repeated question but I did't find in
>> the list a complete answer for it.
>>
>> I've just got some *.par *.rec 's data - and tried to convert it to
>> fsl_nifti
>> which functioned quite good (through dcm2nii) - but
>>
>> without getting the bvals and bvec??
>>
>> with the error message par 4.1 not yet fully supported.
>>
>> I tried r2agui with no success.
>> Any other ideas of becoming the bvals and bvecs?
>>
>> thanks a lot and sorry for this never ending story.
>>
>> best wishes
>>
>> Sergiu
--
Mit freundlichen Grüßen
S. Groppa
mailto:[log in to unmask]
|