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

Latest Blast #146

Open
Sivanandan opened this issue Jul 26, 2022 · 3 comments
Open

Latest Blast #146

Sivanandan opened this issue Jul 26, 2022 · 3 comments

Comments

@Sivanandan
Copy link

I see that you have blast 10.1, do you plan on updating to the latest blast? We have a galaxy instance on a HPC system. On that galaxy we have blast 10.1 (from you) but we have made the latest DB available in a centralized location. Unfortunately, they aren't compatible. What do you suggest in such a situation?

@peterjc
Copy link
Owner

peterjc commented Jul 27, 2022

If you mean we currently wrap NCBI BLAST+ version 2.10.1, yes, it is a bit old.

If you are having difficulties with the DB v4 to v5 change, you can have a mixture of databases (e.g. database A in v4 format, and database B in v5 format), all in the same folder.

However, if upgrading a database from v4 to v5, you must make sure all the old files are removed. We update our NCBI databases with a script, and found with an NCBI mirrored database in v5 format, a few old v4 files still present broke things. The extensions used has changed, but the data stamps should also be informative.

@Sivanandan
Copy link
Author

Sivanandan commented Jul 27, 2022

Yes, I meant 2.10.1. Thanks for your suggestion. Do you plan on wrapping the latest NCBI BLAST+ (2.13.0)?

@peterjc
Copy link
Owner

peterjc commented Jul 27, 2022

At some point, the addition of threading by query batch in BLAST+ 2.12.0 is the most note worth feature to me.

However, #140 really needs addressing first.

peterjc added a commit that referenced this issue Sep 11, 2023
Would close issue #146
peterjc added a commit that referenced this issue Sep 22, 2023
Would close issue #146
peterjc added a commit that referenced this issue Sep 22, 2023
Would close issue #146
peterjc added a commit that referenced this issue Oct 26, 2023
Would close issue #146
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants