Thank you very much, Anastasia.
I have checked the related mails in the list and found not me came across this problem.
As you said, I know how I can run my data.
But I have a question. Why would we make trac-all compatible to other scanner or acquisitions, since we can get bvecs and bval from the DICOM header?
 
thank in advance.
 
 
Xiangzhen Kong
 
From: Anastasia Yendiki
Date: 2012-02-04 00:52
To: Xiangzhen Kong
CC: freesurfer
Subject: Re: [Freesurfer] /path/to/dmri/dwi_orig_flip.mghdti.bvecs': No such file or directory
 
Unless your dicoms came from the same acquisition as the default 
MGH/Siemens one, you'll have to set bvecfile and bvalfile and provide 
those files yourself.
 
On Fri, 3 Feb 2012, Xiangzhen Kong wrote:
 
> Hi all
> Now I am learning the trac-all using with DICOM data, but came across a
> problem.
> +++
> mv?f?xxx/dmri/dwi_orig_flip.mghdti.bvecs?xxxx/dmri/bvecs
> mv:?cannot?stat?`/xxx/dmri/dwi_orig_flip.mghdti.bvecs':?No?such?file?or?dir
> ectory
> +++
> I check the dir /xxx/dmri/ and there are only two files
> 'dwi_orig_flip.nii.gz' , 'dwi_orig.nii.gz'?and a dir 'xfms'.
> Does trac-all extract bvals/bvecs automatically when start with DICOM data?
> My data is from a siemens scanner.
> ?
> Thanks!
> ?
> Xiangzhen
> ?
> 2012-02-03
> 
> ____________________________________________________________________________
> Xiangzhen Kong
> 
>
 
 
The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.