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

PacBio: NGMLR slows from 110 reads-mapped/s to ~1 reads-mapped/s on last million reads #69

Open
matthale16 opened this issue Oct 9, 2019 · 0 comments

Comments

@matthale16
Copy link

Did high coverage PacBio sequencing of a human donor (about 8.5 million reads). Trying to use NGMLR to map to GRCh38.p13 Running on a system with an i9-9900K (8 core) and 32gb of ram with the files on the M.2 disk. Everything starts out great with ~110 reads mapped per second for the first ~7.9 million reads (~20 hours in) and then suddenly it slows to about 1 read mapped per second. All 8 cores are still running at 100%, there's 17gb of ram free, and 436gb of disk space available so I don't think it is due to a lack of system resources. This is the second time trying to run this and getting the exact same result --- slows to the point where it will probably not complete.

Any idea what the problem might be? If we want to cut our losses, is there a way to have NGMLR stop trying to align new reads and spit out a usable BAM file? Any help would be greatly appreciated. Thanks, -Matt

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