Skip to content

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

Closed
@clairexu010

Description

@clairexu010

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions