Closed Sashanity closed 6 years ago
This is a known issue when you have very long reads (e.g. the 300k+ reads in your dataset) and are using a high error rate for the corrected nanopore reads. See issue #521. You can try the fast options recommended there (overlapper=mhap utgReAlign=true
). You can also lower the correctedErrorRate from the default of 0.144 which is meant to handle most nanopore data including older R7 to something like 0.1 or 0.12 assuming you are using a recent chemistry and base caller.
Thank you for the quick respond! I'll try to do it as you suggested.
@skoren does it make sense to run it toghether? lower correctedErrorRate and overlapper=mhap utgReAlign=true
The alternate parameters are fast enough that you don't have to lower the error rate so you can run either or.
I'm running canu 1.6 released version. I am running all 3 steps (correction, trimming, assembling) separately. I am assembling nanopore data. I am trying to trim the corrected data that was produced by canu, and the trimming process running about 3 days by know without any progress in it, so I think that something is wrong with it. Here is the command:
Here is the .log file for the process.