Template instructions:

This template is designed to be a stripped down version of the nf-core template. It is intended as an intermediate-level template with some of the more advanced features of the nf-core template removed and certain files consolidated. It is intended to be used as a starting point for creating a new pipeline. You can read more about this template in my blog post here.

Template Naming

• [ ] Replace all instances of simplenextflow with the name of your pipeline
• [ ] Replace all instances of kenibrewer with your GitHub username/organization

Samplesheet handling

• [ ] Modify bin/check_samplesheet.py to check your samplesheet for errors
• [ ] Modify the process modules/local/samplesheet_check.nf check for the existence of any paths in your samplesheet and set metadata

Add needed modules/processes

• [ ] Add any needed nf-core modules via the cli command nf-core modules install
• [ ] Add any custom processes to the modules/local directory
• [ ] Add and required software to the environment.yml file to be installed via conda or wave containers

Modify the main workflow

• [ ] Modify the main.nf file to add any needed processes

Documentation

• [ ] Search for TODO and replace with your own content
• [ ] Delete this section of the README

Introduction

kenibrewer/simplenextflow is a bioinformatics best-practice analysis pipeline for A simple nextflow template repository modeled after nf-core's template.

The pipeline is built using Nextflow, a workflow tool to run tasks across multiple compute infrastructures in a very portable manner. It uses Docker/Singularity containers making installation trivial and results highly reproducible. The Nextflow DSL2 implementation of this pipeline uses one container per process which makes it much easier to maintain and update software dependencies. Where possible, these processes have been submitted to and installed from nf-core/modules in order to make them available to all nf-core pipelines, and to everyone within the Nextflow community!

On release, automated continuous integration tests run the pipeline on a full-sized dataset on the AWS cloud infrastructure. This ensures that the pipeline runs on AWS, has sensible resource allocation defaults set to run on real-world datasets, and permits the persistent storage of results to benchmark between pipeline releases and other analysis sources.

Pipeline summary

1. Read QC (FastQC)

Quick Start

1. Install Nextflow (>=22.10.1)

2. Install any of Docker, Singularity (you can follow this tutorial), Podman, Shifter or Charliecloud for full pipeline reproducibility (you can use Conda both to install Nextflow itself and also to manage software within pipelines. Please only use it within pipelines as a last resort; see docs).

3. Download the pipeline and test it on a minimal dataset with a single command:

bash nextflow run kenibrewer/simplenextflow -profile test,YOURPROFILE --outdir <OUTDIR>

Note that some form of configuration will be needed so that Nextflow knows how to fetch the required software. This is usually done in the form of a config profile (YOURPROFILE in the example command above). You can chain multiple config profiles in a comma-separated string.

• The pipeline comes with config profiles called docker, singularity, podman, shifter, charliecloud and conda which instruct the pipeline to use the named tool for software management. For example, -profile test,docker.
• Please check nf-core/configs to see if a custom config file to run nf-core pipelines already exists for your Institute. If so, you can simply use -profile <institute> in your command. This will enable either docker or singularity and set the appropriate execution settings for your local compute environment.
• If you are using singularity, please use the nf-core download command to download images first, before running the pipeline. Setting the NXF_SINGULARITY_CACHEDIR or singularity.cacheDir Nextflow options enables you to store and re-use the images from a central location for future pipeline runs.
• If you are using conda, it is highly recommended to use the NXF_CONDA_CACHEDIR or conda.cacheDir settings to store the environments in a central location for future pipeline runs.

1. Start running your own analysis!

<!-- TODO nf-core: Update the example "typical command" below used to run the pipeline -->

bash nextflow run kenibrewer/simplenextflow --input samplesheet.csv --outdir <OUTDIR> --genome GRCh37 -profile <docker/singularity/podman/shifter/charliecloud/conda/institute>

Credits

kenibrewer/simplenextflow was originally written by Ken Brewer, PhD.

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

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.