-
Notifications
You must be signed in to change notification settings - Fork 89
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
Long runtime - choosing correct parameters #229
Comments
Have a look at the Quatiles:
10% 20% 30% 40% 50% 60% 70% 80% 90% 95%
16 21 29 72 268 972 3329 11697 42939 65535 If you find the kmer were highly repetitive, please set -K 2000 to speed the alignment up. Otherwise, please paste the log message. Jue |
The kmer distribution looks ok to me.
|
[Fri Feb 5 16:57:44 2021] - high frequency kmer depth is set to 16534 Try to set |
Hi, |
In this case, if discarded too many high freq kmers, it may lead to fragmental and truncated contigs. |
Hi,
I'm using wtdbg2 v2.5 on a 3G genome with about 60x PacBio Sequel CLR data and chose
-x preset3
for large genomes. Kmer counting was done in 90 minutes with 60 threads. The overlap stage is running for eight days now and still not finished, which seems quite high compared to runtimes other get on similar genome sizes and data. Would using-x sq
speed things up or do you have recommendations on which parameter set to use?Thanks,
Chris
The text was updated successfully, but these errors were encountered: