-
Notifications
You must be signed in to change notification settings - Fork 78
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
Erroneous f_unique_to_query
calculation in Rust code.
#3137
Comments
I can't tell if the same calculation in sourmash/src/core/src/index/linear.rs Line 183 in 472d4e5
It looks like here maybe |
And, also, we should have tests for this on the Rust side in sourmash core. Right now we're relying on catching it over in the branchwater plugin, which is, well, roundabout and also a bit unreliable! |
f_unique_to_query
calculation in Rust code.f_unique_to_query
calculation in Rust code.
This PR fixes an issue introduced in #2943 where we introduced a subtly broken calculation that uses the _current_ size of the query metagenome as the denominator for the `f_unique_to_query` calculation. Fixes #3137 This PR also adds some commented-out test code that demonstrates #3139 / sourmash-bio/sourmash_plugin_branchwater#322. That's something I haven't been able to debug, so I'd suggest fixing that independently - I'd rather fix _a_ problem _now_, rather than waiting until we can fix _multiple_ problems at some later indeterminate time :). ## Notes - [x] do we need to fix same problem in `linear.rs`? or just rename things per #3137? - [x] we should add some tests for this
It looks like #2943 introduced a subtly broken calculation that uses the current size of the query metagenome as the denominator for the
f_unique_to_query
calculation:sourmash/src/core/src/index/mod.rs
Line 235 in 472d4e5
In order to match the Python version, this should use the original size of the query metagenome:
sourmash/src/sourmash/search.py
Line 586 in 472d4e5
Discovered over in sourmash-bio/sourmash_plugin_branchwater#318 when trying to debug discrepancies there ;)
The text was updated successfully, but these errors were encountered: