-
Notifications
You must be signed in to change notification settings - Fork 356
Update NCI Gadi config #920
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
Changes from all commits
3ac5528
f74b747
6604a74
8de4348
e09360e
7666d32
b4babd5
fbacde0
c327c7a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,3 +7,4 @@ | |
| **/unsw_katana** @jscgh | ||
| **/seadragon** @jiawku | ||
| **/fred_hutch** @derrik-gratz | ||
| **/nci_gadi** @georgiesamaha | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,11 +12,11 @@ Please be aware that you will need to have a user account, be a member of an Gad | |
|
|
||
| ### Prerequisites | ||
|
|
||
| Before running the pipeline you will need to load Nextflow and Singularity, both of which are globally installed modules on Gadi. You can do this by running the commands below: | ||
| Before running the pipeline you will need to load Nextflow, both of which are globally installed modules on Gadi (see `/apps`). You can do this by running the commands below: | ||
|
|
||
| ```bash | ||
| module purge | ||
| module load nextflow singularity | ||
| module load nextflow | ||
| ``` | ||
|
|
||
| ### Execution command | ||
|
|
@@ -32,7 +32,25 @@ nextflow run <nf-core_pipeline>/main.nf \ | |
|
|
||
| ### Cluster considerations | ||
|
|
||
| Please be aware that as of July 2023, NCI Gadi HPC queues **do not** have external network access. This means you will not be able to pull the workflow code base or containers if you submit your `nextflow run` command as a job on any of the standard job queues. NCI currently recommends you run your Nextflow head job either in a GNU screen or tmux session from the login node or submit it as a job to the [copyq](https://opus.nci.org.au/display/Help/Queue+Structure). See the [nf-core documentation](https://nf-co.re/docs/usage/offline) for instructions on running pipelines offline. | ||
| #### External network access | ||
|
|
||
| Please be aware that as of June 2025, NCI Gadi HPC compute nodes **do not** have external network access. This means you will not be able to pull the workflow code base or containers if you submit your `nextflow run` command as a job on any of the standard job queues. NCI currently recommends you run your Nextflow head job in a [persistent session](https://opus.nci.org.au/spaces/Help/pages/241926895/Persistent+Sessions) from the login node or submit it as a job to the [copyq](https://opus.nci.org.au/display/Help/Queue+Structure). See the [nf-core documentation](https://nf-co.re/docs/usage/offline) for instructions on running pipelines offline. | ||
|
|
||
| #### Downloading containers | ||
|
|
||
| This config requires Nextflow to use [Singularity](https://www.nextflow.io/docs/latest/container.html#singularity) to execute processes. Before a process can be executed, any nf-core pipeline you run will download that container to a local cache. This config file specifies the download and storage location with: | ||
|
|
||
| ``` | ||
| cacheDir = "/scratch/${params.project}/singularity" | ||
| ``` | ||
|
|
||
| Additionally, the project parameter is defined using the PBS environmental variable `$PROJECT`: | ||
|
|
||
| ``` | ||
| params.project = System.getenv("PROJECT") | ||
| ``` | ||
|
|
||
| #### Gadi queues and job submission | ||
|
|
||
| This config currently determines which Gadi queue to submit your task jobs to based on the amount of memory required. For the sake of resource and cost (service unit) efficiency, the following rules are applied by this config: | ||
|
|
||
|
|
@@ -56,7 +74,18 @@ The version of Nextflow installed on Gadi has been modified to make it easier to | |
| process { | ||
| executor = 'pbspro' | ||
| project = 'aa00' | ||
| storage = 'scratch/aa00+gdata/aa00' | ||
| storage = 'scratch/params.project' | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I see there's apparently since before the "recommendation" to make a copy of the config file rather than just overriding what's needed (as typically done, e.g. as referenced from https://nf-co.re/docs/usage/getting_started/configuration). If one does, this should have an expansion I assume? (Or could be hardcoded if a user does her own config).
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So |
||
| ... | ||
| } | ||
| ``` | ||
|
|
||
| Similarly, you can override the default storage location to change locations or add multiple locations by manually overriding the storage definition inside the process scope. For example: | ||
|
|
||
| ```nextflow | ||
| process { | ||
| executor = 'pbspro' | ||
| project = System.getenv("PROJECT") | ||
| storage = 'scratch/aa11+gdata/aa11' | ||
| ... | ||
| } | ||
| ``` | ||
|
|
||
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 this exist already, writable for everyone with the same project set?