CFC Configuration

All nf-core pipelines have been successfully configured for use on the CFC cluster at the Quantitative Biology Center here.

This profile is designed for developmental work, where container images might be frequently updated.

To use, run the pipeline with -profile cfc_dev. This will download and launch the cfc_dev.config which has been pre-configured with a setup suitable for the CFC cluster. Using this profile, for DSL1 pipelines a docker image containing all of the required software will be downloaded, and converted to a Singularity image before execution of the pipeline. For pipelines in DSL2, the individual Singularity images will be downloaded.

Before running the pipeline you will need to install Nextflow on the CFC cluster. You can do this by following the instructions here.

NB: You will need an account to use the HPC cluster CFC in order to run the pipeline. If in doubt contact IT. NB: Nextflow will need to submit the jobs via the job scheduler to the HPC cluster and as such the commands above will have to be executed on one of the login nodes. If in doubt contact IT.

Config file

See config file on GitHub

cfc_dev.config
//Profile config names for nf-core/configs
params {
    config_profile_description = 'QBiC Core Facility cluster dev profile without container cache provided by nf-core/configs.'
    config_profile_contact     = 'Sabrina Krakau (@skrakau)'
    config_profile_url         = 'http://qbic.uni-tuebingen.de/'
}
 
singularity {
    enabled = true
}
 
process {
    resourceLimits = [
        memory: 1992.GB,
        cpus: 128,
        time: 168.h
    ]
    executor = 'slurm'
    queue    = 'qbic'
    scratch  = 'true'
}
 
params {
    igenomes_base = '/nfsmounts/igenomes'
    max_memory    = 1992.GB
    max_cpus      = 128
    max_time      = 168.h
}