-
Notifications
You must be signed in to change notification settings - Fork 14
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
frequency per feature after proceesing nanopore seq data in qiime2 #8
Comments
You have your output, meaning nothing is wrong there. If you read carefully the pipeline description, you will learn that the vsearch is clustering OTUs based on 85% similarity, which is sort of a threshold that has been used in this study. I would also advise you to explore different pipelines for analysis of 16S rRNA generated by ONT. q2ONT is a fairly old pipeline, and it is not updated anymore. |
Dear, 1 - Do you think data should be rarefied before analyzing alpha and beta diversity? Looking forward to having answer based on your expertise. |
Dear,
I am writing to get input from experienced ones. I got nanopore data and using q2ONT command line to process my 16srRNA gene seq data. After demuliplexing, adapters removal, and trimming the reads to 1400 length, i imported my sequencing data into qiime2.
Ised these commands for deprelication of sequences, and for obtaining feature table seqs and feature table summary.
Dereplication of sequences
qiime vsearch dereplicate-sequences
--i-sequences 4_single-end-demux.qza
--o-dereplicated-table 5_derep-table.qza
--o-dereplicated-sequences 5_derep-seqs.qza
visualization files
qiime feature-table tabulate-seqs
--i-data 5_derep-seqs.qza
--o-visualization 5_derep-seqs.qzv
qiime feature-table summarize
--i-table 5_derep-table.qza
--o-visualization 5_derep-table.qzv
After these steps, i got two files, derep-seqs.qzv and derep-table.qzv.
Upon checking derep-table.qzv using qiime2 view, i realized that something might have gone wrong, as Frequency per feature is showing 1. Photo is attached.

Could you please provide insights what could have gone wrong that i obtained such outcomes, or it is normal to get such outcomes while processing nanopore seq data?
Thank you
The text was updated successfully, but these errors were encountered: