Repository navigation
Improved blending of 1D and 3D turbulence schemes - #752
James Bruten (james-bruten-mo) merged 40 commits into
Conversation
…hallow CTH instead of zhpar
iboutle
left a comment
There was a problem hiding this comment.
Thanks Adrian,
My main comment is around the new test being introduced. blopt4 is a bit opaque, especially given this magic number doesn't really mean anything in the lfric namelist. But also, I'm reluctant to end up with a plethora of different tests for every individual namelist option. So...
- how about calling the test
raldev, and it can be built on with other things aimed at future RAL releases - In the optional config, instead of duplicating everything from the ral3 config, just include the bits which you need that are different from the ral3 config, and then include both when setting up the test.
- Call the optional config something descriptive like
blend_shcuor suchlike.- To get the metadata checker not to fail, you may have to include slightly more than you need here, as it needs to be a valid config that can be applied to the base app. That probably just means including the options needed to switch Smagorinsky on, since that is off in the base app.
Thanks!
…w options under a better named blend_shcu opt file
No CoPilot, or other AI, was used on the code change at all. I tried taking advice from CoPilot on how to merge my vn3.2 branch up to main in a separate branch but keeping the same PR. But that turned out to be bad advice that I reverted and just upgraded my "vn3.2"-named branch to main instead. |
Co-authored-by: Ricky Wong <141156427+mo-rickywong@users.noreply.github.com>
Co-authored-by: Ricky Wong <141156427+mo-rickywong@users.noreply.github.com>
Co-authored-by: Ricky Wong <141156427+mo-rickywong@users.noreply.github.com>
Agreed it wasn't clear - I hope this rephrase is ok?
Second attempt to get this comment making sense
Another tweak to the phrasing
|
Thanks Ricky Wong (@mo-rickywong) for spotting all those. I've had a go at fixing them, mostly taking your suggestions but having a go at my own word-smithing in others. Are those ok now? In case you find it helpful, the full set of changes I've made are here |
Ricky Wong (mo-rickywong)
left a comment
There was a problem hiding this comment.
Few other changes spotted
There was a problem hiding this comment.
| description=Smagorinsky(Smag) subgrid mixing scheme option |
Values titles have been abbreviated inconsistently for space I presume. Add the short hand and make titles consistent (the fully word is in the help as it should be)
There was a problem hiding this comment.
Done
| values='3d_smag', '2d_smag', 'blend_smag_fa','blend_1dbl_fa' | ||
| trigger=namelist:mixing=shallow_cu_maxtop: 'blend_cth_shcu_only' ; | ||
| =namelist:mixing=cap_blended_ml: 'blend_smag_fa', 'blend_1dbl_fa', 'blend_cth_shcu_only' ; | ||
| value-titles=3D Smagorinsky, 2D Smagorinsky + 1D BL, Blended scheme + Smag above, |
There was a problem hiding this comment.
| value-titles=3D Smagorinsky, 2D Smagorinsky + 1D BL, Blended scheme + Smag above, | |
| value-titles=3D Smag, 2D Smag + 1D BL, Blended scheme + Smag above, |
There was a problem hiding this comment.
Done
| help=Cap the magnitude of the blended 1D-3D mixing length | ||
| =by the 1D mixing length. |
There was a problem hiding this comment.
Just a comment, the way this reads, to the unfamiliar reader it the D could be read as "Dimensional", consider rewording?
Actually re-reading this, not sure it makes to me, please reword.
There was a problem hiding this comment.
I've tried a wholesale reworking of this help, which I hope is clearer - thanks for pointing out
|
|
||
| [namelist:mixing=cap_blended_ml] | ||
| compulsory=true | ||
| description=Cap the blended mixing length by the 1D |
There was a problem hiding this comment.
| description=Cap the blended mixing length by the 1D | |
| description=Cap the blended mixing length at 1D |
There was a problem hiding this comment.
Done
| compulsory=true | ||
| description=Max. permitted cloud top height for shallow cloud blending | ||
| help=The maximum permitted cloud top height (in metres) for shallow cumulus clouds | ||
| =to be diagosed. This is used in the blending weight length-scale calculation |
There was a problem hiding this comment.
| =to be diagosed. This is used in the blending weight length-scale calculation | |
| =to be diagnosed. This is used in the blending weight length-scale calculation |
There was a problem hiding this comment.
Doh! Done
More improvements to the meta data and help panels
|
Thanks again, Ricky Wong (@mo-rickywong), for spotting those. Hopefully all covered in this latest commit |
|
Hi Ricky Wong (@mo-rickywong), I just spotted this PR is down as "with the developer to make changes". I'd attempted to respond to your comments 2 weeks ago but have no idea how to revert the PR to "in code review", if that's even something I'm meant to do. Apologies for not understanding the process well enough but it would be good to get this PR through your review, even if we are thinking of waiting until after #742 for the commit. Thanks |
Hi Adrian, When you're ready for another review, please click the little "circle" icon next to their name in the top right. That'll then set the state back to Review and notify the reviewer |
|
There is still requested changes over looked, minor case settings. These were in the previous passes, I've not added new requests. There isn't anything fundamentally wrong as far as I can see with the rest of it, though was waiting to getting to running green on trunk before approving and putting on the queue for commit. |
Ricky Wong (mo-rickywong)
left a comment
There was a problem hiding this comment.
Not sure if git is submitting these or not
I've added a comment against that particular request now, hoping my changed phrasing is good enough? Happy to iterate, though |
|
Thanks for chasing Ricky Wong (@mo-rickywong) and I hope I have now covered all your concerns. I'm not sure of the protocol but I'm assuming I leave it to you to formally "resolve" the comments? |
|
Looks to have updated, the new kgo file is failing at head of trunk so it will need a KGO update on commit. Approved |
Ricky Wong (mo-rickywong)
left a comment
There was a problem hiding this comment.
Looks okay now
cb385a8
into
MetOffice:main
PR Summary
Sci/Tech Reviewer: Shusuke Nishimoto (@mo-snishimoto)
Code Reviewer: Ricky Wong (@mo-rickywong)
RMED problem #111 and development ticket #113 document problems found with the scale-aware wind gust diagnostic (stash 3515) that are much improved by these revisions to the
method= 'blend_cth_shcu_only'option for how the 1D column and 3D Smagorinsky turbulence schemes are blended as a function of resolution. There is also potential for small benefit from including an additional new option(cap_blended_ml)to cap the blended length scale to be at most the physical length scale from the 1D scheme.Code Quality Checklist
Testing
trac.log
Test Suite Results - lfric_apps - testmain_blending_opt4/run1
Suite Information
Task Information
❌ failed tasks - 3
⌛ waiting tasks - 2
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