Skip to content
New issue

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

is there a way to get the kmer counts of the kmers in the produced unitigs? #27

Open
shokrof opened this issue Feb 27, 2023 · 4 comments
Labels
feature request question Further information is requested

Comments

@shokrof
Copy link

shokrof commented Feb 27, 2023

Hi,
I am wondering if I can get the kmer counts along with the unitigs fasta files.

Thanks,
Moustafa

@jamshed
Copy link
Member

jamshed commented Mar 10, 2023

Hello Moustafa,

We do not support this at this moment, unfortunately. It might be doable, given that we have the corresponding KMC databases; but attaching the k-mer counts to the unitigs is non-trivial in cuttlefish.

@shokrof
Copy link
Author

shokrof commented Mar 10, 2023

is there a way to keep the KMC databases? I can make an easy script to get the kmer counts if can get the kc databases

@jamshed
Copy link
Member

jamshed commented Mar 10, 2023

Hi @shokrof: are you using cuttlefish 2, i.e. using the --read or --ref arguments? If yes, then we have valid counts only for the (k + 1)-mers—the k-mers are extracted from them and their counts aren't obtainable in a straightforward manner from the (k + 1)-mers. If the (k + 1)-mer counts would do, then I can post some instructions here to retain the KMC databases.

@rchikhi
Copy link

rchikhi commented Oct 7, 2023

Here's what to change to retain the KMC database of (k+1)-mer counts:
keep-edges-counts-diff.txt

@jamshed jamshed added question Further information is requested feature request labels Oct 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants