Hi
Tracking time will most heavily depend on the number of streamlines, which in turn is proportional to the number of seed voxels (and thus can grow rapidly with image resolution).
To find out how long things will take, it is best to run with a low number of samples and see how long that takes. Also if that is an option consider using the GPU implementation which is a whopping 100x faster! I guess you may have to contact Moises Hernandez Fernandez for this.
Cheers
Saad
> On 19 Jun 2018, at 13:13, Davide Momi <[log in to unmask]> wrote:
>
> Dear FSL Users,
>
> I've run bedpostx and now I'm running the Probtrackx2 with a single mask (motor area), steplenght=2 -P=5000 -c=0.2 but it's really time consuming compared to standard. I mean that I still running since 3 days ago. I've already tried to stop and restart everything from the beginning but nothing has changed.
>
> My DWI image come from a GE scanner 3T (30 directions, 71 slices, voxel size 0.8x0.8x2.2).
>
> The strangest thing is that I have done the same analysis with another DTI coming from another dataset (Siemens 64 directions) and everything went smoothly.
>
> Any tips?
>
> Thanks in advance
>
> Davide
>
> ########################################################################
>
> To unsubscribe from the FSL list, click the following link:
> https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=FSL&A=1
########################################################################
To unsubscribe from the FSL list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=FSL&A=1
|