-
Notifications
You must be signed in to change notification settings - Fork 4
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
blastn 2.15 support #105
Comments
Just posting as I think this covers embedding the taxids in custom blastdbs, I can look in more detail when I get a chance later |
We download the NR database from the NCBI and it should already contain the taxon IDs. The problem is that I had the impression that the error was only showing up with 2.15 (same database and same command-line otherwise). Let me find an example |
Yes, here is an example
If I remember correctly, same problem with a fresh download of the NT database at |
tracking progress in JIRA but adding the solution here for posterity Apparently we need to stage the tax* files into the working dir. This seems to conflict with what the online docs say, but at least the solution on our end is simple. I'll patch the blastn module to copy these over
|
🙌🏼 |
When switching to blastn 2.15 (tried both
2.15.0--pl5321h6f7f691_0
and_1
), there is this warning on stderr:The -taxids command line option requires additional data files. Please see the section 'Taxonomic filtering for BLAST databases' in https://www.ncbi.nlm.nih.gov/books/NBK569839/ for details.
which suggests we could be doing something wrong, but I can't find on https://www.ncbi.nlm.nih.gov/books/NBK569839/#_usrman_BLAST_feat_Taxonomic_filtering_fo_ any information on making the option work.
In the source code
c++/src/algo/blast/blastinput/blast_args.cpp
I can find that the warning is printed whenever an exception is raisedso it seems there really is something wrong, but I don't know what. It'd be great to get more information about that exception, what it means, where exactly it's raised, etc/.
I also tried downloading a recent NT databases and faced the same problem. Maybe we're missing some files ?
The text was updated successfully, but these errors were encountered: