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

Proposal: Lowest Common Ancestor (LCA) module for assigning taxonomy #610

Open
a4000 opened this issue Aug 2, 2023 · 2 comments
Open

Proposal: Lowest Common Ancestor (LCA) module for assigning taxonomy #610

a4000 opened this issue Aug 2, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@a4000
Copy link
Contributor

a4000 commented Aug 2, 2023

Description of feature

I can add a module to Amliseq that would run the LCA scripts from eDNAFlow. More information can be found here: https://github.com/mahsa-mousavi/eDNAFlow#lca-lowest-common-ancestor-script-for-assigning-taxonomy

The input to the module would be the output from blastn, so this module might not work if the user doesn't use blastn. The other input file for this module would be the DADA2_table.tsv file, or alternatively, the curated table produced by LULU if the user chose to use LULU.

The main output file for this module is a tsv file that contains the same information as the input ASV tsv file, plus the number of unique blast hits, and the various taxonomy levels assigned to the ASV (with a "dropped" value in each level where an ASV didn't meet certain thresholds). It's possible this output file may need to be modified to be more compatible with downstream steps in Ampliseq.

@a4000 a4000 added the enhancement New feature or request label Aug 2, 2023
@d4straub
Copy link
Collaborator

d4straub commented Aug 2, 2023

All taxonomic classification subworkflows (see here) use ASV sequence tables (fasta) after the various filtering steps (see e.g. DADA2). In any case, a subworkflow such as here would be great.
I propose to use LCA after blastn (or as Daniel Lundin proposed rather vsearch) in a separate taxonomy assignment subworkflow. The output of that subworkflow would be the downstream-compatible taxonomic classification.

@a4000
Copy link
Contributor Author

a4000 commented Aug 2, 2023

A subworkflow sounds like a good idea, thanks

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