-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add configurations for GIGA and CÉCI clusters #779
Conversation
Hi @MartinGrignard ! Thanks for the PR! I the meantime please also join the nf-core github orgnaisation with instructions here: https://nf-co.re/join So we don't have to wait someone to manually use the tests and also get the code owners file to work :) |
@nf-core-bot fix linting |
|
||
```bash | ||
# Load modules | ||
module load 'Nextflow/24.04.2' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does singularity also need to be laoded, or is this available by default?
Also the dragon2 config doesn't specify a singualrity cache directory, if users need to do this manually maybe document to specify this with the nextflow NXF_SINGULARITY_CACHEDIR
(https://nextflow.io/docs/latest/reference/env-vars.html) so they at least can cache on a per-user basis
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the singularity
command is available by default on both CÉCI clusters (Dragon2 and NIC5).
Since there is no shared directory that I am aware of on those clusters, is this recommended to still specify it to something like ${HOME}/.cache/singularity
? Or is it okay to leave it empty so that the system uses its default value?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is recommended to specify a directory with NXF_SINGULARITY_CACHE_DIR
as the 'default' by Nextflow is to pull the images into the work/
directory, which is run specific. On the next run where -w
is somewhere else it'll download the images again
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the information, I added a default cache directory (for consistency across all users). If, in the future, a shared directory is created on these clusters, I'll document how to use it/switch to it.
The formatting failures:
---
-*Built with* ❤️ *by the [GIGA Bioinformatics Team](https://www.gigabioinformatics.uliege.be/cms/c_8464757/en/gigabioinformatics)*
+
+_Built with_ ❤️ _by the [GIGA Bioinformatics Team](https://www.gigabioinformatics.uliege.be/cms/c_8464757/en/gigabioinformatics)_
diff --git a/docs/ceci_nic5.md b/docs/ceci_nic5.md
index e9743f6..e46ad83 100644
--- a/docs/ceci_nic5.md
+++ b/docs/ceci_nic5.md
@@ -17,4 +17,5 @@ module load 'Nextflow/21.08.0'
---
-*Built with* ❤️ *by the [GIGA Bioinformatics Team](https://www.gigabioinformatics.uliege.be/cms/c_8464757/en/gigabioinformatics)*
+
+_Built with_ ❤️ _by the [GIGA Bioinformatics Team](https://www.gigabioinformatics.uliege.be/cms/c_8464757/en/gigabioinformatics)_
diff --git a/docs/giga.md b/docs/giga.md
index b14c96b..09c619e 100644
--- a/docs/giga.md
+++ b/docs/giga.md
@@ -26,4 +26,5 @@ module load 'nextflow/24.04.4'
---
-*Built with* ❤️ *by the [GIGA Bioinformatics Team](https://www.gigabioinformatics.uliege.be/cms/c_8464757/en/gigabioinformatics)*
+
+_Built with_ ❤️ _by the [GIGA Bioinformatics Team](https://www.gigabioinformatics.uliege.be/cms/c_8464757/en/gigabioinformatics)_ |
I just posted my request on the |
Replaced `configuraiton` by `configuration`. Co-authored-by: James A. Fellows Yates <[email protected]>
@MartinGrignard you'll need to accept the invitation by the email or by going to https://github.com/orgs/nf-core/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One further optimisation you could do is collapse the multiple params
blocks into one (the info and old max_* resource limitations), but not a blocker
…NIC5 configurations
name: GIGA, CÉCI NIC5 and CÉCI Dragon2 Configs
about: Three new cluster configurations for the GIGA and CÉCI.
Please follow these steps before submitting your PR:
[WIP]
in its titlemaster
branchSteps for adding a new config profile:
conf/
directorydocs/
directorynfcore_custom.config
file in the top-level directoryREADME.md
file in the top-level directoryprofile:
scope in.github/workflows/main.yml
.github/CODEOWNERS
(**/<custom-profile>** @<github-username>
)Summary
This PR adds the three following configuration profiles:
giga
to use with GIGA clusterceci_dragon2
to use with Dragon2ceci_nic5
to use with NIC5