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

Fix Trim documentation: it should be keep vs. remove. #3142

Closed
clairexu010 opened this issue Sep 8, 2021 · 1 comment
Closed

Fix Trim documentation: it should be keep vs. remove. #3142

clairexu010 opened this issue Sep 8, 2021 · 1 comment

Comments

@clairexu010
Copy link

Dear developers,

Previously I worked with QIIME1/2 and DADA2 for 16S data processing. Now I'm testing the CMIWorkshop 16S data (demo dataset) on qiita.

Here I come across 3 questions regarding the data processing on qiita.

  1. How does qiita handle paired-end reads produced with the EMP protocol? Can it join PE reads? If it does, at which step does the joining happen?
  • In QIIME, we join PE reads first, then perform the demultiplexing. However, in qiita, the workflow enters the split_libray directly.
  1. The threshold for the trimming of reads during split_libary is not changeable and the default setting is 3. Is there any particular reason that you set it to 3 for all the analysis and do you think the reads will be qualified enough for analysis?
  • We usually trim off the bases with Phred quality score<20, which allows for 1% chance of error.
  1. Qiita trims the reads after demultiplexing to a certain length. Based on the documentation from qiita (screenshot below), if I set the parameter to 100, it removes the first 100 base pairs. Is it true? Why remove the first 100 bases rather than the 100 bases at the right end? For Illumina sequencing, usually the quality for the right end is not that good.

trim

Your comments and feedbacks will be highly appreciated.

Best regards,
Claire

@antgonza
Copy link
Member

Hi Claire,

Thank you for your detailed question and thank you for sending this question to our recommended support method: email qiita.help@gmail.com. Anyway, replying here simply for completeness; then I will link this response to your other question via email.

  1. Qiita does not join pair reads; however, we might in the future, here the open issue for this feature request - also check the links in point 2 as they might help understand more the implications of joining reads for meta-analysis.
  2. That's correct, users can not change processing parameters as they matter a lot for the generated feature tables; in other words, using different processing parameters might prevent doing meta-analyses; for more information I would suggest:
    a. Checking these reads about meta-analyses
    b. Reading about the reasoning behind those split libraries parameters selections
    c. Other meta-analysis discussions in the QIIME 2 forum, note that you need to be registered to access them: thread 1, thread 2, thread 3, and thread 4
  3. Good catch! That's a mistake, it actually keeps the 100 first base pairs. I'm going to change the title of this issue to highlight that change.

Hope this helps.

@antgonza antgonza changed the title 16S data processing on qiita Fix Trim documentation: it should be keep vs. remove. Sep 10, 2021
antgonza added a commit to antgonza/qiita that referenced this issue Sep 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants