We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Similar to dump in KMC_tools, write kmer:count pairs to a text file.
kmer:count
Could add two options for this:
.dump_hash()
hash:count
.dump()
The second option should throw an error if no hash:kmer map is stored in the KmerCountTable object.
hash:kmer
KmerCountTable
Should we support sorting output on either kmer or count?
The text was updated successfully, but these errors were encountered:
Check out Pariter for parallel queries that preserve input / output order.
Sorry, something went wrong.
(I've used rayon extensively - ref also #22)
Just adding .dump_hash() for now until we have a solution for #21.
Default sort on counts then keys. Option to sort on keys.
@ctb For writing output, should we:
2 is easier to write tests for, 1 is probably easier for users.
Adamtaranto
Successfully merging a pull request may close this issue.
Similar to dump in KMC_tools, write
kmer:count
pairs to a text file.Could add two options for this:
.dump_hash()
forhash:count
pairs.dump()
forkmer:count
pairsThe second option should throw an error if no
hash:kmer
map is stored in theKmerCountTable
object.Should we support sorting output on either kmer or count?
The text was updated successfully, but these errors were encountered: