This is an old revision of the document!
Micriobial analysis aims to understand microbes and their functions in their environments. QIIME2 (Quantitative Insights Into Microbial Ecology) is a powerful, extensible, and decentralized microbiome analysis package with a focus on data and analysis transparency. QIIME 2 enables researchers to start an analysis with raw DNA sequence data and finish with publication-quality figures and statistical results.
We outline a pipeline to analyse 16S/18S paired-end sequencing data. Qiime2 can be used to analyse single-end and paired-end data.
Data used and produced by qiime2 are stored as artifacts. Artifacts contain data and metadata and have a
.qza extension. Qiime2 provides methods to view information (data and metadata) stored in artifacts by creating visualizations, that have a
We import raw fastq files into qiime2. Depending on the sequencing platform used to generate the data, you will have data that has been de-multiplexed into sample specif fastq files, or not. The MiSeq platform at BecA-ILRI Hub will de-multiplex the data and we get sample specific fastq files.
Read more about different data types and importing them into qiime2 for anlaysis. We will be importing data described as type Cassava 1.8 paired-end de-multiplexed fastq.
To import fastq files;
#i create a directory to store all my artifact i.e '.qza' and the related visualization i.e '.qzv' files. mkdir /home/mydir/qiime2_data/ #import the fastq files qiime tools import \ --type 'SampleData[PairedEndSequencesWithQuality]' \ --input-path /home/mydir/qiime2_data/ \ --input-format CasavaOneEightSingleLanePerSampleDirFmt \ --output-path /home/mydir/qiime2_data/my_raw_data.qza
We mentioned that qiime2 provides method to summarize and view artifacts by storing them as visualizations, .qzv, files. The
.qzv files can be opened on any browser using qiime viewer. To create visualization for the imported data;
qiime demux summarize \ --i-data /home/mydir/qiime2_data/my_raw_data.qza \ --o-visualization /home/mydir/qiime2_data/my_raw_data.qzv
Qiime2 provides two pluggins/methods for filtering your sequences to the required quality and length.Sequence Variants are then selected from quality filtered data and the results are feature tables better known as OTU tables and the representative feature sequences. These methods are Dada2 and Deblur.
Important to keep in mind is the size of the amplified region covered by the primers used and what is the expected fragment length after read joining? This will determine the trim and truncate length parameters for dada2 and deblur pipelines.
The Dada2 pipeline detects and corrects illumina amplicon sequence data and additionally filter any phiX reads identified in sequencing data and also filter out any chimeric sequences. To see usage and parameters that can be adjusted get the help for the pluggin i.e
qiime dada2 --help
The data we are using is paired-end, hence we will use the qiime dada2 denoise-paired method of the pluggin.
A key parameter to be careful about is the
–p-trunc-q, which is a Q-score value. This means that in filtering for base quality, while reading the sequence from left to right, as soon as it encounters a base with a Q-score lower that threshold, by default its set to 2, the read is truncated at that position.Be careful with this, best to leave it at the default.
The other key parameters in quality control of the sequences are those used to trim the forward,
–p-trunc-len-f and reverse
–p-trunc-len-r reads. The
–p-trim-left-[f/r] tell qiime how many bases to trim from the beginning of the sequence, while the
–p-trunc-len[f|r] tell qiime at what position the sequences should be truncated at the end.
To determine what values to pass for these two parameters;
demux.qzvfile that was generated by
qiime demux summarizeafter importing the data to trim of the poor quality bases.
–p-trunc-len[f|r]. Refer to the expected fragment length for the primers used to prepare the libraries for sequencing. For example if the expected fragment length for your sequences is 465bp, and lets say the insert size during the sequencing was 300bp. We would want to have a final length of at least 465by or more to have better chances of final sequences of full length for the alignment. Considering that more often than not the forward sequences from illumina sequences have better quality than the reverse sequences. We could use a
220. to have a final sequence length of