-
Notifications
You must be signed in to change notification settings - Fork 21
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
peak calling device initialization issue. #12
Comments
Found the problem, I only have 1 gpu on the node, and the gpu_cores is hard coded to 1, but rgtsvm uses this number as gpu id. change this to gpu_cores=gpu_id worked, not sure if it'll work for multi-GPUs. run.time <- system.time(r <- peak_calling( asvm, gdm, ps_plus_path, ps_minus_path, cpu_cores=cpu_cores, use_rgtsvm=use_rgtsvm, gpu_cores=1)); |
Thank you for your feedback. Or Best, |
I tried to run dReg without GPU option and received an error about rgtsvm library. When I check the code in
If I provide 0 for If I don't provide any value for I manually edited |
Thank you for your feedback. I will change it as you did. |
I'm getting "Error in device initialization" error when running peak calling with dREG, but the prediction function runs fines. .
I'm running on a node with:
OS: redhat 7.4 kernel 3.10.0-693
GPU: GTX1080
Cuda: cuda9.0
dreg version: latest version checked out from github
rgtsvm version: latest version
bedops: 2.4.14
All the data are test data downloaded from ftp server provided, below is the test run output:
What have I tried:
Error in if (gpu_id > 0) { : missing value where TRUE/FALSE needed
Execution halted
Please let me know of any insights to this problem.
The text was updated successfully, but these errors were encountered: