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
After counting k-mers for each control sample, we should investigate composing the counttables into a single nodetable before running kevlar novel. This should a couple of synergistic benefits.
We have a single table instead of 2 (or more), reducing time due to k-mer abundance queries
A nodetable consumes 1/8 of the size of a counttable with the same number of buckets
The cost is, of course, another pass over the "data". But it should be possible to build a nodetable directly from the underlying counttables themselves without iterating over the reads again. So "data" should be quite small and manageable.
The text was updated successfully, but these errors were encountered:
After counting k-mers for each control sample, we should investigate composing the counttables into a single nodetable before running
kevlar novel
. This should a couple of synergistic benefits.The cost is, of course, another pass over the "data". But it should be possible to build a nodetable directly from the underlying counttables themselves without iterating over the reads again. So "data" should be quite small and manageable.
The text was updated successfully, but these errors were encountered: