You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ?
The text was updated successfully, but these errors were encountered:
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 ?
The text was updated successfully, but these errors were encountered: