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

deeplexicon produces different demultiplexing results for GPU and CPU mode. #17

Open
adalisan opened this issue Jul 10, 2023 · 8 comments
Assignees

Comments

@adalisan
Copy link

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.

@lucacozzuto lucacozzuto self-assigned this Jul 12, 2023
@lucacozzuto
Copy link
Member

Are you using cuda10?

@ADelgadoT
Copy link

Hi!

Could you tell us in which GPU and cuda version are you currently running MoP? Thanks!

@lpryszcz
Copy link

Hi @adalisan , deeplexicon doesn't support never Nvidia architectures.
Unfortunately the MoP team can't solve this.

@adalisan
Copy link
Author

@lpryszcz oh...
You should definitely have big WARNING messages for this. Despite a lot of experience with GPUs, I definitely did not expect this. Failing to do inference is one thing, but giving wrong results was definitely not within my expectations.

@adalisan
Copy link
Author

Yes, I think I am using cuda 11 with a variety of GPU architectures, some are older and some newer

@adalisan
Copy link
Author

It may be possible to use CUDA 10 in our environment using bash modules. Would that work, with the same deeplexicon containers?

@lpryszcz
Copy link

lpryszcz commented Jul 14, 2023

@lucacozzuto I agree we should warn the users about the issue.
@adalisan we were trying to warn from the level of the program, but we couldn't make it feasible.
what's really odd, when you execute deeplexicon without Docker, it fails nicely. but inside docker it runs and produces wrong results.

It may be possible to use CUDA 10 in our environment using bash modules. Would that work, with the same deeplexicon containers?

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.
On the bright side, we're working on our own demultiplexing tool. so stay tuned.

@enovoa
Copy link

enovoa commented Jan 12, 2024

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!

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

5 participants