My experience has been that using KAligner produces better assemblies
with BWA as a close second. I didn't see as drastic a difference as
you're showing here. That's interesting. Can you try using BWA to add a
third data point to this comparison? How long are the reads?
Cheers,
Shaun
Cheers.
I've actually been focusing on improving the performance of KAligner, and these improvements should be in the next release of ABySS.
First, I've made it so that KAligner creates the number of worker threads specified instead of one worker for each file. This greatly improves the performance when there is only one or two read files. Second, I've made it so that the output is deterministic. The goal here is to make it relatively trivial to split the contigs we're aligning accross many machines, and then merge the result so that we can align anything ABYSS-P is able to assemble.
Tony
________________________________________
From: abyss...@googlegroups.com [abyss...@googlegroups.com] On Behalf Of Matthew MacManes [macm...@gmail.com]
Sent: Wednesday, July 20, 2011 12:00 PM
To: abyss...@googlegroups.com
Subject: KAligner gives better results..
> Also, would the selection of the n parameter have
> to be different depending on the aligner used - when kaligner breaks
> up the read into kmers, is each individual kmer counted as an
> individual link when deciding to join contigs together?
Each read is counted as one link, not each k-mer.
Cheers,
Shaun