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

basecaller dorado-0.4.2-linux-x64 progress bar freeze at 50% #465

Closed
husamia opened this issue Nov 9, 2023 · 3 comments
Closed

basecaller dorado-0.4.2-linux-x64 progress bar freeze at 50% #465

husamia opened this issue Nov 9, 2023 · 3 comments

Comments

@husamia
Copy link

husamia commented Nov 9, 2023

I am running the latest dorado build for linux using gpu on Windows 11 with GPU and Nvidia support within WSL

After about 50% the progress bar stops updating, although the output file and the nvidia GPU utilization shows the basecalling is still ongoing!

/mnt/c/dorado-0.4.2-linux-x64/bin$ ./dorado basecaller --batchsize 96 --recursive --device cuda:all dna_r10.4.1_e8.2_400bps_sup@v4.2.0/ /mnt/d/ONT/PGx_Twist_UDI/raw_combined_pod5/ > /mnt/d/ONT/PGx_Twist_UDI/dorado-0.4.2_dna_r10.4.1_e8.2_400bps_sup@v4.2.0.bam
[2023-11-03 11:10:58.192] [info] > Creating basecall pipeline
[2023-11-03 11:12:06.643] [warning] - set batch size for cuda:0 to 128
[███████████████▏ ] 50% [05d:22h:30m:11s<05d:19h:42m:50s]

@tijyojwad
Copy link
Collaborator

Hi @husamia - are you still running into this issue?

  • When you said GPU utilization says basecalling is going on, do you see consistency high GPU + power utilization?
  • How large is your dataset? Hav you tried with smaller dataset to see if that runs through?
  • To rule out I/O issue, can you redirect the output to /dev/null and check if the same dataset completes?

@husamia
Copy link
Author

husamia commented Dec 27, 2023

@tijyojwad I am running into the issue still this is related #400

at around 50% it seems the updating stops but the GPU high + power utilization
POD5 data is about 57GB in size (I did test it with lower data amount the problem didn't occur) but I am not sure it helps at all

@tijyojwad
Copy link
Collaborator

Hi @husamia can you try with a more recent version v0.7.x to see if the issue prevails?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants