-
Notifications
You must be signed in to change notification settings - Fork 21
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
More fragmented assembly after updating from version 1.3.0 #50
Comments
Hi Ilya, Best regards, |
Hi, |
The data set seems it has enough coverage and not too bad accuracy, not sure why the latter versions do not work as 1.3.0. You could try v1.6.0 from branch options (you can also try different k,w values). Sorry for my delayed reply. |
Can you please elaborate on how the k and w values are expected to affect the assembly? |
I have create a new release, it will be picked up automatically by bioconda soon. Regarding parameters, I think you can first try with k = 19. We have recently evaluated higher k values (up to 25) on Guppy 5 data, which has tendency to increase contiguity. Earlier Raven versions used (k, w) = (29, 9) (option --weaken, now removed) for HiFi data to improve assembly. I am not sure how it will affect Guppy 4.x datasets, but your dataset is quite small so you can try a couple of values around the default (k, w) = (15, 5). |
Thank you for the new release and information. |
Hello,
I have been using raven for a while and recently I reran an assembly of the same bacterial data with a newer version of raven and got a more fragmented genome. With version 1.3.0 I got the complete bacterial genome in one contig. With any later version I got the genome more fragmented and with a smaller total assembly size.
Is it possible to keep the improvements done in recent raven versions but restore the better contiguity observed in version 1.3.0?
Sorry but I can't share the data.
Thanks,
Ilya.
The text was updated successfully, but these errors were encountered: