Yeah, probably Tim is right. I noticed the resolution but it is true that this is unlikely to reflect the "real sampling". On the other hand, depending on your system you may in fact have acquired the data at 256x256? But you better check on it as this is a indeed a fairly big data set to process...
Andreas
-----Ursprüngliche Nachricht-----
Von: FSL - FMRIB's Software Library [mailto:[log in to unmask]] Im Auftrag von Tim Behrens
Gesendet: Donnerstag, 1. Februar 2007 18:11
An: [log in to unmask]
Betreff: Re: [FSL] AW: [FSL] bedpost running time
Your sacnner has upsampled the resolution of your image to <1mm in- plane. This is what is causing it to be slow, and it will also cause huge problems at later stages.
You should turn this feature off on your scanner, so that your data is analysed at the resolution that it is acquired. Then everything will run much faster.
cheers
T
On 1 Feb 2007, at 17:07, Andreas Bartsch wrote:
> Hi,
> Be patient. On cygwin such a data set make take 36 hours or so.
> Cheers-
> Andreas
>
> -----Ursprüngliche Nachricht-----
> Von: FSL - FMRIB's Software Library [mailto:[log in to unmask]] Im
> Auftrag von [log in to unmask]
> Gesendet: Donnerstag, 1. Februar 2007 17:33
> An: [log in to unmask]
> Betreff: [FSL] bedpost running time
>
> Hi,
>
> I'm fairly new to FSL. I'm trying to run bedpost. I have a data set
> with
> 34 volumes, 32 diffusion weighted, and 2 withouth the weighting.
> It has
> 56 slices, and 56 slices. It has been running for over 18 hours now,
> and so far it's only analyzing the 10th slice. Should I be concerned
> that it's taking so long? I got images that looked ok when I ran DTI
> fit.
> when I ran the datacheck, everything was fine. I'm running it on
> windows XP with 2GHz pentium processor, with 2GB of ram. The
> bedpost_datacheck output is below. Any ideas anyone? Or is it just a
> large dataset?
>
> data_type INT16
> dim1 256
> dim2 256
> dim3 56
> dim4 34
> datatype 4
> pixdim1 0.8280000091
> pixdim2 0.8280000091
> pixdim3 2.2000000477
> pixdim4 1.0000000000
> cal_max 4095.0000
> cal_min 0.0000
> file_type NIFTI-1+
>
> /home/mark/Kelly/UBC_3T_DTI_32dir_data/BEDPOST/nodif
> data_type INT16
> dim1 256
> dim2 256
> dim3 56
> dim4 1
> datatype 4
> pixdim1 0.8299999833
> pixdim2 0.8299999833
> pixdim3 2.2000000477
> pixdim4 3.0000000000
> cal_max 4095.0000
> cal_min 0.0000
> file_type NIFTI-1+
>
> /home/mark/Kelly/UBC_3T_DTI_32dir_data/BEDPOST/nodif_brain_mask
> data_type INT16
> dim1 256
> dim2 256
> dim3 56
> dim4 1
> datatype 4
> pixdim1 0.8299999833
> pixdim2 0.8299999833
> pixdim3 2.2000000477
> pixdim4 3.0000000000
> cal_max 1.0000
> cal_min 0.0000
> file_type NIFTI-1+
>
> num lines in /home/mark/Kelly/UBC_3T_DTI_32dir_data/BEDPOST/bvals
> 1
> num words in /home/mark/Kelly/UBC_3T_DTI_32dir_data/BEDPOST/bvals
> 34
> num lines in /home/mark/Kelly/UBC_3T_DTI_32dir_data/BEDPOST/bvecs
> 3
> num words in /home/mark/Kelly/UBC_3T_DTI_32dir_data/BEDPOST/bvecs
> 102
>
> thanks
>
> ~Kelly
|