This workflow will run the TITAN a set of tumour-normal pairs, starting from the BAM files and generating TitanCNA outputs. It will also perform model selection at the end of the workflow to choose the optimal ploidy and clonal cluster solutions.
readCounter
is used.The list of tumour-normal paired samples should be defined in a YAML file. See config/samples.yaml
for an example. Both fields samples
and pairings
must to be provided. pairings
key must match the tumour sample while the value must match the normal sample.
samples:
tumor_sample_1: /path/to/bam/tumor.bam
normal_sample_1: /path/to/bam/normal.bam
pairings:
tumor_sample_1: normal_sample_1
ichorCNA.snakefile
getAlleleCounts.snakefile
TitanCNA.snakefile
Invoking the full snakemake workflow for TITAN
# show commands and workflow
snakemake -s TitanCNA.snakefile -np
# run the workflow locally using 5 cores
snakemake -s TitanCNA.snakefile --cores 5
# run the workflow on qsub using a maximum of 50 jobs. Broad UGER cluster parameters can be set directly in config/cluster.sh.
snakemake -s TitanCNA.snakefile --cluster-sync "qsub" -j 50 --jobscript config/cluster.sh
This will also run both ichorCNA.snakefile
and getAlleleCounts.snakefile
which generate the necessary inputs for TitanCNA.snakfile
.
ichorCNA.snakefile
and getAlleleCounts.snakefile
can also be invoked separately. If only one but not both results are needed, then you can invoke the snakefiles independently.
snakemake -s ichorCNA.snakefile --cores 5
# OR
snakemake -s getAlleleCounts.snakefile --cores 5
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.