Skip to main content

Included Pipelines

This page summarizes the analysis pipelines CBIcall can launch and the backend combinations currently supported.

ConceptYAML keyMeaning
PipelinepipelineThe analysis family: wes, wgs, mit, or a registered external pipeline such as sarek.
ModemodeThe run shape, usually single or cohort.
Workflow backendworkflow_backendThe execution technology: Bash, Snakemake, Nextflow, or Cromwell.
Workflow providerworkflow_providerWho supplies the implementation: cbicall for native CBIcall pipelines, nf-core for registered external provider entries.

A pipeline implementation is native when it produces the CBIcall output contract: standard run directory, logs, reports, output inventory, and final-output fingerprints when available. External provider entries can still be launched and audited by CBIcall, but they keep their upstream output layout and runtime assumptions.

Pipeline Guides

GoalPage
Process one WES/WGS sample from FASTQWES/WGS Single-Sample
Joint-genotype a WES/WGS cohort from gVCFsWES/WGS Cohort
Run mitochondrial variant callingmtDNA
Run selected external nf-core provider entriesExternal nf-core

For a backend-centered view, see Native Backends.

Backend-native validation

CBIcall validates the parameters YAML against the workflow registry and resource catalog, then writes a cbicall-execution-contract.json for the concrete command it launches. Syntax or semantic validation inside each workflow language remains backend-native: use bash -n, Snakemake lint/dry-run checks, Nextflow validation, or womtool validate for WDL/Cromwell workflows.

Compatibility Matrix

Native CBIcall workflows

PipelineModeGenomeSoftware stackBashSnakemakeNextflowCromwell
WESsingleb37gatk-3.5, gatk-4.6Vgatk-4.6gatk-4.6gatk-4.6
WEScohortb37gatk-3.5, gatk-4.6Vgatk-4.6gatk-4.6gatk-4.6
WGSsingleb37, hg38gatk-4.6VVVgatk-4.6
WGScohortb37, hg38gatk-4.6VVVgatk-4.6
mtDNAsinglersrsgatk-3.5VXXX
mtDNAcohortrsrsgatk-3.5VXXX

CBIcall does not ship a validated gatk-3.5 WGS workflow; native WGS support is provided through the gatk-4.6 stack.

mtDNA platform limitation

The bundled mtDNA workflow is not supported on ARM / aarch64 because of legacy third-party dependencies.

Registered external workflows

PipelineModeRegistry sourceReleaseResource model
demosinglenf-core/demo1.1.0Nextflow/nf-core managed
sarekcohortnf-core/sarek3.8.1Nextflow/nf-core managed