-
Notifications
You must be signed in to change notification settings - Fork 162
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
Update in-line post for RRFS and GFS #641
Conversation
@DusanJovic-NOAA I updated io/post_fv3.F90 based on your comment. |
@junwang-noaa and @DusanJovic-NOAA Any actions are needed from my side? Thanks! |
@DusanJovic-NOAA Please let me know your comment on the commit 78cfb35. |
Not related to this PR, but since I'm looking at the code I thought I should mention, there are many OMP directives in which
Also, code indentation is terrible, it is very difficult to reason about the code and understand the logic with inconsistent indentation. This file (post_fv3.F90) requires some serious clean up. |
@DusanJovic-NOAA We could submit another PR to clean up these non-fatal bugs/typos later. |
Sure. Like I said, not related to this PR. |
@DusanJovic-NOAA @junwang-noaa @zhanglikate @EricJames-NOAA Please let me know your comments on my latest commit 246acf2. |
tests are all done at weather model pr: ufs-community/ufs-weather-model#1690 @DusanJovic-NOAA @zhanglikate @EricJames-NOAA Please, go ahead for final reviews and approvals. @WenMeng-NOAA do you think we need to create an issue to follow up Dusan's comments to clean up codes? |
@jkbk2004 Yes, we can create an issue for that at fv3atm repos. Do you want me to create or you will do it? Thanks! |
@WenMeng-NOAA we can resolve the conversations and merge in this pr. can you resolve? |
|
Yes, all conversations are solved. |
@WenMeng-NOAA I will let you create an issue to clean up code. merging the pr now. |
Description
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
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 the ufs-weather-model regression test been run? On what platform?
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