1 Introduction

Users want to provide here background information about the design of their VAR-Seq project.

This report describes the analysis of a VAR-Seq project studying the genetic differences among several strains … from organism ….

1.1 Experimental design

Typically, users want to specify here all information relevant for the analysis of their VAR-Seq study. This includes detailed descriptions of FASTQ files, experimental design, reference genome, gene annotations, etc.

2 Workflow environment

2.1 Generate workflow environment

systemPipeRdata package is a helper package to generate a fully populated systemPipeR workflow environment in the current working directory with a single command. All the instruction for generating the pre-configured workflow templates are provide in the systemPipeRdata vignette.

systemPipeRdata::genWorkenvir(workflow = "varseq", mydirname = "varseq")
setwd("varseq")

This step can be skipped if you already have the environment to run the analysis. If not, you can run it, and it will create the directory structure and populate all the necessary param and demo data files.

After building and loading the workflow environment generated by genWorkenvir from systemPipeRdata all data inputs are stored in a data/ directory and all analysis results will be written to a separate results/ directory, while the systemPipeVARseq.Rmd script and the targets file are expected to be located in the parent directory. The R session is expected to run from this parent directory. Additional parameter files are stored under param/.

To work with real data, users want to organize their own data similarly and substitute all test data for their own data. To rerun an established workflow on new data, the initial targets file along with the corresponding FASTQ files are usually the only inputs the user needs to provide.

For more details, please consult the documentation here. More information about the targets files from systemPipeR can be found here.

2.2 Build the Workflow with a single command

This template provides some common steps for a VARseq workflow. One can add, remove, modify workflow steps by operating on the SYSargsList workflow object. For more details of all the features and utilities, please consult the main vignette.

To initiate a VARseq workflow, this entire Rmarkdown file will be imported as a SYSargsList workflow object, by using the importWF("systemPipeVARseq.Rmd") command.

In this template, code chunks with the option spr = TRUE' will be added to the workflow. Other R code chunks without this option will be ignored. The option eval = FALSE can be ignored when imported and build the workflow object. Please be aware of this possibility.

The template can provide more than one alternative for each step, such as different mapping methods, that will receive the mandatory or optional flag. One can run just the mandatory steps, ALL, or optional steps when running the workflow.

Also, each one of the steps can be run on compute clusters (compute option) or on the current session, here called management session. For the demonstration of this template, a management session will be chosen.

2.3 Workflow initialization

The other alternative is to initialize the workflow and append each of the steps in the workflow object.

sal <- SPRproject()

2.4 Required packages and resources

systemPipeR workflows can be designed and built from start to finish with a single command, importing from an R Markdown file or stepwise in interactive mode from the R console. This tutorial will demonstrate how to build the workflow in an interactive mode, appending each step. The workflow is constructed by connecting each step via appendStep method. Each SYSargsList instance contains instructions needed for processing a set of input files with a specific command-line or R software and the paths to the corresponding outfiles generated by a particular tool/step.

The systemPipeR package needs to be loaded (H Backman and Girke 2016).

appendStep(sal) <- LineWise(code = {
    library(systemPipeR)
}, step_name = "load_SPR")

2.5 FASTQ quality report

The following seeFastq and seeFastqPlot functions generate and plot a series of useful quality statistics for a set of FASTQ files including per cycle quality box plots, base proportions, base-level quality trends, relative k-mer diversity, length, and occurrence distribution of reads, number of reads above quality cutoffs and mean quality distribution. The results are written to a PDF file named fastqReport.pdf.

This is the pre-trimming fastq report. Another post-trimming fastq report step is not included in the default. It is recommended to run this step first to decide whether the trimming is needed.

Please note that initial targets files are being used here. In this case, it has been added to the first step, and later, we used the function getColumn to extract a named vector.

appendStep(sal) <- LineWise(code = {
    targets <- read.delim("targetsPE_varseq.txt", comment.char = "#")
    updateColumn(sal, step = "load_SPR", position = "targetsWF") <- targets
    fq_files <- getColumn(sal, "load_SPR", "targetsWF", column = 1)
    fqlist <- seeFastq(fastq = fq_files, batchsize = 10000, klength = 8)
    pdf("./results/fastqReport_pre.pdf", height = 18, width = 4 *
        length(fqlist))
    seeFastqPlot(fqlist)
    dev.off()
}, step_name = "fastq_report_pre", dependency = "load_SPR")
Figure 1: FASTQ quality report for 18 samples


2.6 Read preprocessing

2.6.1 Read trimming with Trimmomatic

Next, we need to populate the object created with the first step in the workflow. Here, an example of how to perform this task using parameters template files for trimming FASTQ files with Trimmomatic software (Bolger, Lohse, and Usadel 2014). For this step, the SYSargsList function has been used to build the command-line and append to sal object. For more details of all the features and utilities, please consult the main vignette.

If GATK (default) is used for variant calling, any type of fastq trimming is strongly depreciated. GATK have internal function to handle low quality posistions.

appendStep(sal) <- SYSargsList(step_name = "trimmomatic", targets = "targetsPE_varseq.txt",
    wf_file = "trimmomatic/trimmomatic-pe.cwl", input_file = "trimmomatic/trimmomatic-pe.yml",
    dir_path = "param/cwl", inputvars = c(FileName1 = "_FASTQ_PATH1_",
        FileName2 = "_FASTQ_PATH2_", SampleName = "_SampleName_"),
    dependency = c("fastq_report_pre"), run_step = "optional")

2.6.2 Preprocessing with preprocessReads function

The function preprocessReads allows to apply predefined or custom read preprocessing functions to all FASTQ files referenced in a SYSargsList container, such as quality filtering or adaptor trimming routines. Internally, preprocessReads uses the FastqStreamer function from the ShortRead package to stream through large FASTQ files in a memory-efficient manner. The following example performs adaptor trimming with the trimLRPatterns function from the Biostrings package.

Here, we are appending this step at the SYSargsList object created previously. All the parameters are defined on the preprocessReads/preprocessReads-pe.yml file.

appendStep(sal) <- SYSargsList(step_name = "preprocessing", targets = "targetsPE_varseq.txt",
    dir = TRUE, wf_file = "preprocessReads/preprocessReads-pe.cwl",
    input_file = "preprocessReads/preprocessReads-pe.yml", dir_path = "param/cwl",
    inputvars = c(FileName1 = "_FASTQ_PATH1_", FileName2 = "_FASTQ_PATH2_",
        SampleName = "_SampleName_"), dependency = c("fastq_report_pre"),
    run_step = "optional")

After the trimming step, the outfiles files can be used to generate the new targets files containing the paths to the trimmed FASTQ files. The new targets information can be used for the next workflow step instance, e.g. running the NGS alignments with the trimmed FASTQ files.

The following example shows how one can design a custom read ‘preprocessReads’ function using utilities provided by the ShortRead package, and then run it in batch mode with the ‘preprocessReads’ function. For here, it is possible to replace the function used on the preprocessing step and modify the sal object. Because it is a custom function, it is necessary to save the part in the R object, and internally the preprocessReads.doc.R is loading the function. If the R object is saved with a different name (here "param/customFCT.RData"), please replace that accordingly in the preprocessReads.doc.R.

Please, note that this step is not added to the workflow, here just for demonstration.

First, we defined the function in the workflow:

appendStep(sal) <- LineWise(code = {
    filterFct <- function(fq, cutoff = 20, Nexceptions = 0) {
        qcount <- rowSums(as(quality(fq), "matrix") <= cutoff,
            na.rm = TRUE)
        # Retains reads where Phred scores are >= cutoff
        # with N exceptions
        fq[qcount <= Nexceptions]
    }
    save(list = ls(), file = "param/customFCT.RData")
}, step_name = "custom_preprocessing_function", dependency = "preprocessing")

After, we can edit the input parameter:

yamlinput(sal, "preprocessing")$Fct
yamlinput(sal, "preprocessing", "Fct") <- "'filterFct(fq, cutoff=20, Nexceptions=0)'"
yamlinput(sal, "preprocessing")$Fct  ## check the new function
cmdlist(sal, "preprocessing", targets = 1)  ## check if the command line was updated with success

2.7 FASTQ quality after Trimming

This is the post-trimming fastq quality report. If the trimming step is included, it is recommended to add this step to compare trimming of fastq before and after.

appendStep(sal) <- LineWise(code = {
    fq_files <- getColumn(sal, "preprocessing", "outfiles", column = 1)  ## get outfiles path
    fqlist <- seeFastq(fastq = fq_files, batchsize = 10000, klength = 8)
    pdf("./results/fastqReport_pos.pdf", height = 18, width = 4 *
        length(fqlist))
    seeFastqPlot(fqlist)
    dev.off()
}, step_name = "fastq_report_pos", dependency = "trimmomatic",
    run_step = "optional")

2.8 Read mapping with BWA-MEM

The NGS reads of this project are aligned against the reference genome sequence using the highly variant tolerant short read aligner BWA-MEM (Li 2013; Li and Durbin 2009). The parameter settings of the aligner are defined in the param/cwl/gatk/bwa-pe.cwl.

This test code uses untrimmed fastq files since the demo data is minimal and limited. However, it is best to test with FASTQ quality report function provided above to verify your real data first.

2.8.1 Build index and dictionary files for BWA and GATK

Build the index and dictionary files for BWA and GATK to run.

appendStep(sal) <- SYSargsList(step_name = "bwa_index", dir = FALSE,
    targets = NULL, wf_file = "gatk/workflow_bwa-index.cwl",
    input_file = "gatk/gatk.yaml", dir_path = "param/cwl", dependency = "load_SPR")

Create reference fasta dictionary.

appendStep(sal) <- SYSargsList(step_name = "fasta_index", dir = FALSE,
    targets = NULL, wf_file = "gatk/workflow_fasta_dict.cwl",
    input_file = "gatk/gatk.yaml", dir_path = "param/cwl", dependency = "bwa_index")

Create dictionary index.

appendStep(sal) <- SYSargsList(step_name = "faidx_index", dir = FALSE,
    targets = NULL, wf_file = "gatk/workflow_fasta_faidx.cwl",
    input_file = "gatk/gatk.yaml", dir_path = "param/cwl", dependency = "fasta_index")

2.8.2 Mapping reads with BWA

appendStep(sal) <- SYSargsList(step_name = "bwa_alignment", targets = "targetsPE_varseq.txt",
    wf_file = "gatk/workflow_bwa-pe.cwl", input_file = "gatk/gatk.yaml",
    dir_path = "param/cwl", inputvars = c(FileName1 = "_FASTQ_PATH1_",
        FileName1 = "_FASTQ_PATH2_", SampleName = "_SampleName_"),
    dependency = c("faidx_index"))

2.9 Read and alignment stats

The following provides an overview of the number of reads in each sample and how many of them aligned to the reference.

appendStep(sal) <- LineWise(code = {
    bampaths <- getColumn(sal, step = "bwa_alignment", "outfiles",
        column = "samtools_sort_bam")
    fqpaths <- getColumn(sal, step = "bwa_alignment", "targetsWF",
        column = "FileName1")
    read_statsDF <- alignStats(args = bampaths, fqpaths = fqpaths,
        pairEnd = TRUE)
    write.table(read_statsDF, "results/alignStats.xls", row.names = FALSE,
        quote = FALSE, sep = "\t")
}, step_name = "align_stats", dependency = "bwa_alignment", run_step = "optional")

2.11 Variant calling

The following performs variant calling with GATK and BCFtools on a single machine by runWF function for each sample sequentially. If a cluster compute is available, running in parallel mode on a compute cluster can be performed by runWF, making available the resources and choose run_session = "compute".

Not all users have a cluster system, so here to demonstrate an example of variant calling workflow, only single-machine commands are shown. For cluster jobs, please refer to our main vignette.

In addition, the user would choose only one variant caller here rather than running several ones. However, the workflow manager allows keeping multiple options available for running the analysis.

2.11.1 Variant calling with GATK

The following steps are based on GATK 4.1.1.0 Best Practice. There are 10 individual steps where the user can choose where to jump in and where to skip. All scripts are located at param/cwl/gatk. BQSR (Base Quality Score Recalibration) and VQSR (Variant Quality Score Recalibration) are very specific to a limited species like human, so this workflow does not support these steps.

2.11.2 Step1: fastq to ubam

Convert fastq files to bam files to prepare for the following step. It is very important to specific your sequencing platform, default is illumina. User need to change param/cwl/gatk/gatk_fastq2ubam.cwl if the platform is different. Platform information is needed for the variant caller in later steps to correct calling parameters.

appendStep(sal) <- SYSargsList(step_name = "fastq2ubam", targets = "targetsPE_varseq.txt",
    wf_file = "gatk/workflow_gatk_fastq2ubam.cwl", input_file = "gatk/gatk.yaml",
    dir_path = "param/cwl", inputvars = c(FileName1 = "_FASTQ_PATH1_",
        FileName2 = "_FASTQ_PATH2_", SampleName = "_SampleName_"),
    dependency = c("faidx_index"))

2.11.3 Step2: Merge bam and ubam

This step merges a bam and ubam and creates a third bam file that contains alignment information and remaining information that was removed by the aligner like BWA. The removed information is essential for variant statistics calculation. Previous steps are recommended, but variant calling can still be performed without these steps.

appendStep(sal) <- SYSargsList(step_name = "merge_bam", targets = c("bwa_alignment",
    "fastq2ubam"), wf_file = "gatk/workflow_gatk_mergebams.cwl",
    input_file = "gatk/gatk.yaml", dir_path = "param/cwl", inputvars = c(bwa_men_sam = "_bwasam_",
        ubam = "_ubam_", SampleName = "_SampleName_"), rm_targets_col = c("preprocessReads_1",
        "preprocessReads_2"), dependency = c("bwa_alignment",
        "fastq2ubam"))

2.11.4 Step3: Sort bam files by genomic coordinates

Sort bam files by genomic coordinates.

appendStep(sal) <- SYSargsList(step_name = "sort", targets = "merge_bam",
    wf_file = "gatk/workflow_gatk_sort.cwl", input_file = "gatk/gatk.yaml",
    dir_path = "param/cwl", inputvars = c(merge_bam = "_mergebam_",
        SampleName = "_SampleName_"), rm_targets_col = c("bwa_men_sam",
        "ubam", "SampleName_fastq2ubam", "Factor_fastq2ubam",
        "SampleLong_fastq2ubam", "Experiment_fastq2ubam", "Date_fastq2ubam"),
    dependency = c("merge_bam"))

2.11.5 Step4: Mark duplicates

Mark PCR artifacts in sequencing. A duplicate_metrics file will also be produced by this step, but will not be used for the next step. This file is just for the user to check duplicates status summary.

appendStep(sal) <- SYSargsList(step_name = "mark_dup", targets = "sort",
    wf_file = "gatk/workflow_gatk_markduplicates.cwl", input_file = "gatk/gatk.yaml",
    dir_path = "param/cwl", inputvars = c(sort_bam = "_sort_",
        SampleName = "_SampleName_"), rm_targets_col = c("merge_bam"),
    dependency = c("sort"))

2.11.6 Step5: Fixing tags

Takes the bam from the last step and calculates the NM, MD, and UQ tags. These tags are important for variant calling and filtering. This step is recommended but can be skipped.

appendStep(sal) <- SYSargsList(step_name = "fix_tag", targets = "mark_dup",
    wf_file = "gatk/workflow_gatk_fixtag.cwl", input_file = "gatk/gatk.yaml",
    dir_path = "param/cwl", inputvars = c(mark_bam = "_mark_",
        SampleName = "_SampleName_"), rm_targets_col = c("sort_bam"),
    dependency = c("mark_dup"))

Up till this step, sample preprocess is done. All analysis ready BAM files and their index .bai files are created. Individual and cohort calling by HaplotypeCaller is performed from the next step.

2.11.7 Step6: HaplotypeCaller gvcf

The HaplotypeCaller is running a gvcf mode in this step. G stands for ‘genomic’. The file not only contains variant sites information but also non-variant sites information; thus, at the following step, the cohort caller can use this information to validate the true variants.

appendStep(sal) <- SYSargsList(step_name = "hap_caller", targets = "fix_tag",
    wf_file = "gatk/workflow_gatk_haplotypecaller.cwl", input_file = "gatk/gatk.yaml",
    dir_path = "param/cwl", inputvars = c(fixtag_bam = "_fixed_",
        SampleName = "_SampleName_"), rm_targets_col = c("mark_bam"),
    dependency = c("fix_tag"))

2.11.8 Step7: Import all gvcfs

It is recommended to import all gvcfs to a TileDB database for fast cohort variant calling at the following step. Note: if you are working with non-diploid data, use CombineGVCFs function from GATK and change the gvcf_db_folder parameter in param/cwl/gatk/gatk.yaml to be your combined gvcf file path.

Important: Make sure all samples’ *.g.vcf.gz files are in the results folder, also the tbi index files also should be there.

appendStep(sal) <- SYSargsList(step_name = "import", targets = NULL,
    dir = FALSE, wf_file = "gatk/workflow_gatk_genomicsDBImport.cwl",
    input_file = "gatk/gatk.yaml", dir_path = "param/cwl", dependency = c("hap_caller"))

2.11.9 Step8: Cohort calling of gvcf

Assess variants by information from all gvcfs. A collective vcf called samples.vcf.gz is created by default naming.

appendStep(sal) <- SYSargsList(step_name = "call_variants", targets = NULL,
    dir = FALSE, wf_file = "gatk/workflow_gatk_genotypeGVCFs.cwl",
    input_file = "gatk/gatk.yaml", dir_path = "param/cwl", dependency = c("import"))

2.11.10 Step9: Cohort hard filter variants

Variant Quality Score Recalibration (VQSR) is not included in this workflow. Variants are hard filtered together. See this Post for parameters for hard filtering. Change these settings in param/cwl/gak/gatk_variantFiltration.sh if needed. VQSR requires a large quantity of samples to be training data before you can do filtering. Read this post for more information.

appendStep(sal) <- SYSargsList(step_name = "filter", targets = NULL,
    dir = FALSE, wf_file = "gatk/workflow_gatk_variantFiltration.cwl",
    input_file = "gatk/gatk.yaml", dir_path = "param/cwl", dependency = c("call_variants"))

2.11.11 Step10: Extract variant

After cohort calling, filtering, all variants for all samples are stored in one big file. Extract variants for each sample and save them separately (only variants that have passed the filters are stored).

appendStep(sal) <- SYSargsList(step_name = "create_vcf", targets = "hap_caller",
    wf_file = "gatk/workflow_gatk_select_variant.cwl", input_file = "gatk/gatk.yaml",
    dir_path = "param/cwl", inputvars = c(SampleName = "_SampleName_"),
    dependency = c("hap_caller", "filter"))

2.12 Variant calling with BCFtools

Alternative option with BCFtool:

The following runs the variant calling with BCFtools. This tool takes BWA aligned BAM files, sort, mark duplicates by samtools and finally call variants by BCFtools. For legacy reasons we keep this option.

appendStep(sal) <- SYSargsList(step_name = "create_vcf_BCFtool",
    targets = "bwa_alignment", dir = TRUE, wf_file = "workflow-bcftools/workflow_bcftools.cwl",
    input_file = "workflow-bcftools/bcftools.yml", dir_path = "param/cwl",
    inputvars = c(bwa_men_sam = "_bwasam_", SampleName = "_SampleName_"),
    rm_targets_col = c("preprocessReads_1", "preprocessReads_2"),
    dependency = "bwa_alignment", run_step = "optional")

Variant calling ends here. Downstream analysis starts from the next section.

2.13 Inspect VCF file

Scripts of downstream analysis are stored in param/cwl/varseq_downstream.

optional: This step is not included in the default workflow. After successfully execute the entire workflow, users may load individual vcf files to R for other analysis like below.

VCF files can be imported into R with the readVcf function. Both VCF and VRanges objects provide convenient data structure for working with variant data (e.g. SNP quality filtering).

This step is not included in the default workflow steps, but can be useful to inspect individual sample’s raw variants.

library(VariantAnnotation)
vcf_raw <- getColumn(sal, "create_vcf")
vcf <- readVcf(vcf_raw[1], "A. thaliana")
vcf
vr <- as(vcf, "VRanges")
vr

2.14 Filter variants

The function filterVars filters VCF files based on user definable quality parameters. It sequentially imports each VCF file into R, applies the filtering on an internally generated VRanges object and then writes the results to a new subsetted VCF file. The filter parameters are passed on to the corresponding argument as a character string. The function applies this filter to the internally generated VRanges object using the standard subsetting syntax for two dimensional objects such as: vr[filter, ].

2.14.1 Filter variants called by GATK

The below example filters for variants that are supported by >=x reads and >=80% of them support the called variants. In addition, all variants need to pass >=x of the soft filters recorded in the VCF files generated by GATK. Since the toy data used for this workflow is very small, the chosen settings are unreasonabley relaxed. A more reasonable filter setting is given in the line below (here commented out).

There is already some cohort filtering in GATK step 10. Some additional hard filtering is provided here. Apply if you need or skip this step.

appendStep(sal) <- LineWise(code = {
    vcf_raw <- getColumn(sal, "create_vcf")
    library(VariantAnnotation)
    filter <- "totalDepth(vr) >= 2 & (altDepth(vr) / totalDepth(vr) >= 0.8)"
    vcf_filter <- suppressWarnings(filterVars(vcf_raw, filter,
        organism = "A. thaliana", out_dir = "results/vcf_filter"))
    # updateColumn(sal, 'create_vcf',
    # data.frame(vcf_filter=vcf_filter))
}, step_name = "filter_vcf", dependency = "create_vcf", run_step = "optional")

For real samples, use following filters: filter <- "totalDepth(vr) >= 20 & (altDepth(vr) / totalDepth(vr) >= 0.8)"

2.14.2 Filter variants called by BCFtools

The following shows how to filter the VCF files generated by BCFtools using similar parameter settings as in the previous filtering of the GATK results.

appendStep(sal) <- LineWise(code = {
    vcf_raw <- getColumn(sal, "create_vcf_BCFtool")
    library(VariantAnnotation)
    filter <- "totalDepth(vr) >= 2 & (altDepth(vr) / totalDepth(vr) >= 0.8)"
    vcf_filter <- suppressWarnings(filterVars(vcf_raw, filter,
        organism = "A. thaliana", out_dir = "results/vcf_filter_BCFtools"))
    # updateColumn(sal, 'create_vcf',
    # data.frame(vcf_filter=vcf_filter))
}, step_name = "filter_vcf_BCFtools", dependency = "create_vcf_BCFtool",
    run_step = "optional")

Check filtering outcome for one sample

This mini step can be used to compare vcfs files before and after filtering. This can be used once the workflow has been run, and make sure “filter_vcf” is done, since it is an optional step.

copyEnvir(sal, "vcf_raw", globalenv())
copyEnvir(sal, "vcf_filter", globalenv())
length(as(readVcf(vcf_raw[1], genome = "Ath"), "VRanges")[, 1])
length(as(readVcf(vcf_filter[1], genome = "Ath"), "VRanges")[,
    1])

2.15 Annotate filtered variants

The function variantReport generates a variant report using utilities provided by the VariantAnnotation package. The report for each sample is written to a tabular file containing genomic context annotations (e.g. coding or non-coding SNPs, amino acid changes, IDs of affected genes, etc.) along with confidence statistics for each variant. The CWL file param/cwl/varseq_downstream/annotate.cwl defines the paths to the input and output files which are stored in a SYSargs2 instance.

2.15.1 Basics of annotating variants

This step can be run after running the default workflow, not included in the default.

Variants overlapping with common annotation features can be identified with locateVariants.

library("GenomicFeatures")
# comment the next line if optional step 'filter_vcf' is
# included
vcf_filter <- getColumn(sal, "create_vcf")
# uncomment the next line if optional step 'filter_vcf' is
# included copyEnvir(sal, 'vcf_filter', globalenv())
txdb <- loadDb("./data/tair10.sqlite")
vcf <- readVcf(vcf_filter[1], "A. thaliana")
locateVariants(vcf, txdb, CodingVariants())

Synonymous/non-synonymous variants of coding sequences are computed by the predictCoding function for variants overlapping with coding regions.

fa <- FaFile("data/tair10.fasta")
predictCoding(vcf, txdb, seqSource = fa)

2.15.2 Annotate filtered variants GATK or BCFtools

required

appendStep(sal) <- LineWise(code = {
    # comment the next line if optional step 'filter_vcf'
    # is included
    vcf_filter <- getColumn(sal, "create_vcf")
    # uncomment the next line if optional step 'filter_vcf'
    # is included copyEnvir(sal, 'vcf_filter', globalenv())
    library("GenomicFeatures")
    txdb <- loadDb("./data/tair10.sqlite")
    fa <- FaFile("data/tair10.fasta")
    vcf_anno <- suppressMessages(suppressWarnings(variantReport(vcf_filter,
        txdb = txdb, fa = fa, organism = "A. thaliana", out_dir = "results/vcf_anno")))
}, step_name = "annotate_vcf", dependency = "create_vcf")

View annotation result for single sample

copyEnvir(sal, "vcf_anno", globalenv())
read.delim(vcf_anno[1])[38:40, ]

2.16 Combine annotation results among samples

To simplify comparisons among samples, the combineVarReports function combines all variant annotation reports referenced in a SYSargs2 instance (here args). At the same time the function allows to consider only certain feature types of interest. For instance, the below setting filtercol=c(Consequence="nonsynonymous") will include only nonsysynonymous variances listed in the Consequence column of the annotation reports. To omit filtering, one can use the setting filtercol="All".

2.16.1 Combine results

required

appendStep(sal) <- LineWise(code = {
    combineDF <- combineVarReports(vcf_anno, filtercol = c(Consequence = "nonsynonymous"))
    write.table(combineDF, "./results/combineDF_nonsyn.tsv",
        quote = FALSE, row.names = FALSE, sep = "\t")
}, step_name = "combine_var", dependency = "annotate_vcf")

2.17 Summary statistics of variants

The varSummary function counts the number of variants for each feature type included in the annotation reports.

2.18 Summary of variants

required

appendStep(sal) <- LineWise(code = {
    write.table(varSummary(vcf_anno), "./results/variantStats.tsv",
        quote = FALSE, col.names = NA, sep = "\t")
}, step_name = "summary_var", dependency = "combine_var")

2.19 Venn diagram of variants

Optional but included in the default

The venn diagram utilities defined by the systemPipeR package can be used to identify common and unique variants reported for different samples and/or variant callers. The below generates a 3-way venn diagram comparing 3 samples for each of the two variant callers.

appendStep(sal) <- LineWise(code = {
    ## make a list of first three samples
    varlist <- sapply(names(vcf_anno[1:3]), function(x) as.character(read.delim(vcf_anno[x])$VARID))
    vennset <- overLapper(varlist, type = "vennsets")
    pdf("./results/vennplot_var.pdf")
    vennPlot(list(vennset), mymain = "Venn Plot of First 3 Samples",
        mysub = "", colmode = 2, ccol = c("red", "blue"))
    dev.off()
}, step_name = "venn_diagram", dependency = "annotate_vcf")
Figure 2: Venn Diagram for 3 samples from GATK and BCFtools


2.20 Plot variants programmatically

Optional but included in default

The following plots a selected variant with ggbio.

In this example, the input BAM file is from the GATK step 5, analysis ready bam. You can use other aligned BAMs as well, but make sure they are indexed. The VCF file is taken from Inspect VCF file section or you can load your own vcf.

appendStep(sal) <- LineWise(code = {
    # comment the next line if optional step 'filter_vcf'
    # is included
    vcf_filter <- getColumn(sal, "create_vcf")
    # uncomment the next line if optional step 'filter_vcf'
    # is included copyEnvir(sal, 'vcf_filter', globalenv())
    library(ggbio)
    library(VariantAnnotation)
    mychr <- "ChrM"
    mystart <- 19000
    myend <- 21000
    bams <- getColumn(sal, "fix_tag")
    vcf <- suppressWarnings(readVcf(vcf_filter["M6B"], "A. thaliana"))
    ga <- readGAlignments(bams["M6B"], use.names = TRUE, param = ScanBamParam(which = GRanges(mychr,
        IRanges(mystart, myend))))
    p1 <- autoplot(ga, geom = "rect")
    p2 <- autoplot(ga, geom = "line", stat = "coverage")
    p3 <- autoplot(vcf[seqnames(vcf) == mychr], type = "fixed") +
        xlim(mystart, myend) + theme(legend.position = "none",
        axis.text.y = element_blank(), axis.ticks.y = element_blank())
    p4 <- autoplot(loadDb("./data/tair10.sqlite"), which = GRanges(mychr,
        IRanges(mystart, myend)), names.expr = "gene_id")
    p1_4 <- tracks(Reads = p1, Coverage = p2, Variant = p3, Transcripts = p4,
        heights = c(0.3, 0.2, 0.1, 0.35)) + ylab("")
    ggbio::ggsave(p1_4, filename = "./results/plot_variant.png",
        units = "in")
}, step_name = "plot_variant", dependency = "create_vcf")
Figure 3: Plot variants with programmatically.


2.21 Version Information

sessionInfo()
## R version 4.1.3 (2022-03-10)
## Platform: x86_64-pc-linux-gnu (64-bit)
## Running under: Ubuntu 20.04.4 LTS
## 
## Matrix products: default
## BLAS:   /home/biocbuild/bbs-3.14-bioc/R/lib/libRblas.so
## LAPACK: /home/biocbuild/bbs-3.14-bioc/R/lib/libRlapack.so
## 
## locale:
##  [1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C              
##  [3] LC_TIME=en_GB              LC_COLLATE=C              
##  [5] LC_MONETARY=en_US.UTF-8    LC_MESSAGES=en_US.UTF-8   
##  [7] LC_PAPER=en_US.UTF-8       LC_NAME=C                 
##  [9] LC_ADDRESS=C               LC_TELEPHONE=C            
## [11] LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C       
## 
## attached base packages:
## [1] stats4    stats     graphics  grDevices utils    
## [6] datasets  methods   base     
## 
## other attached packages:
##  [1] systemPipeRdata_1.22.3      systemPipeR_2.0.8          
##  [3] ShortRead_1.52.0            GenomicAlignments_1.30.0   
##  [5] SummarizedExperiment_1.24.0 Biobase_2.54.0             
##  [7] MatrixGenerics_1.6.0        matrixStats_0.61.0         
##  [9] BiocParallel_1.28.3         Rsamtools_2.10.0           
## [11] Biostrings_2.62.0           XVector_0.34.0             
## [13] GenomicRanges_1.46.1        GenomeInfoDb_1.30.1        
## [15] IRanges_2.28.0              S4Vectors_0.32.4           
## [17] BiocGenerics_0.40.0         BiocStyle_2.22.0           
## 
## loaded via a namespace (and not attached):
##  [1] sass_0.4.1             jsonlite_1.8.0        
##  [3] bslib_0.3.1            assertthat_0.2.1      
##  [5] BiocManager_1.30.16    latticeExtra_0.6-29   
##  [7] GenomeInfoDbData_1.2.7 yaml_2.3.5            
##  [9] remotes_2.4.2          pillar_1.7.0          
## [11] lattice_0.20-45        glue_1.6.2            
## [13] digest_0.6.29          RColorBrewer_1.1-3    
## [15] colorspace_2.0-3       htmltools_0.5.2       
## [17] Matrix_1.4-1           pkgconfig_2.0.3       
## [19] bookdown_0.25          zlibbioc_1.40.0       
## [21] purrr_0.3.4            scales_1.1.1          
## [23] jpeg_0.1-9             tibble_3.1.6          
## [25] generics_0.1.2         ggplot2_3.3.5         
## [27] ellipsis_0.3.2         cli_3.2.0             
## [29] magrittr_2.0.3         crayon_1.5.1          
## [31] evaluate_0.15          fansi_1.0.3           
## [33] hwriter_1.3.2.1        tools_4.1.3           
## [35] formatR_1.12           lifecycle_1.0.1       
## [37] stringr_1.4.0          munsell_0.5.0         
## [39] DelayedArray_0.20.0    compiler_4.1.3        
## [41] jquerylib_0.1.4        rlang_1.0.2           
## [43] grid_4.1.3             RCurl_1.98-1.6        
## [45] htmlwidgets_1.5.4      bitops_1.0-7          
## [47] rmarkdown_2.13         gtable_0.3.0          
## [49] codetools_0.2-18       DBI_1.1.2             
## [51] R6_2.5.1               knitr_1.38            
## [53] dplyr_1.0.8            fastmap_1.1.0         
## [55] utf8_1.2.2             stringi_1.7.6         
## [57] parallel_4.1.3         vctrs_0.4.0           
## [59] png_0.1-7              tidyselect_1.1.2      
## [61] xfun_0.30

3 Running workflow

3.1 Interactive job submissions in a single machine

For running the workflow, runWF function will execute all the steps store in the workflow container. The execution will be on a single machine without submitting to a queuing system of a computer cluster.

sal <- runWF(sal)

3.2 Parallelization on clusters

Alternatively, the computation can be greatly accelerated by processing many files in parallel using several compute nodes of a cluster, where a scheduling/queuing system is used for load balancing.

The resources list object provides the number of independent parallel cluster processes defined under the Njobs element in the list. The following example will run 18 processes in parallel using each 4 CPU cores. If the resources available on a cluster allow running all 18 processes at the same time, then the shown sample submission will utilize in a total of 72 CPU cores.

Note, runWF can be used with most queueing systems as it is based on utilities from the batchtools package, which supports the use of template files (*.tmpl) for defining the run parameters of different schedulers. To run the following code, one needs to have both a conffile (see .batchtools.conf.R samples here) and a template file (see *.tmpl samples here) for the queueing available on a system. The following example uses the sample conffile and template files for the Slurm scheduler provided by this package.

The resources can be appended when the step is generated, or it is possible to add these resources later, as the following example using the addResources function:

resources <- list(conffile=".batchtools.conf.R",
                  template="batchtools.slurm.tmpl", 
                  Njobs=18, 
                  walltime=120, ## minutes
                  ntasks=1,
                  ncpus=4, 
                  memory=1024, ## Mb
                  partition = "short"
                  )
sal <- addResources(sal, c("hisat2_mapping"), resources = resources)
sal <- runWF(sal)

3.3 Visualize workflow

systemPipeR workflows instances can be visualized with the plotWF function.

plotWF(sal, rstudio = TRUE)

3.4 Checking workflow status

To check the summary of the workflow, we can use:

sal
statusWF(sal)

3.5 Accessing logs report

systemPipeR compiles all the workflow execution logs in one central location, making it easier to check any standard output (stdout) or standard error (stderr) for any command-line tools used on the workflow or the R code stdout.

sal <- renderLogs(sal)

4 Funding

This project was supported by funds from the National Institutes of Health (NIH) and the National Science Foundation (NSF).

References

Bolger, Anthony M, Marc Lohse, and Bjoern Usadel. 2014. “Trimmomatic: A Flexible Trimmer for Illumina Sequence Data.” Bioinformatics 30 (15): 2114–20.

H Backman, Tyler W, and Thomas Girke. 2016. “systemPipeR: NGS workflow and report generation environment.” BMC Bioinformatics 17 (1): 388. https://doi.org/10.1186/s12859-016-1241-0.

Li, H, and R Durbin. 2009. “Fast and Accurate Short Read Alignment with Burrows-Wheeler Transform.” Bioinformatics 25 (14): 1754–60. https://doi.org/10.1093/bioinformatics/btp324.

Li, Heng. 2013. “Aligning Sequence Reads, Clone Sequences and Assembly Contigs with BWA-MEM.” arXiv [Q-bio.GN], March. http://arxiv.org/abs/1303.3997.