-
Notifications
You must be signed in to change notification settings - Fork 154
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
Modify hpc stack to point to hpc-stack-gfsv16 since hpc-stack is outd… #562
Modify hpc stack to point to hpc-stack-gfsv16 since hpc-stack is outd… #562
Conversation
@emilyhcliu - please note that EPIC-maintained stacks are now available, as in |
@natalie-perlin Thanks for letting me about the EPIC hpc-stack update. |
@RussTreadon-NOAA I think I should close this PR since we can use the EPIC-maintenance stacks in develop (PR #571). |
@emilyhcliu : This PR (#562) merges into |
The CRTM-2.4.0_emc installed in @HaixiaLiu-NOAA and I worked with EIB to make sure the version with the bug fix was installed on HERA last summer. We checked the source code and knew the bug-fixed version was installed. Lately, we had some parallel experiments that were having trouble. So I went to check the CRTM source installed on HERA again. The source code did not contain the bug fix. Some changes must be made for I found there were two versions of hpc stacks ( So, I went to check CRTM-v2.4.0_emc installed in Anyway, the whole process has been very frustrating for me. |
Thank you @emilyhcliu for confirming that we need to keep this PR to update Two questions:
|
I checked ORION before. It is not the CRTM with bug-fix. I will run the regression test for release/gfsda.v16 with the change from |
@RussTreadon-NOAA Just to clarify, the regression tests you mentioned above are the standard regression tests (total 19 tests) in the release/gfsda.v16, correct? |
Ooops, this a problem. This will be a problem moving forward. I don't think GFS v16.x implementations can move to Please try old ctests bundled with |
@RussTreadon-NOAA Thanks for your quick response. My control is release/gfsda.v16 All 19 tests ran to completion except The error message from the control runs is the following:
As you expected, many tests failed.
I did not find the summary output for each run. (I remembered there should be a summary output for each test documenting the reproducibility, timing, scalability, ...etc). |
@RussTreadon-NOAA |
PR #1 has been opened in your fork. This PR replaces the old regression tests in Only the global ctests work since
The I'd like to hear from you, Andrew, and others working on GFS v16 implementations if we want to update |
@RussTreadon-NOAA I agree with you. We should add the updated regression tests for release/gfsda.v16 |
Thank you @emilyhcliu for your reply. I am currently running the updated ctests on Orion. The Hera and Cactus tests are done. Global ctest results will be posted in PR #1 once the Orion tests finish. After this I'll change PR #1 to active status. |
@RussTreadon-NOAA Thanks for working on updating the regression for release/gfsda.v16. |
@emilyhcliu , we have two hera modulefiles: |
@RussTreadon-NOAA Let's just address the HPC stack change ( |
update regression tests
It is my understanding that
GFS v16 implementations occur on WCOSS2. Pre-implementation testing may occur on Orion or Hera. I assume Hera testing will use intel builds since WCOSS2 uses intel builds. If true, What's your take? |
@RussTreadon-NOAA I am totally OK with it! |
Pending two peer reviews I believe we can move forward with the PR. |
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.
Thanks for getting this all sorted out @emilyhcliu. And thank you Russ for updating the regression tests. Looks good to me.
Thank you @CatherineThomas-NOAA for your review. When you have time, would you please click approve so we record two peer reviews for this PR. @emilyhcliu, I'll contact the Handling Review team to schedule merger of this PR into release/gfsda.v16 on Tuesday, 5/16. |
My bad @CatherineThomas-NOAA . I see that you already approved this PR. @emilyhcliu , I hope to merge this PR before lunch tomorrow. |
Given feedback from GSI Handling Review team move forward with merging this PR into |
Description
Based on the discussion in the GW issue #1453 and GSI issue #560
Fixes #560
We need to do the following:
develop
uses EPIC-maintain hpc-stacks and, later, spack-stackrelease/gfsda.v16
uses hpc-stack-gfsv16On HERA, updating the hpc stack to hpc-stack-gfsv16 is ready. So, This PR is focused on updating the HERA modulefiles for gfsda.v16. The updated changes can be found in gfsda.v16_crtm under emilyhcliu fork.
Here are the changes
How Has This Been Tested?
Checklist
DUE DATE for this PR is 6/2/2023. If this PR is not merged into
develop
by this date, the PR will be closed and returned to the developer.