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

Getting nt BLAST lineage directly from BLAST output #50

Open
eeaunin opened this issue Jul 18, 2024 · 0 comments
Open

Getting nt BLAST lineage directly from BLAST output #50

eeaunin opened this issue Jul 18, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@eeaunin
Copy link
Contributor

eeaunin commented Jul 18, 2024

Description of feature

In the future we could change the BLAST code so that it wouldn't need the accession2taxid files and the GET_LINEAGE_FOR_TOP module. The accession2taxid files were needed in the past because the nt BLAST database at /data/blastdb/Supported/NT didn't have built-in taxonomy. But when using the v5 databases with built-in taxonomy like this version of ASCC does, it should be possible to get BLAST hit taxid's directly from BLAST's output and circumvent the need for the accession2taxid database files and the https://github.com/sanger-tol/ascc/blob/dp24_btk_datasets/bin/get_lineage_for_top.py script

@eeaunin eeaunin added the enhancement New feature or request label Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants