Home | BioWDL: BamMetrics

Please be aware that the page you are currently viewing is not for the latest available version!

This workflow can be used to collect a variety of metrics from a BAM file. Metrics are collected using picard and samtools.

This workflow is part of BioWDL developed by the SASC team at Leiden University Medical Center.

Usage

This workflow can be run using Cromwell:

java -jar cromwell-<version>.jar run -i inputs.json bammetrics.wdl

Inputs

Inputs are provided through a JSON file. The minimally required inputs are described below and a template containing all possible inputs can be generated using Womtool as described in the WOMtool documentation. For an overview of all available inputs, see this page.

{
  "BamMetrics.referenceFasta": "The path to the reference fasta file",
  "BamMetrics.referenceFastaFai": "The path to the index for the reference fasta",
  "BamMetrics.referenceFastaDict": "The path to the sequence dictionary dict file for the reference fasta",
  "BamMetrics.bam": "A path to an input BAM file",
  "BamMetrics.bamIndex": "A path to the index of the BAM file."
}

In the case of RNAseq samples tho following inputs are also required. By providing these inputs additional RNAseq metrics will be collected.

{
  "BamMetrics.refRefflat": "A path to a Refflat annotation file for the reference",
  "BamMetrics.strandedness": "The strandedness of an RNAseq sample. This should be on of 'None', 'FR' (forward-reverse) or 'RF' (reverse-forward), defaults to 'None'"
}

For targeted sequencing samples the following inputs are also required. By providing these inputs additional targeted PCR metrics will be collected.

{
  "BamMetrics.targetIntervals": "A list of paths to the bed files containing the target regions",
  "BamMetrics.ampliconIntervals": "The path to the bed file containing the amplicon regions"
}

An output directory can be set using an options.json file. See the cromwell documentation for more information.

Example options.json file:

{
"final_workflow_outputs_dir": "my-analysis-output",
"use_relative_output_paths": true,
"default_runtime_attributes": {
  "docker_user": "$EUID"
  }
}

Alternatively an output directory can be set with BamMetrics.outputDir. BamMetrics.outputDir must be mounted in the docker container. Cromwell will need a custom configuration to allow this.

Example

{
  "BamMetrics.referenceFasta": "/home/user/genomes/human/GRCh38.fasta",
  "BamMetrics.referenceFastaFai": "/home/user/genomes/human/GRCh38.fasta.fai",
  "BamMetrics.referenceFastaDict": "/home/user/genomes/human/GRCh38.dict",
  "BamMetrics.outputDir": "/home/user/analysis/metrics",
  "BamMetrics.bam": "/home/user/mapping/results/s1.bam",
  "BamMetrics.bamIndex": "/home/user/mapping/results/s1.bai",
  "BamMetrics.targetIntervals": [
    "/home/user/analysis/target1.bed",
    "/home/user/analysis/target2.bed"
  ],
  "BamMetrics.ampliconIntervals": "/home/user/analysis/amplicon.bed"
}

Dependency requirements and tool versions

Biowdl pipelines use docker images to ensure reproducibility. This means that biowdl pipelines will run on any system that has docker installed. Alternatively they can be run with singularity.

For more advanced configuration of docker or singularity please check the cromwell documentation on containers.

Images from biocontainers are preferred for biowdl pipelines. The list of default images for this pipeline can be found in the default for the dockerImages input.

Output

A directory containing the various metrics collected.

Contact

For any questions about running this workflow and feature requests, please use the github issue tracker or contact the SASC team directly at: sasc@lumc.nl.