mirror of
https://github.com/MillironX/nf-configs.git
synced 2024-11-22 00:26:03 +00:00
Merge branch 'master' into master
This commit is contained in:
Alexander Peltzer
GitHub
commit
23f9fd2d73
24 changed files with 203 additions and 120 deletions
5
.github/markdownlint.yml
vendored
Normal file
5
.github/markdownlint.yml
vendored
Normal file
|
|
@ -0,0 +1,5 @@
|
|||
# Markdownlint configuration file
|
||||
default: true,
|
||||
line-length: false
|
||||
no-duplicate-header:
|
||||
siblings_only: true
|
||||
20
.github/workflows/linting.yml
vendored
Normal file
20
.github/workflows/linting.yml
vendored
Normal file
|
|
@ -0,0 +1,20 @@
|
|||
name: Markdown linting
|
||||
# This workflow is triggered on pushes and PRs to the repository.
|
||||
on: [push, pull_request]
|
||||
|
||||
jobs:
|
||||
Markdown:
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- uses: actions/checkout@v1
|
||||
- uses: actions/setup-node@v1
|
||||
with:
|
||||
node-version: '10'
|
||||
- name: Install markdownlint
|
||||
run: |
|
||||
npm install -g markdownlint-cli
|
||||
- name: Run Markdownlint
|
||||
run: |
|
||||
markdownlint ${GITHUB_WORKSPACE} -c ${GITHUB_WORKSPACE}/.github/markdownlint.yml
|
||||
|
||||
|
||||
20
.github/workflows/main.yml
vendored
Normal file
20
.github/workflows/main.yml
vendored
Normal file
|
|
@ -0,0 +1,20 @@
|
|||
name: Configs tests
|
||||
|
||||
jobs:
|
||||
profile_test:
|
||||
runs-on: ubuntu-latest
|
||||
name: Run individual profiles
|
||||
strategy:
|
||||
matrix:
|
||||
profile: ['awsbatch', 'bigpurple', 'binac', 'cbe', 'ccga_dx', 'ccga', 'cfc', 'crick', 'czbiohub_aws_highpriority', 'czbiohub_aws', 'denbi_qbic', 'genouest', 'gis', 'hebbe', 'kraken', 'munin', 'pasteur', 'phoenix', 'prince', 'shh', 'uct_hex', 'uppmax_devel', 'uppmax', 'uzh']
|
||||
steps:
|
||||
- uses: actions/checkout@v1
|
||||
- name: Install Nextflow
|
||||
run: |
|
||||
wget -qO- get.nextflow.io | bash
|
||||
sudo mv nextflow /usr/local/bin/
|
||||
- name: Check whether profiles are all tested
|
||||
run: |
|
||||
python ${GITHUB_WORKSPACE}/bin/cchecker.py ${GITHUB_WORKSPACE}/nfcore_custom.config ${GITHUB_WORKSPACE}/.github/workflows/main.yml
|
||||
- name: "Check profile"
|
||||
run: nextflow run ${GITHUB_WORKSPACE}/configtest.nf --custom_config_base=${GITHUB_WORKSPACE} -profile ${{ matrix.profile }}
|
||||
30
.travis.yml
30
.travis.yml
|
|
@ -1,30 +0,0 @@
|
|||
sudo: required
|
||||
language: python
|
||||
jdk: openjdk8
|
||||
services:
|
||||
- docker
|
||||
python:
|
||||
- '3.6'
|
||||
cache: pip
|
||||
matrix:
|
||||
fast_finish: true
|
||||
|
||||
install:
|
||||
# Install Nextflow
|
||||
- mkdir /tmp/nextflow && cd /tmp/nextflow
|
||||
- wget -qO- get.nextflow.io | bash
|
||||
- sudo ln -s /tmp/nextflow/nextflow /usr/local/bin/nextflow
|
||||
- mkdir -p ${TRAVIS_BUILD_DIR}/tests && cd ${TRAVIS_BUILD_DIR}/tests
|
||||
|
||||
env:
|
||||
- NXF_VER='18.10.1' SCRATCH='~' # Specify a minimum NF version that should be tested and work. Set SCRATCH for prince.config.
|
||||
- NXF_VER='' SCRATCH='~' # Plus: get the latest NF version and check, that it works. Set SCRATCH for prince.config.
|
||||
|
||||
script:
|
||||
# Run the pipeline with the test profile and test remote config
|
||||
- |
|
||||
grep "{.*includeConfig.*[a-z]*\.config\"" ${TRAVIS_BUILD_DIR}/nfcore_custom.config | \
|
||||
tr -s ' ' | \
|
||||
cut -d " " -f 2 | \
|
||||
grep -v "czbiohub_aws" | \
|
||||
xargs -I {} nextflow run ${TRAVIS_BUILD_DIR}/configtest.nf --custom_config_base=${TRAVIS_BUILD_DIR} -profile {}
|
||||
10
README.md
10
README.md
|
|
@ -1,14 +1,18 @@
|
|||
# 
|
||||
# [](https://github.com/nf-core/configs)
|
||||
|
||||
[](https://travis-ci.org/nf-core/configs)
|
||||
[](https://github.com/nf-core/configs/workflows/nfcore%20configs%20tests/badge.svg)
|
||||
|
||||
A repository for hosting nextflow config files containing custom parameters required to run nf-core pipelines at different Institutions.
|
||||
|
||||
## Table of contents
|
||||
|
||||
* [](#nf-coreconfigshttpsgithubcomnf-coreconfigs)
|
||||
* [Table of contents](#table-of-contents)
|
||||
* [Using an existing config](#using-an-existing-config)
|
||||
* [Configuration and parameters](#configuration-and-parameters)
|
||||
* [Offline usage](#offline-usage)
|
||||
* [Adding a new config](#adding-a-new-config)
|
||||
* [Checking user hostnames](#checking-user-hostnames)
|
||||
* [Testing](#testing)
|
||||
* [Documentation](#documentation)
|
||||
* [Uploading to `nf-core/configs`](#uploading-to-nf-coreconfigs)
|
||||
|
|
@ -112,6 +116,8 @@ Currently documentation is available for the following systems:
|
|||
|
||||
[Fork](https://help.github.com/articles/fork-a-repo/) the `nf-core/configs` repository to your own GitHub account. Within the local clone of your fork add the custom config file to the [`conf/`](https://github.com/nf-core/configs/tree/master/conf) directory, and the documentation file to the [`docs/`](https://github.com/nf-core/configs/tree/master/docs) directory. You will also need to edit and add your custom profile to the [`nfcore_custom.config`](https://github.com/nf-core/configs/blob/master/nfcore_custom.config) file in the top-level directory of the clone.
|
||||
|
||||
Afterwards, make sure to edit the `.github/main.yml` file and add your profile name to alphabetically sorted `profile:` scope. This way, it will be tested automatically using GitHub Actions.
|
||||
|
||||
Commit and push these changes to your local clone on GitHub, and then [create a pull request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/) on the `nf-core/configs` GitHub repo with the appropriate information.
|
||||
|
||||
We will be notified automatically when you have created your pull request, and providing that everything adheres to nf-core guidelines we will endeavour to approve your pull request as soon as possible.
|
||||
|
|
|
|||
68
bin/cchecker.py
Normal file
68
bin/cchecker.py
Normal file
|
|
@ -0,0 +1,68 @@
|
|||
#!/usr/bin/env python
|
||||
|
||||
#######################################################################
|
||||
#######################################################################
|
||||
## Created on November 26 to check pipeline configs for nf-core/configs
|
||||
#######################################################################
|
||||
#######################################################################
|
||||
|
||||
import os
|
||||
import sys
|
||||
import argparse
|
||||
import re
|
||||
|
||||
############################################
|
||||
############################################
|
||||
## PARSE ARGUMENTS
|
||||
############################################
|
||||
############################################
|
||||
|
||||
Description = 'Double check custom config file and github actions file to test all cases'
|
||||
Epilog = """Example usage: python cchecker.py <nfcore_custom.config> <github_actions_file>"""
|
||||
|
||||
argParser = argparse.ArgumentParser(description=Description, epilog=Epilog)
|
||||
## REQUIRED PARAMETERS
|
||||
argParser.add_argument('CUSTOM_CONFIG', help="Input nfcore_custom.config.")
|
||||
argParser.add_argument('GITHUB_CONFIG', help="Input Github Actions YAML")
|
||||
|
||||
args = argParser.parse_args()
|
||||
|
||||
############################################
|
||||
############################################
|
||||
## MAIN FUNCTION
|
||||
############################################
|
||||
############################################
|
||||
|
||||
def check_config(Config, Github):
|
||||
|
||||
regex = 'includeConfig*'
|
||||
ERROR_STR = 'ERROR: Please check config file! Did you really update the profiles?'
|
||||
|
||||
## CHECK Config First
|
||||
config_profiles = set()
|
||||
with open(Config, 'r') as cfg:
|
||||
for line in cfg:
|
||||
if re.search(regex, line):
|
||||
hit = line.split('/')[2].split('.')[0]
|
||||
config_profiles.add(hit.strip())
|
||||
|
||||
###Check Github Config now
|
||||
tests = set()
|
||||
with open(Github, 'r') as ghfile:
|
||||
for line in ghfile:
|
||||
if re.search('profile: ', line):
|
||||
line = line.replace('\'','').replace('[','').replace(']','').replace('\n','')
|
||||
profiles = line.split(':')[1].split(',')
|
||||
for p in profiles:
|
||||
tests.add(p.strip())
|
||||
|
||||
###Check if sets are equal
|
||||
if tests == config_profiles:
|
||||
sys.exit(0)
|
||||
else:
|
||||
#Maybe report what is missing here too
|
||||
print("Tests don't seem to test these profiles properly!\n")
|
||||
print(config_profiles.symmetric_difference(tests))
|
||||
sys.exit(1)
|
||||
|
||||
check_config(Config=args.CUSTOM_CONFIG,Github=args.GITHUB_CONFIG)
|
||||
|
|
@ -1,14 +1,14 @@
|
|||
//Nextflow config file for running on AWS batch
|
||||
|
||||
params {
|
||||
config_profile_name = 'AWSBATCH'
|
||||
config_profile_description = 'AWSBATCH Cloud Profile'
|
||||
awsqueue = false
|
||||
awsregion = 'eu-west-1'
|
||||
config_profile_contact = 'Alexander Peltzer (@apeltzer)'
|
||||
config_profile_description = 'AWSBATCH Cloud Profile'
|
||||
config_profile_name = 'AWSBATCH'
|
||||
config_profile_url = 'https://aws.amazon.com/batch/'
|
||||
tracedir = './'
|
||||
}
|
||||
|
||||
aws.region = params.awsregion
|
||||
process.executor = 'awsbatch'
|
||||
process.queue = params.awsqueue
|
||||
executor.awscli = '/home/ec2-user/miniconda/bin/aws'
|
||||
params.tracedir = './'
|
||||
|
|
@ -1,8 +1,10 @@
|
|||
# nf-core/configs: BigPurple Configuration
|
||||
|
||||
## nf-core pipelines that use this repo
|
||||
|
||||
All nf-core pipelines that use this config repo (which is most), can be run on BigPurple. **Before** running a pipeline for the first time, go into an interactive slurm session on a compute node (`srun --pty --time=02:00:00 -c 2`), as the docker image for the pipeline will need to be pulled and converted. Once in the interactive session:
|
||||
|
||||
```
|
||||
```bash
|
||||
module load singularity/3.1
|
||||
module load squashfs-tools/4.3
|
||||
```
|
||||
|
|
@ -13,12 +15,11 @@ An example commandline:
|
|||
`nextflow run nf-core/<pipeline name> -profile bigpurple <additional flags>`
|
||||
|
||||
## nf-core pipelines that do not use this repo
|
||||
|
||||
If the pipeline has not yet been configured to use this config, then you will have to do it manually.
|
||||
git clone this repo, copy the `bigpurple.config` from the conf folder and then you can invoke the pipeline like this:
|
||||
|
||||
`nextflow run nf-core/<pipeline name> -c bigpurple.config <additional flags>`
|
||||
|
||||
|
||||
>NB: You will need an account to use the HPC cluster BigPurple in order to run the pipeline. If in doubt contact MCIT.
|
||||
|
||||
>NB: You will need to install nextflow in your home directory - instructions are on nextflow.io (or ask the writer of this profile). The reason there is no module for nextflow on the cluster, is that the development cycle of nextflow is rapid and it's easy to update yourself: `nextflow self-update`
|
||||
|
|
|
|||
|
|
@ -13,7 +13,5 @@ module load devel/java_jdk/1.8.0u112
|
|||
module load devel/singularity/3.0.1
|
||||
```
|
||||
|
||||
|
||||
>NB: You will need an account to use the HPC cluster BINAC 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.
|
||||
|
|
|
|||
|
|
@ -14,5 +14,4 @@ module load singularity/3.2.1
|
|||
```
|
||||
|
||||
>NB: You will need an account to use the HPC cluster on CBE 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.
|
||||
|
|
|
|||
|
|
@ -5,5 +5,4 @@ Deployment and testing of nf-core pipelines at the CCGA DX cluster is on-going.
|
|||
To use, run the pipeline with `-profile ccga_dx`. This will download and launch the [`ccga_dx.config`](../conf/ccga_dx.config) which has been pre-configured with a setup suitable for the CCGA cluster. Using this profile, a docker image containing all of the required software will be downloaded, and converted to a Singularity image before execution of the pipeline.
|
||||
|
||||
Before running the pipeline you will need to have Nextflow installed.
|
||||
|
||||
>NB: Access to the CCGA DX cluster is restricted to IKMB/CCGA employes. Please talk to Marc Hoeppner to get access (@marchoeppner).
|
||||
|
|
|
|||
|
|
@ -13,7 +13,5 @@ module load devel/java_jdk/1.8.0u121
|
|||
module load qbic/singularity_slurm/3.0.3
|
||||
```
|
||||
|
||||
|
||||
>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.
|
||||
|
|
|
|||
|
|
@ -20,5 +20,4 @@ Alternatively, if you are running the pipeline regularly for genomes that arent
|
|||
All of the intermediate files required to run the pipeline will be stored in the `work/` directory. It is recommended to delete this directory after the pipeline has finished successfully because it can get quite large, and all of the main output files will be saved in the `results/` directory anyway.
|
||||
|
||||
>NB: You will need an account to use the HPC cluster on CAMP in order to run the pipeline. If in doubt contact IT.
|
||||
|
||||
>NB: Nextflow will need to submit the jobs via SLURM 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.
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ The pipeline will monitor and submit jobs to AWS Batch on your behalf. To ensure
|
|||
|
||||
[tmux](https://hackernoon.com/a-gentle-introduction-to-tmux-8d784c404340) is a "Terminal Multiplexer" that allows for commands to continue running even when you have closed your laptop. Start a new tmux session with `tmux new` and we'll name this session `nextflow`.
|
||||
|
||||
```
|
||||
```bash
|
||||
tmux new -n nextflow
|
||||
```
|
||||
|
||||
|
|
@ -22,89 +22,87 @@ Now you can run pipelines with abandon!
|
|||
|
||||
### 2. Make a GitHub repo for your workflows (optional :)
|
||||
|
||||
|
||||
To make sharing your pipelines and commands easy between your teammates, it's best to share code in a GitHub repository. One way is to store the commands in a Makefile ([example](https://github.com/czbiohub/kh-workflows/blob/master/nf-kmer-similarity/Makefile)) which can contain multiple `nextflow run` commands so that you don't need to remember the S3 bucket or output directory for every single one. [Makefiles](https://kbroman.org/minimal_make/) are broadly used in the software community for running many complex commands. Makefiles can have a lot of dependencies and be confusing, so we're only going to write *simple* Makefiles.
|
||||
|
||||
```
|
||||
```bash
|
||||
rnaseq:
|
||||
nextflow run -profile czbiohub_aws nf-core/rnaseq \
|
||||
--reads 's3://czb-maca/Plate_seq/24_month/180626_A00111_0166_BH5LNVDSXX/fastqs/*{R1,R2}*.fastq.gz' \
|
||||
--genome GRCm38 \
|
||||
--outdir s3://olgabot-maca/nextflow-test/
|
||||
```
|
||||
|
||||
human_mouse_zebrafish:
|
||||
Human_Mouse_Zebrafish:
|
||||
|
||||
```bash
|
||||
nextflow run czbiohub/nf-kmer-similarity -latest -profile aws \
|
||||
--samples s3://kmer-hashing/hematopoeisis/smartseq2/human_mouse_zebrafish/samples.csv
|
||||
```
|
||||
|
||||
Merkin2012_AWS:
|
||||
|
||||
merkin2012_aws:
|
||||
```bash
|
||||
nextflow run czbiohub/nf-kmer-similarity -latest --sra "SRP016501" \
|
||||
-r olgabot/support-csv-directory-or-sra \
|
||||
-profile aws
|
||||
-r olgabot/support-csv-directory-or-sra \-profile aws
|
||||
```
|
||||
|
||||
In this example, one would run the `rnaseq` rule and the nextflow command beneath it with:
|
||||
|
||||
```
|
||||
```bash
|
||||
make rnaseq
|
||||
```
|
||||
|
||||
If one wanted to run a different command, e.g. `human_mouse_zebrafish`, they would specify that command instead. For example:
|
||||
|
||||
```
|
||||
```bash
|
||||
make human_mouse_zebrafish
|
||||
```
|
||||
|
||||
Makefiles are a very useful way of storing longer commands with short mnemonic words.
|
||||
|
||||
|
||||
Once you [create a new repository](https://github.com/organizations/czbiohub/repositories/new) (best to initialize with a `.gitignore`, license - MIT and `README`), clone that repository to your EC2 instance. For example, if the repository is called `kh-workflows`, this is what the command would look like:
|
||||
|
||||
```
|
||||
```bash
|
||||
git clone https://github.com/czbiohub/kh-workflows
|
||||
```
|
||||
|
||||
Now both create and edit a `Makefile`:
|
||||
|
||||
```
|
||||
```bash
|
||||
cd
|
||||
nano Makefile
|
||||
```
|
||||
|
||||
Write your rule with a colon after it, and on the next line must be a **tab**, not spaces. Once you're done, exit the program (the `^` command shown in nano means "Control"), write the file, add it to git, commit it, and push it up to GitHub.
|
||||
|
||||
|
||||
```
|
||||
```bash
|
||||
git add Makefile
|
||||
git commit -m "Added makefile"
|
||||
git push origin master
|
||||
```
|
||||
|
||||
|
||||
### 3. Run your workflow!!
|
||||
|
||||
### 3. Run your workflow
|
||||
|
||||
Remember to specify `-profile czbiohub_aws` to grab the CZ Biohub-specific AWS configurations, and an `--outdir` with an AWS S3 bucket so you don't run out of space on your small AMI
|
||||
|
||||
```
|
||||
```bash
|
||||
nextflow run -profile czbiohub_aws nf-core/rnaseq \
|
||||
--reads 's3://czb-maca/Plate_seq/24_month/180626_A00111_0166_BH5LNVDSXX/fastqs/*{R1,R2}*.fastq.gz' \
|
||||
--genome GRCm38 \
|
||||
--outdir s3://olgabot-maca/nextflow-test/
|
||||
```
|
||||
|
||||
### 4. If you lose connection, how do you restart the jobs?
|
||||
### 4. If you lose connection, how do you restart the jobs
|
||||
|
||||
If you close your laptop, get onto the train, or lose WiFi connection, you may lose connection to AWS and may need to restart the jobs. To reattach, use the command `tmux attach` and you should see your Nextflow output! To get the named session, use:
|
||||
|
||||
```
|
||||
```bash
|
||||
tmux attach -n nextflow
|
||||
```
|
||||
|
||||
To restart the jobs from where you left off, add the `-resume` flag to your `nextflow` command:
|
||||
|
||||
|
||||
```
|
||||
```bash
|
||||
nextflow run -profile czbiohub_aws nf-core/rnaseq \
|
||||
--reads 's3://czb-maca/Plate_seq/24_month/180626_A00111_0166_BH5LNVDSXX/fastqs/*{R1,R2}*.fastq.gz' \
|
||||
--genome GRCm38 \
|
||||
|
|
@ -122,7 +120,5 @@ You can do this by simply using the `--genome <GENOME_ID>` parameter.
|
|||
|
||||
For Human and Mouse, we use [GENCODE](https://www.gencodegenes.org/) gene annotations. This doesn't change how you would specify the genome name, only that the pipelines run with the `czbiohub_aws` profile would be with GENCODE rather than iGenomes.
|
||||
|
||||
|
||||
>NB: You will need an account to use the HPC cluster on PROFILE CLUSTER 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.
|
||||
|
|
|
|||
|
|
@ -4,20 +4,20 @@ All nf-core pipelines have been successfully configured for use on the tars clus
|
|||
|
||||
To use, run the pipeline with `-profile pasteur`. This will download and launch the [`pasteur.config`](../conf/pasteur.config) which has been pre-configured with a setup suitable for the Pasteur cluster. Using this profile, a docker image containing all of the required software will be downloaded, and converted to a Singularity image before execution of the pipeline.
|
||||
|
||||
|
||||
|
||||
## Running the workflow on the Pasteur cluster
|
||||
|
||||
Nextflow is not installed by default on the Pasteur cluster.
|
||||
|
||||
- Install Nextflow : [here](https://www.nextflow.io/docs/latest/getstarted.html#)
|
||||
|
||||
|
||||
Nextflow manages each process as a separate job that is submitted to the cluster by using the sbatch command.
|
||||
Nextflow manages each process as a separate job that is submitted to the cluster by using the `sbatch` command.
|
||||
Nextflow shouldn't run directly on the submission node but on a compute node.
|
||||
The compute nodes don't have access to internet so you need to run it offline.
|
||||
|
||||
To do that:
|
||||
|
||||
1. Create a virtualenv to install nf-core
|
||||
|
||||
```bash
|
||||
module purge
|
||||
module load Python/3.6.0
|
||||
|
|
@ -27,17 +27,17 @@ cd /path/to/nf-core/workflows
|
|||
virtualenv .venv -p python3
|
||||
. .venv/bin/activate
|
||||
```
|
||||
|
||||
2. Install nf-core: [here](https://nf-co.re/tools#installation)
|
||||
3. Get nf-core pipeline and container: [here](https://nf-co.re/tools#downloading-pipelines-for-offline-use)
|
||||
4. Get the nf-core Pasteur profile: [here](https://github.com/nf-core/rnaseq/blob/master/docs/usage.md#--custom_config_base)
|
||||
5. Run nextflow on a compute node:
|
||||
|
||||
```bash
|
||||
# create a terminal
|
||||
tmux
|
||||
|
||||
# Get a compute node
|
||||
salloc
|
||||
|
||||
# Load the dependencies if not done before
|
||||
module purge
|
||||
module load java
|
||||
|
|
@ -52,5 +52,5 @@ nextflow run \\
|
|||
--email my-email@pasteur.fr \\
|
||||
--custom_config_base /path/to/configs/from/step/4/ \\
|
||||
-c my-specific.config
|
||||
...
|
||||
|
||||
```
|
||||
|
|
|
|||
|
|
@ -1,5 +1,7 @@
|
|||
# nf-core/configs: Prince Configuration
|
||||
|
||||
## nf-core pipelines that use this repo
|
||||
|
||||
All nf-core pipelines that use this config repo (which is most), can be run on prince. **Before** running a pipeline for the first time, go into an interactive slurm session on a compute node (`srun --pty --time=02:00:00 -c 2`), as the docker image for the pipeline will need to be pulled and converted.
|
||||
|
||||
Now, run the pipeline of your choice with `-profile prince`. This will download and launch the prince.config which has been pre-configured with a setup suitable for the prince cluster. Using this profile, a docker image containing all of the required software will be downloaded, and converted to a singularity image before execution of the pipeline. This step **takes time**!!
|
||||
|
|
@ -8,13 +10,11 @@ An example commandline:
|
|||
`nextflow run nf-core/<pipeline name> -profile prince <additional flags>`
|
||||
|
||||
## nf-core pipelines that do not use this repo
|
||||
|
||||
If the pipeline has not yet been configured to use this config, then you will have to do it manually.
|
||||
git clone this repo, copy the `prince.config` from the conf folder and then you can invoke the pipeline like this:
|
||||
|
||||
`nextflow run nf-core/<pipeline name> -c prince.config <additional flags>`
|
||||
|
||||
|
||||
>NB: You will need an account to use the HPC cluster Prince in order to run the pipeline. If in doubt contact the HPC admins.
|
||||
|
||||
>NB: Rather than using the nextflow module, I recommend you install nextflow in your home directory - instructions are on nextflow.io (or ask the writer of this profile). The reason this is better than using the module for nextflow on the cluster, is that the development cycle of nextflow is rapid and it's easy to update your installation yourself: `nextflow self-update`
|
||||
|
||||
>NB: Rather than using the nextflow module, I recommend you install nextflow in your home directory - instructions are on nextflow.io (or ask the writer of this profile). The reason this is better than using the module for nextflow on the cluster, is that the development cycle of nextflow is rapid and it's easy to update your installation yourself: `nextflow self-update`.
|
||||
|
|
|
|||
|
|
@ -14,5 +14,4 @@ This configuration will automatically choose the correct SLURM queue (`short`,`m
|
|||
Please note that there is no `supercruncher` queue on CDAG.
|
||||
|
||||
>NB: You will need an account and VPN access to use the cluster at MPI-SHH in order to run the pipeline. If in doubt contact IT.
|
||||
|
||||
>NB: Nextflow will need to submit the jobs via SLURM to the clusters and as such the commands above will have to be executed on one of the head nodes. If in doubt contact IT.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ All nf-core pipelines have been successfully configured for use on the PROFILE C
|
|||
|
||||
To use, run the pipeline with `-profile PROFILENAME`. This will download and launch the [`profile.config`](../conf/profile.config) which has been pre-configured with a setup suitable for the PROFILE cluster. Using this profile, a docker image containing all of the required software will be downloaded, and converted to a Singularity image before execution of the pipeline.
|
||||
|
||||
## Below are non-mandatory information e.g. on modules to load etc.
|
||||
## Below are non-mandatory information e.g. on modules to load etc
|
||||
|
||||
Before running the pipeline you will need to load Nextflow and Singularity using the environment module system on PROFILE CLUSTER. You can do this by issuing the commands below:
|
||||
|
||||
|
|
@ -20,7 +20,5 @@ module load Singularity/2.6.0
|
|||
A local copy of the iGenomes resource has been made available on PROFILE CLUSTER so you should be able to run the pipeline against any reference available in the `igenomes.config` specific to the nf-core pipeline.
|
||||
You can do this by simply using the `--genome <GENOME_ID>` parameter.
|
||||
|
||||
|
||||
>NB: You will need an account to use the HPC cluster on PROFILE CLUSTER 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.
|
||||
|
|
|
|||
|
|
@ -3,6 +3,7 @@
|
|||
All nf-core pipelines have been successfully configured for use on the Swedish UPPMAX clusters.
|
||||
|
||||
## Using the UPPMAX config profile
|
||||
|
||||
To use, run the pipeline with `-profile uppmax` (one hyphen). This will download and launch the [`uppmax.config`](../conf/uppmax.config) which has been pre-configured with a setup suitable for the UPPMAX servers. Using this profile, a docker image containing all of the required software will be downloaded, and converted to a Singularity image before execution of the pipeline.
|
||||
|
||||
In addition to this config profile, you will also need to specify an UPPMAX project id.
|
||||
|
|
@ -18,10 +19,12 @@ This config enables Nextflow to manage the pipeline jobs via the Slurm job sched
|
|||
Just run Nextflow on a login node and it will handle everything else.
|
||||
|
||||
## Using iGenomes references
|
||||
|
||||
A local copy of the iGenomes resource has been made available on all UPPMAX clusters so you should be able to run the pipeline against any reference available in the `igenomes.config`.
|
||||
You can do this by simply using the `--genome <GENOME_ID>` parameter.
|
||||
|
||||
## Running offline with Bianca
|
||||
|
||||
If running on Bianca, you will have no internet connection and these configs will not be loaded.
|
||||
Please use the nf-core helper tool on a different system to download the required pipeline files, and transfer them to bianca.
|
||||
This helper tool bundles the config files in this repo together with the pipeline files, so the profile will still be available.
|
||||
|
|
@ -33,6 +36,7 @@ Note that Bianca only allocates 7 GB memory per core so the max memory needs to
|
|||
```
|
||||
|
||||
## Getting more memory
|
||||
|
||||
If your nf-core pipeline run is running out of memory, you can run on a fat node with more memory using the following nextflow flags:
|
||||
|
||||
```bash
|
||||
|
|
@ -47,6 +51,7 @@ Note that each job will still start with the same request as normal, but restart
|
|||
All jobs will be submitted to fat nodes using this method, so it's only for use in extreme circumstances.
|
||||
|
||||
## Uppmax-devel config
|
||||
|
||||
If doing pipeline development work on Uppmax, this profile allows for faster testing.
|
||||
|
||||
Applied after main UPPMAX config, it overwrites certain parts of the config and submits jobs to the `devcore` queue, which has much faster queue times.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,5 @@ All nf-core pipelines have been successfully configured for use on the UZH clust
|
|||
|
||||
To use, run the pipeline with `-profile uzh`. This will download and launch the [`uzh.config`](../conf/uzh.config) which has been pre-configured with a setup suitable for the UZH cluster. Using this profile, a docker image containing all of the required software will be downloaded, and converted to a Singularity image before execution of the pipeline.
|
||||
|
||||
|
||||
>NB: You will need an account to use the HPC cluster UZH 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.
|
||||
|
|
|
|||
|
|
@ -11,6 +11,7 @@
|
|||
params.custom_config_version = 'master'
|
||||
params.custom_config_base = "https://raw.githubusercontent.com/nf-core/configs/${params.custom_config_version}"
|
||||
|
||||
//Please use a new line per include Config section to allow easier linting/parsing. Thank you.
|
||||
profiles {
|
||||
awsbatch { includeConfig "${params.custom_config_base}/conf/awsbatch.config" }
|
||||
bigpurple { includeConfig "${params.custom_config_base}/conf/bigpurple.config" }
|
||||
|
|
@ -21,7 +22,9 @@ profiles {
|
|||
cfc { includeConfig "${params.custom_config_base}/conf/cfc.config" }
|
||||
crick { includeConfig "${params.custom_config_base}/conf/crick.config" }
|
||||
czbiohub_aws { includeConfig "${params.custom_config_base}/conf/czbiohub_aws.config" }
|
||||
czbiohub_aws_highpriority { includeConfig "${params.custom_config_base}/conf/czbiohub_aws.config"; includeConfig "${params.custom_config_base}/conf/czbiohub_aws_highpriority.config" }
|
||||
czbiohub_aws_highpriority {
|
||||
includeConfig "${params.custom_config_base}/conf/czbiohub_aws.config";
|
||||
includeConfig "${params.custom_config_base}/conf/czbiohub_aws_highpriority.config"}
|
||||
genotoul { includeConfig "${params.custom_config_base}/conf/genotoul.config" }
|
||||
denbi_qbic { includeConfig "${params.custom_config_base}/conf/denbi_qbic.config" }
|
||||
genouest { includeConfig "${params.custom_config_base}/conf/genouest.config" }
|
||||
|
|
@ -35,7 +38,8 @@ profiles {
|
|||
shh { includeConfig "${params.custom_config_base}/conf/shh.config" }
|
||||
uct_hex { includeConfig "${params.custom_config_base}/conf/uct_hex.config" }
|
||||
uppmax { includeConfig "${params.custom_config_base}/conf/uppmax.config" }
|
||||
uppmax_devel { includeConfig "${params.custom_config_base}/conf/uppmax.config"; includeConfig "${params.custom_config_base}/conf/uppmax_devel.config" }
|
||||
uppmax_devel { includeConfig "${params.custom_config_base}/conf/uppmax.config";
|
||||
includeConfig "${params.custom_config_base}/conf/uppmax_devel.config" }
|
||||
uzh { includeConfig "${params.custom_config_base}/conf/uzh.config" }
|
||||
}
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue