Novo Nordisk’s Marjorie Configuration

Using the Marjorie config profile

Before running any pipeline in Novo Nordisk’s Marjorie cluster, Nextflow will need to be installed in the conda environment being used.

To use, run the pipeline with -profile marjorie (one hyphen). This will download and launch the marjorie.config which has been pre-configured with a setup suitable for the Marjorie server. It will enable Nextflow to manage the pipeline jobs via the Slurm job scheduler.

Using this profile, Docker image(s) containing required software(s) will be downloaded, and converted to Singularity image(s) if needed before execution of the pipeline.

Below are non-mandatory information on e.g., required modules

Before running the pipeline you will need to have a working Nextflow installation and load Singularity using the environment module system on the Marjorie cluster. You can do this by doing for example:

# Load Singularity environment modules
module load nextflow
module load singularity

Config file

See config file on GitHub

marjorie.config
/*
* ------------------------------------------------------------------
*   Config file for nextflow pipelines for Novo Nordisk's Marjorie cluster
* ------------------------------------------------------------------
*/
 
params {
    config_profile_description = "Novo Nordisk's Marjorie cluster profile"
    config_profile_contact     = 'Ashot Margaryan (ashotmarg2004@gmail.com)'
    max_memory                 = "512.GB"
    max_cpus                   = 64
    max_time                   = "240.h"
}
 
process {
    resourceLimits = [
        memory: 512.GB,
        cpus: 64,
        time: 240.h
    ]
    executor     = 'slurm'
    beforeScript = 'module purge; module load singularity/3.8.1'
    scratch      = true
    maxRetries   = 3
    scratch      = "/scratch/${USER}"
}
 
executor {
    queueSize       = 64
    submitRateLimit = "10/1sec"
}
 
singularity {
    enabled    = true
    autoMounts = true
    cacheDir   = "/scratch/${USER}"
}