Rename qdb.lookup so that it will not be removed
#325
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This would break pairing, which relies on qdb.lookup to decide which sequences to pair. You'd need to make a copy of qdb.lookup, or rename it after the pairing part. |
sokrypton
force-pushed
the
main
branch
2 times, most recently
from
f7b765e to
b4c1bc7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The colabfold.mmseqs.search.py generates a
qdb.lookupto match queries and ids. This file is useful to map back the batched results. However, this file is removed bymmseqs rmdb qdb, which basically doesrm qdb*. Renaming this file avoids this (potentially accidental) removing.