Tried to run 0.22.0 and unstable 0.22.1
Did not get any output from dis_studio_autotrack. From one of the log files (attached)
slurm-37677449_137.pdf
, it appears that dsi_studio_autotrack attempted to run, but there were errors during the process related to logging and the execution of DSI Studio commands.
Ran qsiprep, trying to run dis_studio_autotrack to obtain the segmented 56 WM tracts in a CSV file.
What did you expect to happen?
I expected to get 2 directory outputs: qsiprep and qsirecon-DSIStudio (which would have the CSV file with data from the segmented WM tracts). I did a run with an earlier version, which successfully ran through autotrack, and gave a CSV output, but some tracts were missing. I know this was a bug you were working on.
What actually happened?
I only got qsiprep outputs. Did not get any qsirecon-DSIStudio output
Summary
Tried to run 0.22.0 and unstable 0.22.1 Did not get any output from dis_studio_autotrack. From one of the log files (attached) slurm-37677449_137.pdf , it appears that dsi_studio_autotrack attempted to run, but there were errors during the process related to logging and the execution of DSI Studio commands.
Additional details
What were you trying to do?
Ran qsiprep, trying to run dis_studio_autotrack to obtain the segmented 56 WM tracts in a CSV file.
What did you expect to happen?
I expected to get 2 directory outputs: qsiprep and qsirecon-DSIStudio (which would have the CSV file with data from the segmented WM tracts). I did a run with an earlier version, which successfully ran through autotrack, and gave a CSV output, but some tracts were missing. I know this was a bug you were working on.
What actually happened?
I only got qsiprep outputs. Did not get any qsirecon-DSIStudio output
Reproducing the bug