-
Notifications
You must be signed in to change notification settings - Fork 19
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
WARNING: iterations are disabled #15
Comments
Hi Phylloxera, Alex |
Hi Alex, |
Yes, it is a low coverage issue - you lost many reads after bbmerge. From the log you uploaded you can see that the average coverage is 8.86528. It is supposed to be > 10 for the default parameters. You can try --max_kmer_count 5 or lower, and you'll probably get some results. I'll be surprised if premerging paired reads will be more efficient than allowing skesa to do it internally. |
Good to know about the coverage count cut-off, it makes intuitive sense. And also the max_kmer_count 'fix', I'll try it! Skesa works really well on my paired-end single cell genomes with adequate coverage. The test was more thinking whether it might also be useful for single-end, metagenome, and 'dirty' viral samples in the future. |
Hello,
I saw in issue #11 that iterations are disabled by default for single-end data. I've also observed that this seems to be hard coded, ie. even when I specify
--steps 11
, I still get 'WARNING: iterations are disabled'. It seems skesa should be more powerful for single-end data (return fewer contigs) if run at multiple kmers... am I missing something important theoretically by thinking this?Thanks!
The text was updated successfully, but these errors were encountered: