Skip to content
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

Question: how megahit deals with different size read sets? #336

Open
Valentin-Bio-zz opened this issue Aug 15, 2022 · 0 comments
Open

Question: how megahit deals with different size read sets? #336

Valentin-Bio-zz opened this issue Aug 15, 2022 · 0 comments

Comments

@Valentin-Bio-zz
Copy link

Hello , I just want to understand what happens to the iterative assembly on each k-mer step. Lets say I have a read set of different lengths. the minimum read length is of 40bp and the longer reads are of 150bp. (the great majority of the reads are on the 130-150 bp range). So if I let megahit choose the k-mer sizes how it deals with the shorter reads? I was taking a look into the log file of a running assembly and I see this "k-max reset to: 141" this means that the last iteration is going to use a k-mer size of 141bp. So I assume that shorter reads are discarded due to k-mer > shorter input reads and it will employ the previous assembled contigs plus the input reads that are equal or longer to the last k-mer size ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant