From 1a54b7a1956b28feaf334f10aeaae5c1dfea7cca Mon Sep 17 00:00:00 2001 From: Vincent Beaudoin <77688542+VincentBeaud@users.noreply.github.com> Date: Wed, 6 Nov 2024 15:47:10 -0500 Subject: [PATCH] Update fibertube_tracking.rst --- docs/source/documentation/fibertube_tracking.rst | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/source/documentation/fibertube_tracking.rst b/docs/source/documentation/fibertube_tracking.rst index f2c3424c3..d64517139 100644 --- a/docs/source/documentation/fibertube_tracking.rst +++ b/docs/source/documentation/fibertube_tracking.rst @@ -86,10 +86,10 @@ The first thing to do is resample ``centerlines.trk`` so that each centerline is formed of segments no longer than 0.2 mm. Note: This is because the next script will rely on a KDTree to find - all neighboring fibertube segments of any given point. Because the - search radius is set at the length of the longest fibertube segment, - the performance drops significantly if they are not shortened to - ~0.2mm. +all neighboring fibertube segments of any given point. Because the +search radius is set at the length of the longest fibertube segment, +the performance drops significantly if they are not shortened to +~0.2mm. To resample a tractogram, we can use this script from scilpy: @@ -171,8 +171,8 @@ saved in ``metrics.txt``. (Values expressed in mm): :alt: max_voxel_rotated visualized in 3D Note: This information can be useful for analyzing the - reconstruction obtained through tracking, as well as for performing - track density imaging. +reconstruction obtained through tracking, as well as for performing +track density imaging. Performing fibertube tracking ----------------------------- @@ -222,7 +222,7 @@ waiting a little bit, feel free to play with the parameters and explore the resulting tractogram. Note: Given the time required for each streamline, the - ``--processes`` parameter will be very useful. +``--processes`` parameter will be very useful. Reconstruction analysis ~~~~~~~~~~~~~~~~~~~~~~~