-
Notifications
You must be signed in to change notification settings - Fork 250
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
(1) update MOM6 to its main branch 20220902 commit (2) update GNU to include s2swa tests #1401
(1) update MOM6 to its main branch 20220902 commit (2) update GNU to include s2swa tests #1401
Conversation
@jiandewang we can start working on the pr. can we combine in #1388 ? |
@jiandewang once you update your branch, I will make a PR to add the S2SWA test for GNU (script level changes only). |
@DeniseWorthen just updated my branch |
yes we can combine them |
@jiandewang #1388 needs only changes in rt_gnu.conf. I think its possible to manually add in but @DeniseWorthen will you create pr to jiande's branch? |
I made a PR to @jiandewang UWM branch a couple of hours ago. |
Feature/adds2swa gnutests
just saw that, merged. |
@jiandewang thanks! I will add new BL_DATE and start testing RT runs on RDHPCs. @BrianCurtis-NOAA will test on wcoss2 |
WCOSS2 on baseline creation: Failed test hafs_regional_atm_wav (test 073) walltime 1813 exceeded limit 1800. |
on-behalf-of @ufs-community <[email protected]>
on-behalf-of @ufs-community <[email protected]>
Automated RT Failure Notification |
MOM6 PR merged, let me know when it's time to switch submodule in UFS |
my fresh clone for the branch of this PR shows |
now I see |
@jiandewang Should HYCOM in UFS be at the HEAD of the emc/develop branch? |
yes, this is what's inside .gitmodules and my fresh clone for the above is
|
can someone repeat what I just did: cd HYCOM-interface/HYCOM what I got is
it should point to emc.develop, not the HEAD my cloned directory on HERA: /scratch1/NCEPDEV/climate/Jiande.Wang/MOM6-update/MOM6-update-20220902/Final/ufs-weather-model during the submodule update --init --recursive, it had
I also cloned the ufs develop branch, and got the same thing |
Yes, I see the same on other machines. BTW, we need to use 'module load git/2.28.0' on orion. |
I checked out a ufs-wm hash around early June. |
Please hold while we track down this HYCOM issue. |
The hycom hash should not have changed. Brian and I have checked w/ Bin Liu. The emc/develop branch in our fork was updated---and we're not clear why. Please don't merge until we can straighten this out. The issue is that we cannot find the hash 09bdf00 currently in emc/develop. For instance: git clone https://github.com/NOAA-EMC/HYCOM-src.git |
The last event in NOAA-EMC/HYCOM-src repo that changed the HEAD of the emc/develop branch from 09bdf00 to 8d24702 was: [
{
"id": "23923922315",
"type": "PushEvent",
"actor": {
"id": 11394126,
"login": "aerorahul",
"display_login": "aerorahul",
"gravatar_id": "",
"url": "https://api.github.com/users/aerorahul",
"avatar_url": "https://avatars.githubusercontent.com/u/11394126?"
},
"repo": {
"id": 389701838,
"name": "NOAA-EMC/HYCOM-src",
"url": "https://api.github.com/repos/NOAA-EMC/HYCOM-src"
},
"payload": {
"push_id": 10978986151,
"size": 66,
"distinct_size": 1,
"ref": "refs/heads/emc/develop",
"head": "8d247021484c5cb7f8ded897c1e2020c028ef7e9",
"before": "09bdf00e500d99e2b8811c0571258f86c14efc30",
"commits": [
{
"sha": "8c5cc444f5065d5fd8c74582db95c360e0e4a99f",
"author": {
"email": "[email protected]",
"name": "TRasmussen"
},
"message": "Merge pull request #2 from HYCOM/master\n\nUpdate from upstream",
"distinct": false,
"url": "https://api.github.com/repos/NOAA-EMC/HYCOM-src/commits/8c5cc444f5065d5fd8c74582db95c360e0e4a99f"
},
. . .
]
},
"public": true,
"created_at": "2022-09-09T19:58:45Z",
"org": {
"id": 37810995,
"login": "NOAA-EMC",
"gravatar_id": "",
"url": "https://api.github.com/orgs/NOAA-EMC",
"avatar_url": "https://avatars.githubusercontent.com/u/37810995?"
}
},
. . .
] |
Looks like coaps people from fsu |
@jkbk2004 The FSU folks do not have write permission to the emc fork. Only Bin Liu, Rahul, Jun, Dan Rosen and "the bot" have write permission. |
@DeniseWorthen so we need to ask hafs to come with urgent pr to sync up hycom, right? But it sounds like they need to evaluate hycom code changes first. |
@jkbk2004 We do not want to update the hycom hash in our fork. Bin Liu will make a force push back to our emc fork to recover our history. |
The commit hash of 09bdf00 has now been forced pushed and restored in NOAA-EMC HYCOM-src fork. |
just made a fresh clone, this is what I have now for HYCOM:
is it suppose to point to emc/develop ? UFS code location: /scratch1/NCEPDEV/climate/Jiande.Wang/MOM6-update/MOM6-update-20220902/Final/ufs-weather-model/ |
@jiandewang When I do a fresh checkout of UWM, I get the hash for Hycom as 09bdf00. That is our current hash in the develop branch of UWM. The commit message for that hash is "Add :: symbol to read from nems.configure.Required for ESMF 8bs20+. (#1)". |
I checked hycom source codes that we used to test against fresh clone. All looks good. |
yes I got the same thing. What puzzled me is the location of the *
what I mean is the * should located on emc/develop (note here * is showing as dot, but if you do on one of the machine, you will see the *) |
let me know when it's the time to do submodule switch |
|
MOM6 submodule switched |
PR Checklist
This 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.
Results for one or more of the regression tests change and the reasons for the changes are understood and explained below.
the SPPT temperature limiter calculation method is being changed, thus the stochastic test case will require new baseline
New or updated input data is required by this PR. If checked, please work with the code managers to update input data sets on all platforms.
Instructions: All subsequent sections of text should be filled in as appropriate.
The information provided below allows the code managers to understand the changes relevant to this PR, whether those changes are in the ufs-weather-model repository or in a subcomponent repository. Ufs-weather-model code managers will use the information provided to add any applicable labels, assign reviewers and place it in the Commit Queue. Once the PR is in the Commit Queue, it is the PR owner's responsibility to keep the PR up-to-date with the develop branch of ufs-weather-model.
Description
Provide a detailed description of what this PR does. What bug does it fix, or what feature does it add? Is a change of answers expected from this PR? Are any library updates included in this PR (modulefiles etc.)?
update MOM6 to its main branch 20220902 commit, this is originally based on dev-emc-candidate-20220828 to MOM6 main branch but with minor modification on SPPT temperature limiter
Issue(s) addressed
UFS #1400 and MOM6 issue NOAA-EMC/MOM6#103
MOM6 PR NOAA-EMC/MOM6#104
Link the issues to be closed with this PR, whether in this repository, or in another repository.
(Remember, issues must 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 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)
Dependencies