Skip to content

Transmute bl exp and imp kernels over domain#377

Draft
MetBenjaminWent wants to merge 4 commits intoMetOffice:mainfrom
MetBenjaminWent:transmute_bl_exp_imp_kernels
Draft

Transmute bl exp and imp kernels over domain#377
MetBenjaminWent wants to merge 4 commits intoMetOffice:mainfrom
MetBenjaminWent:transmute_bl_exp_imp_kernels

Conversation

@MetBenjaminWent
Copy link
Contributor

@MetBenjaminWent MetBenjaminWent commented Mar 17, 2026

PR Summary

Create or enable Transformation scripts for the boundary layer kernels which affect the domain to add OMP directives to either the outer loop, or in an occurrence, an inner loop which runs over a larger bound.
interfaces/physics_schemes_interface/source/kernel/bl_exp_kernel_mod.F90 - Custom Script
interfaces/physics_schemes_interface/source/kernel/bl_imp_kernel_mod.F90 - Global with Override
interfaces/physics_schemes_interface/source/kernel/bl_imp2_kernel_mod.F90 - Global with Override

Reviewer note, I'm yet to performance test this one, as fixes included in #231 are blocking this, as is the lack of max time in Vernier, which will need developing.
I'm going to finish all of the Wave 2 ones noted in #106 together and get updated performance data for each of these issues, and progress in the boundary layer.

Could the change-set be reviewed sans the performance data, just to keep this ticket moving, but hold the final approval until I've added this? Thanks

Sci/Tech Reviewer:
Code Reviewer:

Umbrella Issue: #106
Issue: #361

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

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

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.

2 participants