Hi @Melisa_Olivelli,
To train a region specific classifier, it is necessary to use extract-reads from q2-feature-classifier, followed by fit-classifier-naive-bayes. The exact commands used for the V4 classifier with Greengenes2 can be found here.
As an alternative, you could use the classifier trained on the full length records, and should work "out of the box".
All the best,
Daniel
An off-topic reply has been split into a new topic: Feature classifers in python
Please keep replies on-topic in the future.
Hi @wasade
This is excellent! Thank you kindly for your efforts!
I was just wondering if the command "greengenes2 non-v4-16s" is a separate package I need to download. As I receive the error "QIIME 2 has no plugin/command named 'greengenes2'". Any feedback would be greatly appreciated!
Kind regards,
Johann
Thanks @Johanndb!
To run qiime greengenes2 non-v4-16s, it is necessary to install the plugin. That can be done with pip install q2-greengenes2.
All the best,
Daniel
Hello @wasade ,
thank you for your kind advice! Can I kindly ask you one more question? I now obtai several taxa names including numbers or capital letters, such as "g__Blautia_A_141781;s__Blautia_A_141781 faecis" or "p__Firmicutes_A;c__Clostridia_258483;o__Lachnospirales;f__Lachnospiraceae;g__Mediterraneibacter_A_155507;s__Mediterraneibacter_A_155507 faecis". So the questions are:
Thank you again!
Ilaria
Hi @iptz1,
Good questions! The _A labels are directly from GTDB (see here for why). The _<number> is used to represent a distinct node in the phylogeny. In this case, "g__Blautia_A" is supported by more than one node, so we have to differentiate them to ensure the taxonomy label is unique. You can find the three Blautia clades in the Greengenes2 website if you'd like to explore the taxonomy directly.
All the best,
Daniel
Hello, I am also using qiime2 to analyze microbiome data for the first time, I am using V5-V7 region training classifier, I want to ask you if this problem is solved? Can you share your process at this step, thank you very much！
Hi @XIAOXI,
For V5-V7 data, I recommend using the non-v4-16s action which will perform closed reference OTU picking against the backbone. Or, you could perform naive Bayes classification using the full length model.
All the best,
Daniel
8 off-topic replies have been split into a new topic: Command not found with redbiom
Please keep replies on-topic in the future.
An off-topic reply has been split into a new topic: Greengenes Taxonomic Naming Schema: Letters and Numbers
Please keep replies on-topic in the future.
An off-topic reply has been split into a new topic: installing Greengenes2 in a minimal environment
Please keep replies on-topic in the future.
Hello @wasade - Very helpful information! I have a couple of questions. I have paired-end human stool data (processed with dada2) that is good quality through 250 not.
Do you know if there is any advantage to using the single-end versus paired-end data (i.e. the filter-features versus non-v4-16s approach)? And you mention trimming to 150nt (in the Deblur/Dada2 section) - is that a recommendation for filter-features and/or non-v4-16s? Thanks!
Hi @m_s,
If the sequences were generated using 515F-806R EMP primers, then you could trim them to 150nt and filter-features. If you'd prefer to keep the full length, then you'd need to use non-v4-16s.
I'm unaware of literature that has independently benchmarked the various read stitching strategies. In my own analyses, I only use the fwd read from the EMP primers. Most of the taxonomic and phylogenetic signal is proximal to 515F as well, which is why studies like Yatsunenko et al 2012 Nature, which used 90 cycles if I recall correctly, still were quite exciting and compelling. In fact, quite a few of the analyses in the Thompson et al 2017 EMP paper were at 90nt too.
Best,
Daniel
Hi Daniel, thank you for this resource! Can you provide a brief instruction on how to use this database outside of QIIME? For instance, I'd prefer to use Kraken2 and I have both 16s and shotgun sequencing. I presume I need the 16s sequence database, the whole-genome sequence database, and the shared taxonomy, but I can't immediately tell which files these correspond to since there are many files in the FTP repository with similar descriptions.
Hi @John_McElderry,
For shotgun, we recommend using the Woltka toolkit. The genome identifiers in the database are relative to the Web of Life version 2. It is possible Kraken2 will work although we haven't evaluated that. The exact commands we use are buried in here; as an alternative, I would encourage considering depositing data into Qiita as that resource will take care of the compute.
Best,
Daniel
An off-topic reply has been split into a new topic: Importance of using consistance qiime2 versions with classifiers
Please keep replies on-topic in the future.
@wasade
Hi!
Where can we obtain this file gg2-- label_ Map.qza ?
qiime greengenes2 relabel \
--i-feature-table <your_feature_table> \
--i-reference-label-map gg2-<version>-label_map.qza \
--p-as-md5 \
--o-relabeled-table <the_relabeled_table>
Hi @liang_zhou,
That action was created in preparation for an artifact type which I accidentally didn't export! Could you create an issue?
For the near term, what data do you need to relabel?
Best,
Daniel
@wasade Thanks!
Here are my commands and the corresponding input/output files.
qiime greengenes2 non-v4-16s
--i-table table_filtered.qza
--i-sequences rep_seqs_filtered.qza
--i-backbone ../2022.10.backbone.full-length.fna.qza
--o-mapped-table table_filtered.gg2.biom.qza
--o-representatives rep_seqs_filtered.gg2.fna.qza
qiime greengenes2 taxonomy-from-table
--i-reference-taxonomy 2022.10.taxonomy.asv.nwk.qza
--i-table table_filtered.gg2.biom.qza
--o-classification table_filtered_gg2.taxonomy.qza
qiime greengenes2 taxonomy-from-features
--i-reference-taxonomy ../2022.10.taxonomy.asv.nwk.qza
--i-reads rep_seqs_filtered.gg2.fna.qza
--o-classification rep_seqs_filtered_gg2.taxonomy.qza
table_filtered.qza (52.2 KB)
rep_seqs_filtered.qza (423.8 KB)
table_filtered.gg2.biom.qza (45.3 KB)
table_filtered.gg2.biom.qza (45.3 KB)
rep_seqs_filtered_gg2.taxonomy.qza (48.8 KB)
table_filtered_gg2.taxonomy.qza (49.1 KB)
table_filtered.zip (24.0 KB)
table_filtered.gg2.zip (4.3 KB)
My question is:
When I use Greengenes2 to taxonomically characterize my Feature tables, the ID(ASV) of my feature tables will become the record IDs of Greengenes2.
Can I convert record IDs back to ASV through the parameter " --p-as-asv " of qiime greengenes2 relabel? If so, how can I do it.
Hi @liang_zhou,
Thank you for the detail on the commands run!
When using non-v4-16s, the plugin executes the q2-vsearch closed reference OTU picking pipeline against the backbone sequences. The features expressed in the resulting table will be a subset of the backbone. The exact code applied is here.
With 16S V4 ASVs, if using filter-features, the resulting features will be a subset of the V4 ASVs that have previously been placed into Greengenes2.
I'm not aware of a means to do that through QIIME 2 right now. The q2-vsearch's cluster_features_closed_reference action does not appear to return the UC mapping that describes the query / subject relationship. That mapping is necessary to determine what ASVs recruit to which backbone records.
@gregcaporaso I don't think there is a mechanism right now with q2-vsearch to obtain the mapping detail. Would that be valuable? If so I'll open an issue to track it
Best,
Daniel