-
Notifications
You must be signed in to change notification settings - Fork 80
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
allow gather to mixed databases, letting manifests/selectors sort it out? #2200
Comments
hmm, maybe. see #1426, especially my comment:
IIRC, the history is: before zipfiles, we (mostly) had databases that were locked to a single ksize. so if an incompatible database was specified, it seemed good to error out. and, before manifests, we had no fast/easy way of counting the number of matching signatures, so we had problems doing accurate and informative display of number of signatures early on in the process. but this has all changed. while I think we do want to support legacy formats, the existence of as another sign that we should be doing something different, I note this ugly bit of code in for db in databases:
counter = None
try:
counter = db.counter_gather(prefetch_query, args.threshold_bp)
except ValueError:
if picklist or pattern_search:
# catch "no signatures to search" ValueError from filtering
continue
else:
raise # re-raise other errors, if no picklist. which is needed to maintain the error exit when no compatible signatures exist... I keep on stumbling over this and would very much like to refactor it! codewise, it should be as simple as calling |
Duplicate of #1637 :) |
While running gather, we search with a single ksize and now use manifests to figure out what signatures we can search against. That means:
zip
database, we only search against the right one and everything is fine.BUT,
no compatible signatures found in '{database}'
, rather than searching against the compatible sigs.Could we just allow search databases to have no compatible signatures, as long as there are some compatible signatures to search?
use case: makes passing in search databases easier for cases where you may want to run more than one ksize in a workflow.
The text was updated successfully, but these errors were encountered: