Skip to content

Make DKCOEXP the large domain#116

Open
uandrae wants to merge 1 commit into
ACCORD-NWP:developfrom
uandrae:feature/DKCOEXP_is_the_large_domain
Open

Make DKCOEXP the large domain#116
uandrae wants to merge 1 commit into
ACCORD-NWP:developfrom
uandrae:feature/DKCOEXP_is_the_large_domain

Conversation

@uandrae

@uandrae uandrae commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Describe your changes

Use the DKCOEXP domain as the default large option and reduce the node usage. Haven't touched the CY49 files yet so these will run the 500m but very very slow.

Requires #114 to work.

< Please also include relevant motivation and context. >

< List any dependencies that are required for this change. >

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist before requesting a review

Testing

  • I have tested this on ATOS using the atos_bologna.toml configuration in the latest version of Tactus-test-runner
  • I have tested this on LUMI using the lumi.toml configuration in the latest version of Tactus-test-runner

For further information see the development guide

Code quality

  • My change follows the best practices for this project.
  • My local environment is correctly initialised as described in the README file.
  • My branch is up-to-date with the target branch - if not update your fork with the changes from the target branch (use pull with --rebase option if possible).
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have updated the documentation and docstrings to reflect the changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have ensured that the code is still installable with poetry after the changes and runs
  • I have requested one or more reviewer(s) and an assignee (assignee is responsible for merging). At least one reviewer has accepted to review.

Checklist for reviewers

Each PR comes with its own improvements and flaws. The reviewer should check the following:

  • the code readable
  • the code well tested (checked coverage report)
  • the code documented
  • the code easy to maintain

Author checklist after completed review

  • I have added a line to the CHANGELOG describing this change (in section
    reflecting type of change, for example "bug fixes", add section where
    missing)

Checklist for assignees

  • PR is up to date with the base branch
  • the tests passing
  • author has added an entry to the changelog (and designated the change as added, changed or fixed)
  • the PR has been approved by all the reviewers, that accepted to review.
  • Once the PR ready to be merged, squash commits and merge the PR.

Tag possible reviewers

You can @-tag people to review this PR in addition to formal review requests.

@kastelecn

Copy link
Copy Markdown
Contributor

Can I expect all tasks to work on large domain?

@uandrae

uandrae commented Jun 16, 2026

Copy link
Copy Markdown
Contributor Author

Can I expect all tasks to work on large domain?

Good point! No, it's only HARMONIE-AROME that works. I don't want to start debugging the others though before we have introduced new namelist settings.

@kastelecn kastelecn left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

With assuming that the node configuration is good it looks good to me

@bstrajnar

bstrajnar commented Jun 16, 2026 via email

Copy link
Copy Markdown

@romick-knmi romick-knmi left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Tested and works for Harmonie-Arome

@uandrae

uandrae commented Jun 16, 2026

Copy link
Copy Markdown
Contributor Author

It's worth noting that the 500m_template domain runs through with all CSCs when driven by global DT data. Haven't tested with HRES data.

@uandrae

uandrae commented Jun 17, 2026

Copy link
Copy Markdown
Contributor Author

@kastelecn, will this break anything for DEODE or have you already detached the config part?

@kastelecn

Copy link
Copy Markdown
Contributor

@kastelecn, will this break anything for DEODE or have you already detached the config part?

We have already detached config part

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.

4 participants