Difference between GUI AutoTrack result and command-line result using the same parameter_id

7 views
Skip to first unread message

Chiara Matti

unread,
Dec 2, 2025, 2:51:11 AM (4 days ago) Dec 2
to DSI Studio
Hi,

I am trying to reproduce in the command line the same tractography and structural connectivity matrix that I obtain in the DSI Studio GUI using the AutoTrack preset. I am using subject 103818a.qsdr.fz of hcp-ya-retest.

In the GUI, the tracking report shows:
A deterministic fiber tracking algorithm (Yeh et al., PLoS ONE 2013) with augmented tracking strategies (Yeh, Neuroimage 2020) was used.
The anisotropy threshold was randomly selected between 0.5 and 0.7 of the Otsu threshold. The angular threshold was randomly selected between 45° and 90°. Step size was set to voxel size. Tracks shorter than 30 mm or longer than 200 mm were discarded. A total of 1,000,000 tracts were tracked. parameter_id=c9A99193Fb803FdbF041b484340420Fcba803FcCDCC4C3Ec

I also compute the connectivity matrix with the following parameters: custom parcellation in MNI, end in region, count, no threshold.

I then run the following command:
dsi_studio --action=trk \
  --source=103818a.qsdr.fz \
  --thread_count=8 \
  --output=103818a_test.tt.gz \
  --parameter_id=c9A99193Fb803FdbF041b484340420Fcba803FcCDCC4C3Ec \
  --connectivity=/Applications/dsi_studio.app/Contents/MacOS/atlas/human/human_schaefer_100_TH_mni.mni.nii.gz \
  --connectivity_threshold=0.0 \
  --connectivity_value=count \
  --connectivity_type=end

However, when I load the resulting .tt.gz file into the GUI using Load Tracts, the tractogram looks noticeably different from the tractogram generated in the GUI using the same preset. Both runs produce 1,000,000 tracts, but when I load the CLI output is seems that there are way less tracts.
Question 1: Why does this happen?

I also tried outputing trk.gz (instead of  tt.gz) and manually tuning the parameters to:

'--tract_count=1000000',
'--min_length=30.0',
'--max_length=200.0',
'--track_voxel_ratio=1',
'--tip_iteration=0', but the results are the same. Here are the differences in connectivity matrices:
- when i use the parameter_id
output2.png
- when I manually change the parameters
output.png

Note: the CLI manual params and the CLI parameter_id are equal.

Question 2: why are the count values of the GUI matrix almost double the CLI ones?

If I divide by 2 the GUI matrix and plot the same matrices as before:
output3.png
Question 3: there are still some differences. Are these acceptable?
Thank you for your help. Best, Chiara

Frank Yeh

unread,
Dec 2, 2025, 9:55:28 AM (3 days ago) Dec 2
to chiaram...@gmail.com, DSI Studio
I will check this in detail and get back to you soon.
Best regards,
Frank

--
You received this message because you are subscribed to the Google Groups "DSI Studio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dsi-studio+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dsi-studio/b3e31ade-d735-402b-9474-3bfbb0e47394n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages