Merge pull request #103 from jfy133/master

EAGER Pipeline specific config for SHH

conf/pipeline/eager/shh.config

@@ -0,0 +1,17 @@
+// Profile config names for nf-core/configs
+
+params {
+  // Specific nf-core/configs params
+  config_profile_contact = 'James Fellows Yates (@jfy133)'
+  config_profile_description = 'nf-core/eager SHH profile provided by nf-core/configs'
+}
+
+// Specific nf-core/eager process configuration
+process {
+  withName: malt {
+    memory = { check_max( 756.GB * task.attempt, 'memory' ) }
+    cpus = { check_max(64 * task.attempt, 'cpus') }
+    time = 1440.h
+    queue = { task.memory > 756.GB ? 'supercruncher': 'long' }
+  }
+}

docs/pipeline/eager/shh.md

@@ -0,0 +1,17 @@
+# nf-core/configs: shh eager specific configuration
+
+Extra specific configuration for eager pipeline
+
+## Usage
+
+To use, run the pipeline with `-profile shh`.
+
+This will download and launch the eager specific [`shh.config`](../conf/pipeline/eager/shh.config) which has been pre-configured with a setup suitable for the shh cluster.
+
+Example: `nextflow run nf-core/eager -profile shh`
+
+## eager specific configurations for shh
+
+Specific configurations for shh has been made for eager.
+
+* Running with the MALT module turned on, will by default be sent either to long or supercruncher queues with a minimum of 756GB and 64 cores.

pipeline/eager.config

@@ -0,0 +1,13 @@
+/*
+ * -------------------------------------------------
+ *  nfcore/eager custom profile Nextflow config file
+ * -------------------------------------------------
+ * Config options for custom environments.
+ * Cluster-specific config options should be saved
+ * in the conf/pipeline/eager folder and imported
+ * under a profile name here.
+ */
+
+profiles {
+  shh { includeConfig "${params.custom_config_base}/conf/pipeline/eager/shh.config" }
+}