-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dsi_studio_autotrack not running #804
Comments
Hi @aazor, Could you please add --stop-on-first-crash? Also, we're splitting up qsiprep into qsiprep and qsirecon, so in the next release you'll have to do a separate apptainer command to run the recon workflow. |
Hi @mattcieslak |
do you know anything about the error at the bottom? |
yes. It's the very last line and attempt at moving my files to another directory out of /scratch " Copy data back to final destination
" But this shouldn't be impacting qsirecon and DSI studio output correct? |
I also think "qsiprep" did not finish running successfully and therefore ${output_dir} and its subdirectories were not created. |
There are two slashes in the path: |
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
The text was updated successfully, but these errors were encountered: