Skip to content

Latest commit

 

History

History
92 lines (66 loc) · 4.52 KB

installation.md

File metadata and controls

92 lines (66 loc) · 4.52 KB
Raw

nf-core/qtlmap: Installation

To start using the nf-core/qtlmap pipeline, follow the steps below:

1) Install NextFlow

Nextflow runs on most POSIX systems (Linux, Mac OSX etc). It can be installed by running the following commands:

# Make sure that Java v8+ is installed:
java -version

# Install Nextflow
curl -fsSL get.nextflow.io | bash

# Add Nextflow binary to your PATH:
mv nextflow ~/bin/
# OR system-wide installation:
# sudo mv nextflow /usr/local/bin

See nextflow.io for further instructions on how to install and configure Nextflow.

2) Install the pipeline

2.1) Automatic

This pipeline itself needs no installation - NextFlow will automatically fetch it from GitHub if eQTL-Catalogue/qtlmap is specified as the pipeline name.

2.2) Offline

The above method requires an internet connection so that Nextflow can download the pipeline files. If you're running on a system that has no internet connection, you'll need to download and transfer the pipeline files manually:

git clone https://github.com/eQTL-Catalogue/qtlmap.git
cd qtlmap
nextflow run main.nf -profile docker,test
# nextflow run main.nf -profile singularity,test

To stop nextflow from looking for updates online, you can tell it to run in offline mode by specifying the following environment variable in your ~/.bashrc file:

export NXF_OFFLINE='TRUE'

2.3) Development

If you would like to make changes to the pipeline, it's best to make a fork on GitHub and then clone the files. Once cloned you can run the pipeline directly as above.

3) Pipeline configuration

By default, the pipeline loads a basic server configuration conf/base.config This uses a number of sensible defaults for process requirements and is suitable for running on a simple (if powerful!) local server.

Be warned of two important points about this default configuration:

  1. The default profile uses the local executor
    • All jobs are run in the login session. If you're using a simple server, this may be fine. If you're using a compute cluster, this is bad as all jobs will run on the head node.
    • See the nextflow docs for information about running with other hardware backends. Most job scheduler systems are natively supported.
  2. Nextflow will expect all software to be installed and available on the PATH
    • It's expected to use an additional config profile for docker, singularity or conda support. See below.

3.1) Software deps: Docker

First, install docker on your system: Docker Installation Instructions

Then, running the pipeline with the option -profile docker tells Nextflow to enable Docker for this run. An image containing all of the software requirements will be automatically fetched and used from quay.io (https://quay.io/repository/eqtlcatalogue/qtlmap).

3.1) Software deps: Singularity

If you're not able to use Docker then Singularity is a great alternative. The process is very similar: running the pipeline with the option -profile singularity tells Nextflow to enable singularity for this run. An image containing all of the software requirements will be automatically fetched and used from quay.io.

3.2) Software deps: conda

If you're not able to use Docker or Singularity, you can instead use conda to manage the software requirements. This is slower and less reproducible than the above, but is still better than having to install all requirements yourself! The pipeline ships with a conda environment file and nextflow has built-in support for this. To use it first ensure that you have conda installed (we recommend miniconda), then follow the same pattern as above and use the flag -profile conda

3.3) Configuration profiles

See docs/configuration/adding_your_own.md