Short-Read Quality Control

Overview

This module is designed to function as both a standalone MAG short-read quality control pipeline as well as a component of the larger CAMP metagenome analysis pipeline. As such, it is both self-contained (ex. instructions included for the setup of a versioned environment, etc.), and seamlessly compatible with other CAMP modules (ex. ingests and spawns standardized input/output config files, etc.).

There are two filtration steps in the module- i) for general poor quality (Phred scores, length, Ns, adapters, polyG/X) and ii) for host reads- followed by a sequencing error correction step. The properties of the QC-ed FastQs are summarized in aggregate by a MultiQC report.

Installation

1. Clone repo from Github.

git clone https://github.com/MetaSUB-CAMP/camp_short-read-quality-control

2. Set up the conda environment using configs/conda/short-read-quality-control.yaml.

# Create and activate conda environment 
cd camp_short-read-quality-control
conda env create -f configs/conda/short-read-quality-control.yaml
conda activate short-read-quality-control

3. Download the appropriate host reference genome(s) and make a Bowtie2 index using bowtie2-build /path/to/host_reference.fa /path/to/host_reference, and add the prefix /path/to/host_reference to parameters.yaml.
   • For example, I downloaded the latest major release of the human reference genome. This is needed for the test run.

wget https://ftp.ncbi.nlm.nih.gov/genomes/all/GCA/000/001/405/GCA_000001405.15_GRCh38/GCA_000001405.15_GRCh38_genomic.fna.gz
bowtie2-build --threads 20 GCA_000001405.15_GRCh38_genomic.fna.gz GCA_000001405.15_GRCh38_genomic

4. Update the relevant parameters (if applicable- for example, location of external non-conda tools, your downloaded databases) in test_data/parameters.yaml.

5. Make sure the installed pipeline works correctly. With 40 threads and a maximum of 150 GB allocated for a command (tadpole), the test dataset should finish in approximately 6 minutes.

# Run tests on the included sample dataset
python /path/to/camp_short-read-quality-control/workflow/short-read-quality-control.py test

Using the Module

Input: /path/to/samples.csv provided by the user.

Output: 1) An output config file summarizing the locations of the error-corrected FastQs, 2) summary statistics about the dataset after each error correction step indicating how many reads and/or bases were pruned, and 3) the MultiQC report summarizing the properties for the QC-ed FastQ. For more information, see the demo test output directory in test_data/test_out.

• /path/to/work/dir/short_read_qc/final_reports/samples.csv for ingestion by the next module

• /path/to/work/dir/short_read_qc/final_reports/read_stats.csv

• Optional: /path/to/work/dir/short_read_qc/final_reports/*_multiqc_report.html, where * is 'pre' or 'post'-module

Module Structure

└── workflow
    ├── Snakefile
    ├── short-read-quality-control.py
    ├── utils.py
    ├── __init__.py
    └── ext/
        └── scripts/

• workflow/short-read-quality-control.py: Click-based CLI that wraps the snakemake and other commands for clean management of parameters, resources, and environment variables.
• workflow/Snakefile: The snakemake pipeline.
• workflow/utils.py: Sample ingestion and work directory setup functions, and other utility functions used in the pipeline and the CLI.
• ext/: External programs, scripts, and small auxiliary files that are not conda-compatible but used in the workflow.

Running the Workflow

1. Make your own samples.csv based on the template in configs/samples.csv.

   • ingest_samples in workflow/utils.py expects Illumina reads in FastQ (may be gzipped) form
   • samples.csv requires either absolute paths or paths relative to the directory that the module is being run in

2. Update the relevant parameters in configs/parameters.yaml.

3. Update the computational resources available to the pipeline in configs/resources.yaml.

Command Line Deployment

To run CAMP on the command line, use the following, where /path/to/work/dir is replaced with the absolute path of your chosen working directory, and /path/to/samples.csv is replaced with your copy of samples.csv. - The default number of cores available to Snakemake is 1 which is enough for test data, but should probably be adjusted to 10+ for a real dataset. - Relative or absolute paths to the Snakefile and/or the working directory (if you're running elsewhere) are accepted! - The parameters and resource config YAMLs can also be customized.

python /path/to/camp_short-read-quality-control/workflow/short-read-quality-control.py \
    (-c number_of_cores_allocated) \
    (-p /path/to/parameters.yaml) \
    (-r /path/to/resources.yaml) \
    -d /path/to/work/dir \
    -s /path/to/samples.csv

Slurm Cluster Deployment

To run CAMP on a job submission cluster (for now, only Slurm is supported), use the following. - --slurm is an optional flag that submits all rules in the Snakemake pipeline as sbatch jobs. - In Slurm mode, the -c flag refers to the maximum number of sbatch jobs submitted in parallel, not the pool of cores available to run the jobs. Each job will request the number of cores specified by threads in configs/resources/slurm.yaml.

sbatch -J jobname -o jobname.log << "EOF"
#!/bin/bash
python /path/to/camp_short-read-quality-control/workflow/short-read-quality-control.py --slurm \
    (-c max_number_of_parallel_jobs_submitted) \
    (-p /path/to/parameters.yaml) \
    (-r /path/to/resources.yaml) \
    -d /path/to/work/dir \
    -s /path/to/samples.csv
EOF

Finishing Up

1. To quality-check the processed FastQs, download and compare the collated MultiQC reports, which can be found at /path/to/work/dir/short_read_qc/final_reports/*_multiqc_report/html. Multiple rounds of preprocessing may be needed to fully get rid of low-quality bases, adapters, and duplicated sequences.

   • For example, the dataset I worked with required an additional round of fastp to trim 10 low-quality bases from the 5' and 4 low-quality bases from the 3' end respectively.
   • I recommend creating a new directory, which I've called /path/to/work/dir/short_read_qc/5_retrimming and placing reprocessed reads inside them.
   • Afterwards, I reran FastQC and MultiQC and collated summary statistics (ex. numbers of reads, etc.) from the reprocessed datasets manually. I also updated the location of the reprocessed reads in /path/to/work/dir/short_read_qc/final_reports/samples.csv to /path/to/work/dir/short_read_qc/5_retrimming.

2. To plot grouped bar graph(s) of the number of reads and bases remaining after each quality control step in each sample, set up the dataviz environment and follow the instructions in the Jupyter notebook:

conda env create -f configs/conda/dataviz.yaml
conda activate dataviz
jupyter notebook &

3. After checking over final_reports/ and making sure you have everything you need, you can delete all intermediate files to save space.

python3 /path/to/camp_short-read-quality-control/workflow/short-read-quality-control.py cleanup \
    -d /path/to/work/dir \
    -s /path/to/samples.csv

4. If for some reason the module keeps failing, CAMP can print a script containing all of the remaining commands that can be run manually.

python3 /path/to/camp_short-read-quality-control/workflow/short-read-quality-control.py --dry_run \
    -d /path/to/work/dir \
    -s /path/to/samples.csv

Credits

• This package was created with Cookiecutter as a simplified version of the project template.
• Free software: MIT
• Documentation: https://camp-documentation.readthedocs.io/en/latest/short-read-quality-control.html