Introduction

CTI/DNAinn is a bioinformatics pipeline for processing DNA sequencing data from the MSKCC panels IMPACT and ACCESS.

Pipeline Steps

1. DNAinn starts from DNAseq data as FastQ files, in the

Structural Variants Calling (SVtorm as stand-alone pipeline also avairable)

1. Calling SVs
   • (Delly)
   • (Gridss)
   • (Manta)
   • (Svaba)
   • (Tiddit)
2. Merging Calls (SURVIVOR)
3. Bed to Interval list (GATK)
4. ReCalling (Gridss)
5. Filtering Calls (SURVIVOR)
6. Annotate SVs (iAnnotateSV)
7. Draw SVs (DrawSV)
8. Check for expected SVs in Controls

9. Present QC for raw reads (MultiQC)

10. Read QC (FastQC)

11. Present QC for raw reads (MultiQC)

Usage

[!NOTE] If you are new to Nextflow and nf-core, please refer to this page on how to set-up Nextflow. Make sure to test your setup with -profile test before running the workflow on actual data.

To run DNAinn follow these steps:

First, prepare the structure of the project, the ideal structure would be like follows:

PROJECT/ ├── 01_data/ │ ├── samples.csv │ ├── SAMPLE1_TUMOUR_R1.fastq.gz │ ├── SAMPLE1_TUMOUR_R2.fastq.gz │ ├── SAMPLE1_NORMAL_R1.fastq.gz │ ├── SAMPLE1_NORMAL_R2.fastq.gz │ ├── SAMPLE2_TUMOUR_R1.fastq.gz │ └── SAMPLE2_TUMOUR_R2.fastq.gz ├── 02_code/ │ └── run_DNAinn.sh ├── 03_outs/ ├── 04_logs/ ├── 05_work/ └── 06_cach/

Note: Any other structure is also possible, just adjust the launching script accordingly.

Second, prepare a samplesheet with your input data that looks as follows:

samples.csv:

csv patient,sample,fastq1,fastq2,tumour,matched PATIENT1,SAMPLE1,/path/to/normal/fastq1/file/SAMPLE1_NORMAL_R1.fastq.gz,/path/to/normal/fastq2/file/SAMPLE1_NORMAL_R2.fastq.gz,false,true PATIENT1,SAMPLE1,/path/to/tumour/fastq1/file/SAMPLE1_TUMOUR_R1.fastq.gz,/path/to/tumour/fastq2/file/SAMPLE1_TUMOUR_R2.fastq.gz,true,true PATIENT2,SAMPLE2,/path/to/tumour/fastq1/file/SAMPLE2_TUMOUR_R1.fastq.gz,/path/to/tumour/fastq2/file/SAMPLE2_TUMOUR_R2.fastq.gz,true,false Each row corresponds to a couple of paired FASTQ files per sample. The matched column indicates whether a matched normal is available (true/false), and the tumour column designates whether the sample is a tumour. If no normal is provided, a default putative normal will be automatically used to support somatic variant calling, structural variant, etc...

Third, now you can run the pipeline using the assets/run_DNAinn.sh script as a template, such script is:

```bash

!/bin/bash

source activate

export NXFLOGFILE="../04logs/nextflow.log" export NXFCACHEDIR="../06cach/nextflow-cache"

nextflow run \ /path/to/DNAinn/main.nf \ --input ../01data/samples.csv \ --outdir ../03outs/ \ --email @mskcc.org \ -profile \ -work-dir ../05work \ --seqlibrary Av2 \ --genome HG19VS \ -resume ```

[!WARNING] Please provide pipeline parameters via the CLI or Nextflow -params-file option. Custom config files including those provided by the -c Nextflow option can be used to provide any configuration except for parameters; see docs.

Credits

DNAinn was originally written by Juan Blanco-Heredia at the Marie-Josée and Henry R. Kravis Center for Molecular Oncology, Technology Innovation Lab, Memorial Sloan Kettering Cancer Center.

Main developer:

• Juan Blanco-Heredia

We thank the following people for their extensive assistance in the development of this pipeline:

• Caryn Hale
• Brian Loomis
• Kanika Arora
• Shivani Guturu

Contributions and Support

If you would like to contribute to this pipeline, please see the contributing guidelines.

Citations

An extensive list of references for the tools used by the pipeline can be found in the CITATIONS.md file.

This pipeline uses code and infrastructure developed and maintained by the nf-core community, reused here under the MIT license.

The nf-core framework for community-curated bioinformatics pipelines.

Philip Ewels, Alexander Peltzer, Sven Fillinger, Harshil Patel, Johannes Alneberg, Andreas Wilm, Maxime Ulysse Garcia, Paolo Di Tommaso & Sven Nahnsen.

Nat Biotechnol. 2020 Feb 13. doi: 10.1038/s41587-020-0439-x.