Skip to content

Site configurations for NCI-Gadi, Australia.#2013

Open
Vinod Kumar (vinodk-bom) wants to merge 7 commits intoMetOffice:mainfrom
vinodk-bom:main
Open

Site configurations for NCI-Gadi, Australia.#2013
Vinod Kumar (vinodk-bom) wants to merge 7 commits intoMetOffice:mainfrom
vinodk-bom:main

Conversation

@vinodk-bom
Copy link
Copy Markdown
Collaborator

Add a site-specific configuration for NCI-Gadi, as well as an optional workflow configuration that runs at NCI for a deterministic LFRic and UM comparison.

Contribution checklist

Aim to have all relevant checks ticked off before merging. See the developer's guide for more detail.

  • Documentation has been updated to reflect change.
  • New code has tests, and affected old tests have been updated.
  • All tests and CI checks pass.
  • Ensured the pull request title is descriptive.
  • Ensure rose-suite.conf.example has been updated if new diagnostic added.
  • Conda lock files have been updated if dependencies have changed.
  • Attributed any Generative AI, such as GitHub Copilot, used in this PR.
  • Marked the PR as ready to review.

Copy link
Copy Markdown
Member

@jfrost-mo James Frost (jfrost-mo) left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like a sensible site configuration. I've left a few minor comments, but the only thing that needs changing is to move the changes to rose-meta.conf into rose-meta.conf.jinja2, as that is the source from which the .conf file is generated.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For various reasons we do a bit of templating into this file. The actual source file is rose-meta.conf.jinja2, while this file is regenerated from that. Please make this change in the .jinja2 file for them to be persisted.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added. See c49bc8e


[runtime]
[[root]]
platform = gadi_background
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does gadi_background have sensible default directives, or do they need setting?

Aside from the baking tasks which you have already got separate definitions for, the other tasks should be resource light. (Single CPU, <1 GiB RAM).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gadi_background is appropriate for very light tasks, it's running in the background of the users cylc server so no directives needed

Comment on lines +14 to +21
[[validate_environment]]
platform = gadi_background

[[parbake_recipes]]
platform = gadi_background

[[parbake_aggregation_recipes]]
platform = gadi_background
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All of these tasks will inherit from root, so you don't need to specify them explicitly.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Removed them now. See f136ab5

Vinod Kumar (vinodk-bom) and others added 4 commits April 1, 2026 21:15
Co-authored-by: James Frost <james.frost@metoffice.gov.uk>
Co-authored-by: James Frost <james.frost@metoffice.gov.uk>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants