Conversation
|
C12 - 2T seems to be failing KGOs in testing. All others are fine, as are run throughs. Reverting all changes fixes KGO. Investigation WIP. |
Test Suite Results - lfric_apps - ex_coef/run19Suite Information
Task Information✅ succeeded tasks - 10 |
|
KGO for C12 full holds |
|
Copies of listing files: |
|
Post a KGO update, fast holds too: Test Suite Results - lfric_apps - ex_coef/run23Suite Information
Task Information✅ succeeded tasks - 18 |
|
All I've checked the namelist for I did expand OMP coverage, possibly to sections which under a flag may never use it. (However PSyclone will likely do the same). These have always occured with the removal of the j loop, so there could be something I've missed, where j is required. But given how localised it is to just |
|
All liner model KGO issues seem related to issues on trunk, as latest tests run through fine. With this in mind, I'm going to push this to review this morning, as I am getting consistent enough results, that only that C12 test is failing KGOs, and the rest of the issues are trunk related. |




PR Summary
Sci/Tech Reviewer: @christophermaynard
Code Reviewer: @mo-alistairp
Remove the j loop which is adversely affecting performance in the boundary layer, and improve blocking loops.
NOTE - it seems that the C12 fast debug 2T run is being affected by a KGO change. No other OMP, or developer test is failing it's KGO.
The
allgroup will be run with final commits moving into SR, this will also need a Science approval for the KGO.Code Quality Checklist
Testing
trac.log
Test Suite Results - lfric_apps - ex_coef/run39
Suite Information
Task Information
❌ failed tasks - 3
🚫 submit-failed tasks - 1
Test Suite Results - lfric_apps - ex_coef/run30
Suite Information
Task Information
✅ succeeded tasks - 51
Test Suite Results - lfric_apps - ex_coef/run6
Suite Information
Task Information
❌ failed tasks - 5
Security Considerations
Performance Impact
AI Assistance and Attribution
Documentation
PSyclone Approval
Sci/Tech Review
(Please alert the code reviewer via a tag when you have approved the SR)
Code Review