-
Notifications
You must be signed in to change notification settings - Fork 251
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
Develop drag suite intent mods -- Changed UGWP diagnostic variable declaration intents from 'out' to 'inout' #1612
Conversation
@mdtoyNOAA We are currently working on #1529. As discussed before, this pr can be combined to #1597. I will check again after we merge in #1529. We can coordinate with @binli2337 then. |
@jkbk2004 Sounds good. |
It does not appear that the GNU suite was run. Also FV3 is out of date. |
…r-model into develop_drag_suite_intent_mods
@jkbk2004 I've merged the latest changes to "ufs-weather-model" and "FV3ATM" in my fork. Would you like me to retest Intel and test GNU? |
@mdtoyNOAA you are bringing in the change from gsl fork branches. It's a bit tricky. Easiest solution is to go with community develop and emc fv3 develop. Since this pr is small change, I think it's doable to re-create pr. What do you think? we are still working on #1529. There is enough time. |
@jkbk2004 Actually, I am not bringing in changes from the GSL fork branches. Although I did originally fork my ufs-weather-model repo from NOAA-GSL, the branches related to this PR are strictly based on the ufs-community repos. To double check this, I just cloned my ufs-weather-model repo into a fresh directory and "git diffed" each component, i.e., ufs-weather-model, fv3atm, and ccpp/physics, and they are all synched (except for my "inout" mods) to the ufs-community repos/branches. So, I shouldn't need to redo the PR. Please let me know if you agree. |
cool! sounds at least synching branch is working. Once we don't see conflictions to resolve, we are fine. |
@mdtoyNOAA hera is very slow from yesterday. Do you have access to Cheyenne? I can help to make a quick test on cheyenne with gnu. |
@jkbk2004 No, I don't have access to Cheyenne. |
@mdtoyNOAA let me give a quick test on cheyenne. Anyway, we like to start working on this pr today with combining to #1597 |
RegressionTests_cheyenne.gnu.log cheyenn.gnu reproduces |
@mdtoyNOAA Ok! #1529 was merged in. So, we can start working to combine this pr to #1597. Can you sync up ccpp and fv3 one more time? I will ask @binli2337 to point to your fv3 branch in his pr. |
…r-model into develop_drag_suite_intent_mods
@jkbk2004 I am working on it right now. Can you confirm that there have been changes to the submodules 'WW3' and 'upp'? |
Yes, upp was update: https://github.com/NOAA-EMC/UPP/tree/b37f8ab7b0f298346d79a37e0c5d4a64037fd4d4 |
Sorry, I meant ’NOAHMP-interface/noahmp’.
… On Feb 17, 2023, at 3:50 PM, JONG KIM ***@***.***> wrote:
Yes, upp was update: https://github.com/NOAA-EMC/UPP/tree/b37f8ab7b0f298346d79a37e0c5d4a64037fd4d4 <https://github.com/NOAA-EMC/UPP/tree/b37f8ab7b0f298346d79a37e0c5d4a64037fd4d4>
ww3 no update and the hash is still in last month: https://github.com/NOAA-EMC/WW3/tree/b93b9f00118f6fb316fd2289dff10b1455357f3f <https://github.com/NOAA-EMC/WW3/tree/b93b9f00118f6fb316fd2289dff10b1455357f3f>
—
Reply to this email directly, view it on GitHub <#1612 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARRVLIBNZOKZZE6R5UCI3ZLWX76EHANCNFSM6AAAAAAU26DLMU>.
You are receiving this because you were mentioned.
|
Oh! you are correct. noah-mp was update. |
@jkbk2004 I updated my UPP branch and it looks like the latest hash is '84cp0b8f', not 'b37f8ab7'. Should I revert back to this older hash? Gitlog below: commit 84cb0b8ff4d72506edddff6204d00f39bc3f035a (HEAD, origin/develop, origin/HEAD)
commit ad56e5ca699728df7b300e3624807a6d21dcf186
commit 8c7ca6f36a0347b457e5de89b3b40c79a87ca353
commit b37f8ab7b0f298346d79a37e0c5d4a64037fd4d4 |
upp b37f8ab7 is the one we are using. |
@jkbk2004 Okay, I think I have it synched and pushed properly. Let me know if it looks okay. Thanks. |
@mdtoyNOAA one thing to confirm. this pr has not much to do with noahmp, right? Only code change comes from ccpp. So, @binli2337 can simply poin to your fv3 branch to combine the PRs, right? |
That’s correct. This PR has nothing to do with noahmp.
… On Feb 17, 2023, at 5:09 PM, JONG KIM ***@***.***> wrote:
@mdtoyNOAA <https://github.com/mdtoyNOAA> one thing to confirm. this pr has not much to do with noahmp, right? Only code change comes from ccpp. So, @binli2337 <https://github.com/binli2337> can simply poin to your fv3 branch to combine the PRs, right?
—
Reply to this email directly, view it on GitHub <#1612 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARRVLIAT5TNPSKHQOBYKYP3WYAHKZANCNFSM6AAAAAAU26DLMU>.
You are receiving this because you were mentioned.
|
Description
This pull request fixes Issue #37 of the ufs-community/ccpp-physics repository. The UGWP diagnostic variables (i.e., dusfc_ms, dvsfc_ms, tdaux2d_ms, datauy2d_ms, etc.) are declared with "intent(out)" and initialized in module unified_ugwp.F90, then they are passed to subroutine "drag_suite_run" (in drag_suite.F90). In this subroutine, the UGWP diagnostic variables should have been declared with "intent(inout)" instead of "intent(out)". This PR fixes this.
This PR does not change any results.
Top of commit queue on: TBD
Input data additions/changes
Anticipated changes to regression tests:
Subcomponents involved:
Combined with PR's (If Applicable):
Commit Queue Checklist:
Linked PR's and Issues:
Dependent pull requests:
Related issue:
Testing Day Checklist:
Testing Log (for CM's):