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

potential_false_negative column #3554

Open
bluegenes opened this issue Feb 25, 2025 · 0 comments
Open

potential_false_negative column #3554

bluegenes opened this issue Feb 25, 2025 · 0 comments
Labels
fyi Information that is interesting or useful

Comments

@bluegenes
Copy link
Contributor

Potential false negative was a mistake column for gather results, because we can never get a false negative. By definition, every gather result is a positive sequence match we obtained with prefetch.

When used correctly, potential_false_negative indicates a situation where the sketch size and /or scaling of one or both sketches means we are unlikely to find a match, regardless of sequence similarity.

We can get false negatives when doing pairwise or search without greedy gather decomposition. It would not be a mistake to include this column in manysearch results, for example, if we use the “—write-all” to write rows without matches. Same for pairwise, multisearch, compare.

Since we have traditionally just written files with only the matching results for e.g. prefetch/search, it is not currently being used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fyi Information that is interesting or useful
Projects
None yet
Development

No branches or pull requests

2 participants