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
I figured that if you follow what's done in the Tutorial, you can see that the files distributed with metaDMG cannot be necessarily used for your own data.
This tutorial is not very explicit, but then it makes sense to peek into the files downloaded with metaDMG get-data --output-dir raw_data:
Indeed, in raw_data/acc2taxid.map.gz, you can discover that what the metaDMG-cpp will use to lookup taxids and calculate the LCA are likely the "chr" listed as accession. Likewise, these accession are the targets onto which the reads were mapped.
For example, if you download these files using metaDMG get-data, you can see that is matches and there is a taxid for a given mapped-onto genome.
The thing is, if you use a custom database and not NCBI genomes, that you have to make sure you make matching contents in files passed to --names, --nodes and --acc2tax. For each of my metagenomes' contigs, I'll be pulling taxids from the GOs of the majority of genes annotated using eggnog-mapper, and make sure the taxids are themselves pulled/referenced is an NBCI taxdump (https://ftp.ncbi.nlm.nih.gov/pub/taxonomy/).
Hi,
I'm trying to use this tool but it's unclear where the names and nodes files comes from in the documentation.
Does the tool provide or download it automatically?
Thanks,
Susheel
The text was updated successfully, but these errors were encountered: