Skip to content
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

Open
aazor opened this issue Aug 13, 2024 · 6 comments
Open

dsi_studio_autotrack not running #804

aazor opened this issue Aug 13, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@aazor
Copy link

aazor commented Aug 13, 2024

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

  • QSIPrep version: 0.22.0 and 0.22.1-unstable
  • Docker version:
  • Singularity version: Singularity/Apptainer Version: 1.1.7

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

@aazor aazor added the bug Something isn't working label Aug 13, 2024
@mattcieslak
Copy link
Collaborator

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.

@aazor
Copy link
Author

aazor commented Aug 13, 2024

Hi @mattcieslak
I had the --stop-on-first-crash flag in the previous attempt. Here is the log file. I had the same outputs.
slurm-37604789_99.pdf

@mattcieslak
Copy link
Collaborator

do you know anything about the error at the bottom? cp: cannot stat '/om2/scratch/tmp/aazor/read_proc/sub-READ2043//data/derivatives/qsirecon/sub-READ2043

@aazor
Copy link
Author

aazor commented Aug 13, 2024

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

mkdir -p ${output_dir}/qsiprep_${qsiprep_version}/
mkdir -p ${output_dir}/qsirecon_${qsiprep_version}/
cp -rn $scratch/data/derivatives/qsiprep/$subject ${output_dir}/qsiprep_${qsiprep_version}/
cp -n $scratch/data/derivatives/qsiprep/${subject}.html ${output_dir}/qsiprep_${qsiprep_version}/
cp -rn $scratch/data/derivatives/qsirecon/$subject ${output_dir}/qsirecon_${qsiprep_version}/
cp -n $scratch/data/derivatives/qsirecon/${subject}.html ${output_dir}/qsirecon_${qsiprep_version}/

"

But this shouldn't be impacting qsirecon and DSI studio output correct?
Because '/om2/scratch/tmp/aazor/read_proc/sub-READ2043/data/derivatives/qsirecon' doesn't exist.

@aazor
Copy link
Author

aazor commented Aug 13, 2024

I also think "qsiprep" did not finish running successfully and therefore ${output_dir} and its subdirectories were not created.

@tsalo
Copy link
Member

tsalo commented Aug 22, 2024

There are two slashes in the path: /om2/scratch/tmp/aazor/read_proc/sub-READ2043//data/derivatives/qsirecon/sub-READ2043. I think that'll resolve to /data/derivatives/qsirecon/sub-READ2043. Perhaps the double slashes are the source of the problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants