Skip to content

Update regional rose-stem to RAL4.beta1 - #764

Open
iboutle wants to merge 7 commits into
MetOffice:mainfrom
iboutle:ral4b1
Open

Update regional rose-stem to RAL4.beta1#764
iboutle wants to merge 7 commits into
MetOffice:mainfrom
iboutle:ral4b1

Conversation

@iboutle

@iboutle iboutle commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

PR Summary

Sci/Tech Reviewer: annemccabe
Code Reviewer: Pierre Siddall (@Pierre-siddall)

Update rose-stem jobs to remove reference to ral3 (which is UM based) and start referring to things as ral4. Currently, this configuration is still a work in progress, and also is not the complete definition of ral4.beta1, with changes still making their way onto trunk in #699 and #725, which will update these apps in-turn.

This change adds new data to be stored in big_data_dir. Currently this exists at /data/users/ian.boutle/ral4b1 on spice and the HPC (note spice folder is smaller as it only contains the data required by spice jobs).

Code Quality Checklist

  • I have performed a self-review of my own code
  • My code follows the project's style guidelines
  • Comments have been included that aid understanding and enhance the readability of the code
  • My changes generate no new warnings
  • All automated checks in the CI pipeline have completed successfully

Testing

  • I have tested this change locally, using the LFRic Apps rose-stem suite
  • If any tests fail (rose-stem or CI) the reason is understood and acceptable (e.g. kgo changes)
  • I have added tests to cover new functionality as appropriate (e.g. system tests, unit tests, etc.)
  • Any new tests have been assigned an appropriate amount of compute resource and have been allocated to an appropriate testing group (i.e. the developer tests are for jobs which use a small amount of compute resource and complete in a matter of minutes)

trac.log

Test Suite Results - lfric_apps - ral4b1/run1

Suite Information

Item Value
Suite Name ral4b1/run1
Suite User ian.boutle
Workflow Start 2026-09-08T11:32:23
Groups Run developer', 'lfric_atm_extra', 'lfric_atm_ral_ex1a_weekly
Dependency Reference Main Like
casim MetOffice/casim@2026.07.1 True
jules MetOffice/jules@2026.07.1 True
lfric_apps iboutle/lfric_apps@ral4b1 False
lfric_core MetOffice/lfric_core@3e965e8 True
moci MetOffice/moci@2026.07.1 True
SimSys_Scripts MetOffice/SimSys_Scripts@77a5166 True
socrates MetOffice/socrates@2026.07.1 True
socrates-spectral MetOffice/socrates-spectral@2026.07.1 True
ukca MetOffice/ukca@9fc2b6d True

Task Information

❌ failed tasks - 4
Task State
check_lfric_atm_comp_tran_ref_3d_l120-BiP64x64-1500x1500_MG_ex1a_cce_fast-debug-32bit failed
check_lfric_atm_rce-BiP64x64-1500x1500_MG_azspice_gnu_fast-debug-32bit failed
check_lfric_atm_rce-BiP64x64-1500x1500_MG_ex1a_cce_fast-debug-32bit failed
kgo_groups_checker failed
✅ succeeded tasks - 1386
⌛ waiting tasks - 2
Task State
housekeep_azspice waiting
housekeep_ex1a waiting

Security Considerations

  • I have reviewed my changes for potential security issues
  • Sensitive data is properly handled (if applicable)
  • Authentication and authorisation are properly implemented (if applicable)

Performance Impact

  • Performance of the code has been considered and, if applicable, suitable performance measurements have been conducted

AI Assistance and Attribution

  • Some of the content of this change has been produced with the assistance of Generative AI tool name (e.g., Met Office Github Copilot Enterprise, Github Copilot Personal, ChatGPT GPT-4, etc) and I have followed the Simulation Systems AI policy (including attribution labels)

Documentation

  • Where appropriate I have updated documentation related to this change and confirmed that it builds correctly

PSyclone Approval

  • If you have edited any PSyclone-related code (e.g. PSyKAl-lite, Kernel interface, optimisation scripts, LFRic data structure code) then please contact the HPC Optimisation Team

Sci/Tech Review

  • I understand this area of code and the changes being added
  • The proposed changes correspond to the pull request description
  • Documentation is sufficient (do documentation papers need updating)
  • Sufficient testing has been completed

(Please alert the code reviewer via a tag when you have approved the SR)

Code Review

  • All dependencies have been resolved
  • Related Issues have been properly linked and addressed
  • CLA compliance has been confirmed
  • Code quality standards have been met
  • Tests are adequate and have passed
  • Documentation is complete and accurate
  • Security considerations have been addressed
  • Performance impact is acceptable

@iboutle iboutle added the KGO This PR contains changes to KGO label Sep 8, 2026
@iboutle iboutle added this to the Autumn 2026 milestone Sep 8, 2026

@annemccabe annemccabe left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I've compared the changes to the RAL4beta1 configuration that we have in the RNS. The only differences are related to the native wind transport and leonard term options from the two issues that have yet to go on the trunk.

I'm happy for this to be passed into code review now.

@benfitzpatrick

Copy link
Copy Markdown

I am happy with the README that Ian's supplied with the start dumps and LBC files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

KGO This PR contains changes to KGO

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants