Skip to content

Import of high order turbulence closure scheme - #734

Open
Shusuke Nishimoto (mo-snishimoto) wants to merge 12 commits into
MetOffice:mainfrom
mo-snishimoto:3dte_mk1
Open

Import of high order turbulence closure scheme#734
Shusuke Nishimoto (mo-snishimoto) wants to merge 12 commits into
MetOffice:mainfrom
mo-snishimoto:3dte_mk1

Conversation

@mo-snishimoto

@mo-snishimoto Shusuke Nishimoto (mo-snishimoto) commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

PR Summary

Sci/Tech Reviewer: Adrian Lock (@Adrian-Lock)
Code Reviewer: Matthew Hambley (@MatthewHambley)

This PR imports high order turbulence closure scheme (3DTE Mk1 scheme) in UM to LFRic.

Please see #46 for details, documentation and extra tests performed.

Linked PRs

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 - test_3dte_mk1/run2

Suite Information

Item Value
Suite Name test_3dte_mk1/run2
Suite User shusuke.nishimoto
Workflow Start 2026-09-09T18:28:40
Groups Run all
Dependency Reference Main Like
casim MetOffice/casim@2026.07.1 True
jules MetOffice/jules@2026.07.1 True
lfric_apps mo-snishimoto/lfric_apps@3dte_mk1 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 - 2
Task State
check_lfric_atm_3dte-seuk_MG_azspice_gnu_fast-debug-32bit failed
check_lfric_atm_3dte-seuk_MG_ex1a_cce_fast-debug-32bit failed
✅ succeeded tasks - 1609
⌛ 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 TCD 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

@mo-snishimoto Shusuke Nishimoto (mo-snishimoto) added the macro This PR contains a metadata upgrade macro label Aug 25, 2026
@github-actions github-actions Bot added the cla-modified The CLA has been modified as part of this PR - added by GA label Aug 25, 2026
@mo-snishimoto Shusuke Nishimoto (mo-snishimoto) removed the cla-modified The CLA has been modified as part of this PR - added by GA label Aug 25, 2026
@iboutle iboutle mentioned this pull request Aug 25, 2026
28 tasks

@iboutle iboutle 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.

A few comments below. Thanks!

Comment thread interfaces/physics_schemes_interface/rose-meta/um-boundary_layer/versions.py Outdated
Comment thread science/gungho/rose-meta/lfric-gungho/HEAD/rose-meta.conf Outdated
@github-actions github-actions Bot added the cla-modified The CLA has been modified as part of this PR - added by GA label Aug 26, 2026
@mo-snishimoto

Shusuke Nishimoto (mo-snishimoto) commented Aug 26, 2026

Copy link
Copy Markdown
Contributor Author

Hi iboutle, Thank you for the careful check and comments.
I fixed my branch, following your comment.
I also confirmed this change doesn't affect KGOs.

@iboutle iboutle 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.

Thanks, looks good to me now. Just to note the KGO change for the coupled model should disappear when this is merged up to the head of main

@DanStoneMO DanStoneMO 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.

This needs a linked PR in JEDI, which is now up at: https://github.com/MetOffice/lfric-jedi/pull/1335

@DanStoneMO DanStoneMO added the Linked Jedi This PR is linked to a Jedi PR - this will be managed by the DA team label Sep 1, 2026
@mo-snishimoto

Copy link
Copy Markdown
Contributor Author

This needs a linked PR in JEDI, which is now up at: https://github.com/MetOffice/lfric-jedi/pull/1335

Thanks for the comment. I edited the PR summary to include it.

Comment thread applications/lfric_atm/example/configuration.nml Outdated
Comment thread science/gungho/rose-meta/lfric-gungho/versions.py

@Adrian-Lock Adrian Lock (Adrian-Lock) 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.

First many thanks for the very helpful "namelist_and_diagnostics.pdf" and "code_change_detail.pdf" documentation on the accompanying issue. In addition to my comments on the files, I have two further comments:

I apologise for my most significant proposal, which is to use more meaningful names for the two turbulence schemes than the old UM "9C" and "1A", which unfortunately has quite far reaching consequences. I am very happy to take other suggestions but my proposal is to use "Kprof" and "HoC", respectively.

I like having the "blending" options in the blayer namelist, rather than mixing - as long as everyone else is happy that's good.  I'll note explicitly, though, the up-coming clash with my PR #752 where I've added a new blending option

Overall, even if simply porting code from the UM, the interfacing and coupling with the rest of lfric is a very impressive piece of work. Many thanks again.

Comment thread applications/lfric_atm/metadata/field_def_diags.xml Outdated

@Adrian-Lock Adrian Lock (Adrian-Lock) 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.

Thank you so much for all that relabeling of the scheme names.

Apologies if I missed it, but it would be good to open an issue to port UMDP 25, that describes this scheme, to the new lfric documentation area. No need to get that port done as part of this PR.

@github-actions github-actions Bot removed the cla-modified The CLA has been modified as part of this PR - added by GA label Sep 10, 2026
@mo-snishimoto

Shusuke Nishimoto (mo-snishimoto) commented Sep 10, 2026

Copy link
Copy Markdown
Contributor Author

Thank you so much for looking the code again and the approvement.

Though I am prepared for the possibility that further conflict resolution with #714 and #752 might be required depending on the timing of the merge, I also have merged the latest main and resolved conflicts in the following files, heading for merge:

  • science/gungho/rose-meta/lfric-gungho/rose-meta.conf
  • science/gungho/rose-meta/lfric-gungho/versions.py

I also modified following unit-tests in the same way as #725 and #752 , (reflected mixing namelsit change to feign_mixing_config subroutine):

  • science/gungho/unit-test/kernel/diffusion/diffusion_momentum_flux_kernel_mod_test.pf
  • science/gungho/unit-test/kernel/diffusion/divergence_momentum_flux_kernel_mod_test.pf

I confirmed rose-stem (all) suite ends successfully and KGO change for the coupled model disappeared as Ian said above.
I updated KGO files of 3dte tests since they are affected by the merge of #656 .
I replaced trac.log in the ticket summary with the latest one.

Apologies if I missed it, but it would be good to open an issue to port UMDP 25, that describes this scheme, to the new lfric documentation area. No need to get that port done as part of this PR.

Thank you for the suggestion.
Yes, I would love to try converting UMDP 25 into LFRic documentation in another PR.

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

Labels

enhancement New feature or request KGO This PR contains changes to KGO Linked Jedi This PR is linked to a Jedi PR - this will be managed by the DA team macro This PR contains a metadata upgrade macro

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants