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

cudamapper terminates while doing an all-vs-all mapping #664

Open
alanorth opened this issue Sep 20, 2021 · 0 comments
Open

cudamapper terminates while doing an all-vs-all mapping #664

alanorth opened this issue Sep 20, 2021 · 0 comments

Comments

@alanorth
Copy link

I'm trying to do an all-vs-all mapping with cudamapper (dev branch, git-baab5668) and it terminates with an exception:

$ cudamapper SRR.unmapped.choped.fastq.gz SRR.unmapped.choped.fastq.gz
Initialized GenomeWorks logger with log level ERROR
-C / --target-indices-in-host-memory not set, using -Q / --query-indices-in-host-memory value: 10
-c / --target-indices-in-device-memory not set, using -q / --query-indices-in-device-memory value: 5
NOTE - Since query and target files are same, activating all_to_all mode. Query index size used for both files.
Query file: SRR.unmapped.choped.fastq.gz, number of reads: 249455
Target file: SRR.unmapped.choped.fastq.gz, number of reads: 249455
Programmatically looking for max cached memory
Using device memory cache of 33390691615 bytes
Device 0 took batch 1 out of 1 batches in total
terminate called without an active exception
Aborted

Environment is CentOS 7 with an NVIDIA Tesla V100-PCIE-32GB. Thank you!

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

1 participant