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
@JavierJia@Nan-Zhang
Currently, graphbuild uses and outputs VKmer keys and VKmer edges. They could instead use Kmer keys and a single letter for each neighbor.
The text was updated successfully, but these errors were encountered:
@jakebiesinger , actually the graphbuilding currently already used Kmer to represent the key of intermediate results(after keyvalueparser, and local aggregater), and the final output's key is still VKmer. So you mean we also could change the key of final results of graphbuliding to Kmer?
By "a single letter for each neighbor", I meant that given your Kmer and a single letter and direction, you could derive your neighbor's kmer. So during intermediate stages, graphbuild could use this altered representation.
@JavierJia @Nan-Zhang
Currently, graphbuild uses and outputs VKmer keys and VKmer edges. They could instead use Kmer keys and a single letter for each neighbor.
The text was updated successfully, but these errors were encountered: