-
Notifications
You must be signed in to change notification settings - Fork 17
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
one2all/new2all output counts for common k-mers between multiple db-samples #12
Comments
Dear Mikhel, We can think of adding the functionality you mentioned to kmer-db. However, the number of all possible intersections grows exponentially with a number of queries. Wouldn't it be better to give user the possibility to explicitly state what intersections he is interested in? Regards, |
Hi! The number of intersections does indeed grow fast. |
Just run |
Hi!
The one2all/new2all give this information about the intersection sizes with a new sample:
s1: 100/150
s2: 200/300
s3: 50/1000
...
Is there any way to get more detailed information showing common k-mers? For example, given these counts, I have no idea if the 50 k-mers seen in s3 are also present in s1 or s2.
The preferred output would be something like this:
s1: 50/50
s2: 200/300
s3: 0/900
s1 AND s3: 50/100
...
This can be achieved by creating all of the intersections beforehand, but looking at the kmer-db database structure, I was hoping to skip that step.
Regards,
Mihkel
The text was updated successfully, but these errors were encountered: