From 235097e58e545c182bd9d02b00a5e424f150b7bf Mon Sep 17 00:00:00 2001 From: Gwenna Breton Date: Wed, 6 Jul 2022 11:20:59 +0200 Subject: [PATCH] Addressed review comments - removed mention of iGenomes - clarified whom to contact for support --- docs/medair.md | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/docs/medair.md b/docs/medair.md index dd2b9aa..0c54c81 100644 --- a/docs/medair.md +++ b/docs/medair.md @@ -57,12 +57,5 @@ Depending on what you are running, you can choose between the `wgs` and `product >Usage: -profile medair,wgs ?? (Check) -## iGenomes specific configuration - ->TODO modify this part. Do we want to have the iGenomes somewhere? - -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 ` 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. +>NB: You will need an account to use the HPC cluster on PROFILE CLUSTER in order to run the pipeline. If in doubt contact cgg-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 cgg-it.