Safely compute height fields for continuous function spaces#277
Safely compute height fields for continuous function spaces#277tommbendall wants to merge 8 commits intoMetOffice:mainfrom
Conversation
Update stable for vn3.1
|
There is a change to kgo here, so likely to change kgos in lfric-jedi. @DanStoneMO can you test / update this from lfric-jedi perspective? |
jameskent-metoffice
left a comment
There was a problem hiding this comment.
This PR runs the LFRic Apps tests for the linked core ticket. The kgos all change, but these are bit level changes and as shown in the helpful plots attached to the PR, there are not any science changes (the plots all look like main). Therefore this passes science review.
Thanks @adammaycock - adding linked label while we test. PR to follow if it is required. |
thomasmelvin
left a comment
There was a problem hiding this comment.
Missing KGO's are back, so i'm happy
There was a problem hiding this comment.
Im not sure why these files appear to have been deleted (the same comment applies to all the C48 baroclinic tests)
|
JEDI-side PRs are now up at: I'll approve our review shortly if there's no other concerns from us @ss421 @adammaycock |
Thanks, it looks good to me. Perhaps it would be worth updating the |
PR Summary
Sci/Tech Reviewer: @jameskent-metoffice
Code Reviewer: @allynt
This PR contains KGO changes from the linked ticket LFRic-Core #284, which fixes the
sci_get_heightkernel.Continuous height fields (e.g. W2) change at the bit-level, causing KGO changes to any test that uses these fields. The science impact is entirely neutral however.
Linked-To
Blocks
Results
Comparing plots from gungho_model and lfric_atm tests for this branch and vn3.1 shows that the science impact is minimal:
Code Quality Checklist
Testing
trac.log
Test Suite Results - lfric_apps - height_continuous_apps/run5
Suite Information
Task Information
✅ succeeded tasks - 1511
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