millironx/nf-configs
1
0
Fork 0
mirror of https://github.com/MillironX/nf-configs.git synced 2024-11-22 00:26:03 +00:00
Code Issues Releases Packages Activity

w

Browse source
This commit is contained in:
Barry digby 2021-07-28 11:41:42 +01:00
parent 380adf083a
commit 11cb6cc70d
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/lugh.md
View file

@ -16,7 +16,7 @@ Please take care to use the `-bg` flag, or run the job on a compute node.
:warning: DO NOT RUN ANALYSES ON THE HEAD NODE :warning: :warning: DO NOT RUN ANALYSES ON THE HEAD NODE :warning:
The configuration file will load prerequisite modules for users (`Java` & `Singularity`), however it is up to the user to have a functional version of `nextflow` installed in their path. Follow `nextflow` installation instructions at the following (link)[https://www.nextflow.io/docs/latest/getstarted.html#installation]. The configuration file will load prerequisite modules for users (`Java` & `Singularity`), however it is up to the user to have a functional version of `nextflow` installed in their path. Follow `nextflow` installation instructions at the following [link](https://www.nextflow.io/docs/latest/getstarted.html#installation).
## Queue Resources ## Queue Resources
@ -30,7 +30,7 @@ The configuration file will load prerequisite modules for users (`Java` & `Singu
The configuration profile design is very simple. If your process exceeds 64GB memory or 16 cpus, it is sent to the `highmem` queue. If not, it is sent to the `normal` queue. Please do not use the `MSC` queue, this is reserved for Masters students. The configuration profile design is very simple. If your process exceeds 64GB memory or 16 cpus, it is sent to the `highmem` queue. If not, it is sent to the `normal` queue. Please do not use the `MSC` queue, this is reserved for Masters students.
Take others into consideration when deploying your workflow (do not hog the cluster :pig:). If you need to hammer the cluster with a pipeline, please reach out to me and we can tweak the configuration profile to dispatch jobs to only a handful of compute nodes via hostnames. Take others into consideration when deploying your workflow (do not hog the cluster :pig:). If you need to hammer the cluster with a pipeline, please reach out to me and we can tweak the configuration profile to dispatch jobs to only a handful of compute nodes via hostnames.
## Container Cache ## Container Cache