-
Notifications
You must be signed in to change notification settings - Fork 176
Address some compiler warnings in UFSATM #1025
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@NickSzapiro-NOAA Please add corresponding fv3_dycore PR as a dependency |
|
Thanks @DusanJovic-NOAA. The ufsatm, ccpp-physics, and dycore changes are all independent, if need be |
|
Could we get approvals on this PR so that we can process its GFSv17 priority parent PR? (WM #2935) |
|
@NickSzapiro-NOAA ufs-community/ccpp-physics#312 has been merged. Please update the submodule pointer for ccpp-physics (ufs-community/ccpp-physics@14f24db) and revert the .gitmodules file in preparation for the merge. |
|
@NickSzapiro-NOAA Same for NOAA-GFDL/GFDL_atmos_cubed_sphere#396. You can update the atmos_cubed_sphere submodule pointer to b0a1b09. |
|
Sure. Please let me know if ok |
|
@NickSzapiro-NOAA It looks good to me! |
Description
(Instructions: this, and all subsequent sections of text should be removed and filled in as appropriate.)
One round of straight-forward fixes for some of the compiler warnings raised in compiling cpld_debug_gfsv17 to improve code quality and prepare for operational implementation
Issue(s) addressed
Link the issues to be closed with this PR, whether in this repository, or in another repository.
(Remember, issues should always be created before starting work on a PR branch!)
Testing
Tested via ufs-weather-model RTs and compile err logs with Intel and GNU compilers on Ursa
Are the changes covered by regression tests? (If not, why? Do new tests need to be added?) Yes
Have the ufs-weather-model regression test been run? On what platform? Yes, Ursa
Dependencies
If testing this branch requires non-default branches in other repositories, list them.
Those branches should have matching names (ideally)
Do PRs in upstream repositories need to be merged first?
If so add the "waiting for other repos" label and list the upstream PRs