You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: