Hi
Yes these are seed coordinates. They may not match with your surface file input depending on which convention you are using (freesurfer vs first vs caret).
If you want to know how long it takes to run, you can run probtrackx2 with 1 samples per seed location, and multiply the execution time by the number of samples you use in the actual run. The execution time that probtrackx2 outputs correspond to tracking time, i.e. excluding the time it takes to load the data.
Cheers
Saad
On 30 Mar 2012, at 20:10, Ryan Mruczek wrote:
> Can someone tell me what the screen output means for probtrackx2 (--verbose=1)? In particular, I don't know how to interpret the lines of the following format:
>
> run
> 84.0331 90.4158 57.8339
> run
> 93.1025 90.5582 57.1626
> run
> 100.117 90.3825 57.4917
>
> etc...
>
> Can I infer how far along probtrackx2 is from this information? I am running tracking from larger surface ROIs (~14k seeds) to many target voxels (~15k) and I was hoping to be able to track the progress of probtrackx2 along the way. But I'm not sure if the output to the screen is useful in this regard. I thought these values might correspond to seed coordinates, but they don't match up with the surface file or other coordinate files.
>
> Cheers,
> Ryan
>
--
Saad Jbabdi
University of Oxford, FMRIB Centre
JR Hospital, Headington, OX3 9DU, UK
(+44)1865-222466 (fax 717)
www.fmrib.ox.ac.uk/~saad
|