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

What are 'unassigned' hits? #10

Open
vmkalbskopf opened this issue Oct 29, 2021 · 1 comment
Open

What are 'unassigned' hits? #10

vmkalbskopf opened this issue Oct 29, 2021 · 1 comment

Comments

@vmkalbskopf
Copy link

I have quite a few results in my tree that are "unassigned Eukaryota (13)" or "unassigned Plasmodium (1168)" for instance. How should I interpret this?

@adamthrash
Copy link
Contributor

When a hit is assigned to a node, the coverage of that node's ancestors is incremented as well. For example, a hit that is assigned to H. sapiens will increase the coverage of H. sapiens, Homo, Hominidae, etc., all the way up through the root node.

Unassigned hits represent the difference in coverage from hits assigned to the node's children and hits assigned directly to the node. For example, if the node Homo had 15 hits via having 10 hits to H. sapiens and 5 hits assigned directly to Homo, then Keanu would display this node as "Unassigned Homo (5)".

This way of naming indicating hits assigned directly to a non-species node might not be the clearest, so I'll leave this issue open to indicate the need for a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants