-
Notifications
You must be signed in to change notification settings - Fork 4
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
deeplexicon produces different demultiplexing results for GPU and CPU mode. #17
Comments
Are you using cuda10? |
Hi! Could you tell us in which GPU and cuda version are you currently running MoP? Thanks! |
Hi @adalisan , deeplexicon doesn't support never Nvidia architectures. |
@lpryszcz oh... |
Yes, I think I am using cuda 11 with a variety of GPU architectures, some are older and some newer |
It may be possible to use CUDA 10 in our environment using bash modules. Would that work, with the same deeplexicon containers? |
@lucacozzuto I agree we should warn the users about the issue.
adding CUDA10 won't help, because support for newer architectures comes only in CUDA11, while deeplexicon was built against CUDA10. so until deeplexicon is updated, we can't really provide support for newer Nvidia GPUs. |
Thanks @adalisan - we have now updated this info in the DeePlexiCon README and added a WARNING as well as the requriement of CUDA v10. As @lpryszcz mentioned above, we will be releasing very soon (hopefully a couple of weeks) a new version of MasterOfPores (version 3) that contains a new demultiplexing algorithm that works with newer GPU architectures. Thanks! |
For the RNA samples I am running, demultiplexing gives significantly different results. GPU mode results has a lot more unknown assignments and very small number of bc3 barcoded reads. Meanwhile CPU mode produces much more reasonable results.
The text was updated successfully, but these errors were encountered: