You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Over in https://github.com/ctb/magsearch, I added a --scaled parameter to our runtime workflow to make the query signature scaled value configurable, in an attempt to deal with #2 and #4.
This results in the following output:
thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', src/main.rs:131:29
that is issued once for each subject signature. So I'm pretty sure that (at the moment) the query signatures, --scaled argument, and subject signatures all need to be identical for sra_search to run properly.
It would be nice if when --scaled was specified, all the signatures were downsampled to that scaled, with sra_search outputting an error when that can't happen.
The text was updated successfully, but these errors were encountered:
Fixes#4#6Closes#10
Bring a few bits from sourmash-bio/sourmash#2230
to support the proper query config (scaled considering downsampling,
both of queries and DB sigs).
Over in https://github.com/ctb/magsearch, I added a
--scaled
parameter to our runtime workflow to make the query signature scaled value configurable, in an attempt to deal with #2 and #4.This results in the following output:
that is issued once for each subject signature. So I'm pretty sure that (at the moment) the query signatures,
--scaled
argument, and subject signatures all need to be identical forsra_search
to run properly.It would be nice if when
--scaled
was specified, all the signatures were downsampled to that scaled, with sra_search outputting an error when that can't happen.The text was updated successfully, but these errors were encountered: