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
Thank you for the very cool and important package! This will save me hours and hours of computational work
I was wondering if you can add an option to BLAST two protein sequences against each other and get their e-value etc. I have a list of proteins that I want to compare to each other. If you'd prefer to point me to how I can make this feature and do a pull request, I'm more than happy to do so too!
The text was updated successfully, but these errors were encountered:
Currently, gget blast runs the BLAST on the NCBI BLAST server. This, unfortunately, limits it to the databases available on the server (if anybody has any ideas on how to circumvent this, I would love to hear them).
However, NCBI has its own command-line program called BLAST+, which runs a BLAST locally and allows the user to align to custom databases. When building gget blast, I decided to use the server instead of BLAST+ because I did not want to require the user to download a database and thereby limit the alignment to only the passed databases. However, for your case, BLAST+ might be the better option. I would love to hear about your experience with it if you give it a try.
One option for gget would be to build a "gget blast+" module that locally compiles the BLAST+ binary (similarly to what gget muscle does for Muscle v5). The question would be how to facilitate the database download/building of a custom database. Feel free to give it a try, I would be happy to help!
Thank you for the very cool and important package! This will save me hours and hours of computational work
I was wondering if you can add an option to BLAST two protein sequences against each other and get their e-value etc. I have a list of proteins that I want to compare to each other. If you'd prefer to point me to how I can make this feature and do a pull request, I'm more than happy to do so too!
The text was updated successfully, but these errors were encountered: