-
Notifications
You must be signed in to change notification settings - Fork 733
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
Running error with deepvariant_1.6.0-gpu.sif #774
Comments
@Ge-Lab if possible, please structure your issue using code fences. See this guide for details. It will make it easier to read and understand if you place logs inside code blocks, for example. This guide suggests a few things to try. Interestingly, it apperas you should set Additionally, since you have two GPUs you will want to set this variable to 0,1. Do you have the |
Hi Daniele, Thanks for your response. I updated the post as you suggested. How can I set I do have |
@Ge-Lab first lets try setting |
Hi @Ge-Lab , this has been inactive for more than a month, so I'll close. But please feel free to reopen with more details now if you want to follow up! |
Hi,
I followed the instructions on deepvariant quick start (https://github.com/google/deepvariant/blob/r1.6/docs/deepvariant-quick-start.md) to create deepvariant_1.6.0.sif and deepvariant_1.6.0-gpu.sif successfully using apptainer.
Then, I followed the complete genomics T7 case study (https://github.com/google/deepvariant/blob/r1.6/docs/deepvariant-complete-t7-case-study.md) to have some test runs.
I run the following command:
It was successful. Both vcf and gvcf were generated.
I run the following command:
It seems there are some errors and GPU was not used. These are the output (part of the output were removed due to the limit of the characters of this post):
My system is Ubuntu 22.04. I have two GPUs.
nvidia-smi
I did run
export CUDA_VISIBLE_DEVICES=0
before running deepvariant, as you suggested in this issue #761.Why the GPU was not used in my run? Any help would be greatly appreciated!
The text was updated successfully, but these errors were encountered: