-
Notifications
You must be signed in to change notification settings - Fork 253
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
Add new PBL diagnostic variables dkt and dku #505
Add new PBL diagnostic variables dkt and dku #505
Conversation
ufs-weather-model regression tests on Hera have passed successfully. |
Good morning @BinLiu-NOAA , you're on top of the commit queue now. Could you please bring your ufs-weather-model fork up-to-date with ufs-weather-model/develop and make sure your FV3 fork is also up-to-date with fv3atm/develop? Thank you. |
@BrianCurtis-NOAA please note the comment I left in the fv3atm PR that needs to be addressed (in addition to updating to the head of the authoritative branches): NOAA-EMC/fv3atm#269 (comment) |
Yes, make sure you fix the fv3atm issue and update the pointer here afterwards. Thanks Dom. |
Don't forget to bring this branch up-to-date with ufs-community/ufs-weather-model: develop after you bring your fv3atm branch up-to-date as well. |
@BrianCurtis-NOAA I am working on to bring this branch up to date with the latest develop branch. It is currently 1-2 commits behind. Will let you know once it's done. Should be done shortly. Thanks! |
@BrianCurtis-NOAA I looked one of the failed test err log: By any chance, there might be system side issue (file system, io, wallclock limit, etc.), which could have caused the failure? |
It's very possible. Once my Dell P3 run is done i'll retry the cray. |
Machine: hera |
hera intel test error was a slurm issue, nothing related to the RT's, I'm re-running that one test and will add it to the log |
@MinsukJi-NOAA i'm not sure if the issue showing for the failed run-ci tests is something we should be concerned about. Do we need to change anything? |
@BrianCurtis-NOAA this is an ec2/docker issue and not a testing issue, and i suggest going ahead with the PR. I expect this issue to be fixed with an upcoming PR. |
@MinsukJi-NOAA Thanks! I'm just waiting on the failed test to re-run on hera.intel, still sitting in pending |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code can be committed once all RT (except jet) is done and the FV3 repo is updated.
FV3 PR is merged. Please revert .gitmodules and update pointer to NOAA-EMC:develop |
@BrianCurtis-NOAA, Done to revert .gitmodules and update pointer to NOAA-EMC:develop. Please double check. |
The hash's match. Waiting on @climbfuji approval. |
Global variable use has been removed in setup.py, and reduced in generate_FV3LAM_wflow.py. The use of globals is a carry-over from the bash era of this utility, and does not meet modern coding standards.
PR Checklist
Ths PR is up-to-date with the top of all sub-component repositories except for those sub-components which are the subject of this PR. Please consult the ufs-weather-model wiki if you are unsure how to do this.
This PR has been tested using a branch which is up-to-date with the top of all sub-component repositories except for those sub-components which are the subject of this PR
An Issue describing the work contained in this PR has been created either in the subcomponent(s) or in the ufs-weather-model. The Issue should be created in the repository that is most relevant to the changes in contained in the PR. The Issue and the dependent sub-component PR are specified below.
If new or updated input data is required by this PR, it is clearly stated in the text of the PR.
Description
This PR adds new PBL diagnostic variables dkt and dku (atmosphere heat and momentum diffusivity) used in HAFS. This PR should not change answers, neither require any library or module updates.
Issue(s) addressed
Testing
How were these changes tested? What compilers / HPCs was it tested with? Are the changes covered by regression tests? (If not, why? Do new tests need to be added?) Have regression tests and unit tests (utests) been run? On which platforms and with which compilers? (Note that unit tests can only be run on tier-1 platforms)
- [ ] jet.intel NOTE: SKIPPED DUE TO JET PM
Dependencies
Do PRs in upstream repositories need to be merged first?
If so add the "waiting for other repos" label and list the upstream PRs