- Pipeline Design:
- CUT&RUN-Flow is built using Nextflow, a powerful domain-specific workflow language built to create flexible and efficient bioinformatics pipelines. Nextflow provides extensive flexibility in utilizing cluster computing environments such as PBS and SLURM, and in automated and compartmentalized handling of dependencies using Conda / Bioconda and Environment Modules.
- In addition to standard local configurations, Nextflow allows handling of dependencies in separated working environments within the same pipeline using Conda or Environment Modules. CnR-flow is pre-configured to acquire and utilize dependencies using conda environments with no additional required setup.CUT&RUN-Flow utilizes UCSC Genome Browser Tools and Samtools for reference library preparation, FastQC for tag quality control, Trimmomatic and kseq_test (CUT&RUN-Tools) for tag trimming, Bowtie2 for tag alignment, Samtools, bedtools and UCSC Genome Browser Tools for alignment manipulation, and MACS2 and/or SEACR for peak calling, as well as their associated language subdependencies of Java, Python2/3, R, and C++.
- Pipeline Features:
One-step reference database prepration using a path (or URL) to a FASTA file.
Ability to specify groups of samples containing both treatment (Ex: H3K4me3) and control (Ex: IgG) antibody groups, with automated association of each control sample with the respective treatment samples during the peak calling step
Built-in normalization protocol to normalize to a sequence library of the user’s choice when spike-in DNA is used in the CUT&RUN Protocol (Optional, includes an E. coli reference genome for utiliziation of E. coli as a spike-in control as described by Meers et. al. (eLife 2019) [see the References section of this documentation])
SLURM, PBS… and many other job scheduling environments enabled natively by Nextflow
Output of memory-efficient CRAM (alignment), bedgraph (genome coverage), and bigWig (genome coverage) file formats
Here is a brief introduction on how to install and get started using the pipeline. For full details, see this documentation.
- Prepare Task Directory:
- Create a task directory, and navigate to it.
$ mkdir ./my_task # (Example) $ cd ./my_task # (Example)
- Install Nextflow (if necessary):
- Download the nextflow executable to your current directory.(You can move the nextflow executable and add to $PATH for future usage)
$ curl -s https://get.nextflow.io | bash # For the following steps, use: nextflow # If nextflow executable on $PATH (assumed) ./nextflow # If running nextflow executable from local directory
- Download and Install CnR-flow:
- Nextflow will download and store the pipeline in the user’s Nextflow info directory (Default:
$ nextflow run RenneLab/CnR-flow --mode initiate
- Configure, Validate, and Test:
- If using Nextflow’s builtin Conda dependency handling (recommended), install miniconda (if necessary). Installation instructionsThe CnR-flow configuration with Conda should then work “out-of-the-box.”If using an alternative configuration, see the Dependency Config section of this documentation for dependency configuration options.Once dependencies have been configured, validate all dependencies:
$ nextflow run CnR-flow --mode validate_allFill the required task input parameters in “nextflow.config” For detailed setup instructions, see the Task Setup section of this documentation Additionally, for usage on a SLURM, PBS, or other cluster systems, configure your system executor, time, and memory settings.
# Configure: $ <vim/nano...> nextflow.config # Task Input, Steps, etc. Configuration #REQUIRED values to enter (all others *should* work as default): # ref_fasta (or some other ref-mode/location) # treat_fastqs (input paired-end fastq[.gz] file paths) # [OR fastq_groups] (mutli-group input paired-end .fastq[.gz] file paths)
- Prepare and Execute Pipeline:
- Prepare your reference databse (and normalization reference) from .fasta[.gz] file(s):
$ nextflow run CnR-flow --mode prep_fastaPerform a test run to check inputs, paramater setup, and process execution:
$ nextflow run CnR-flow --mode dry_runIf satisifed with the pipeline setup, execute the pipeline:
$ nextflow run CnR-flow --mode runFurther documentation on CUT&RUN-Flow components, setup, and usage can be found in this documentation.
- Task Setup
- Pipe Setup
- Example Files