-
Notifications
You must be signed in to change notification settings - Fork 503
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
Port WW3 to expanse #485
Port WW3 to expanse #485
Conversation
@MinsukJi-NOAA - my tests on orion with the S2SW ufs regtests all passed with the develop branch + your changes, so if the PR to your commit here updating to the top of develop works on expanse I think you would be fine to include this in your ufs-weather-model PR. Let me know how you want to proceed - I can run more tests with the updated WW3 or something else depending on what you prefer. |
Please merge the upstream noaa/develop and resolve the conflicts |
@MinsukJi-NOAA the PR to WW3 yesterday (#483) means the WW3 baselines change. (It's a superficial reason for a version string change in the binary file, not actual answer changes). However, I know this complicates your updating of WW3. @aliabdolali what's the best path forward for this? We will need a PR to ufs-weather-model with the other update and/or we need that branch for the ufs-weather-model. |
@JessicaMeixner-NOAA @aliabdolali @junwang-noaa I think bringing the top of develop of WW3 into the ufs-weather-model should be a separate PR, and the Expanse changes come in a later PR. |
@MinsukJi-NOAA okay. Sounds good. In the meantime, have you had a chance to test the PR I made to your branch bringing this branch up to date with the WW3 develop? Or do I need to create a new branch/PR with those? To get this into WW3 we need to resolve the conflicts. We have a pretty big WW3 commit coming up so we either need to get this PR in now or it might have to wait until after the switch -> CPP PR. I'm okay with either I just want to be prepared with your timeline. @aliabdolali will you be making a PR to ufs-weather-model with the updated WW3 or should I do that? |
@JessicaMeixner-NOAA once the conflicts are solved, I can merge this to WW3 (we can merge this today, the tests are about to finish). Then I will create the PR to ufs-weather-model. |
@JessicaMeixner-NOAA @aliabdolali I have not had a chance to test it on Expanse.
Will try to get this PR ready by the end of today so that it does not delay the WW3 commit coming up. |
The tests ran successfully with pre-known different cases. ********************* non-identical cases **************************** mww3_test_03/./work_PR2_UQ_MPI_d2 (6 files differ) |
I am getting MPI aborts when running
|
@MinsukJi-NOAA I believe this is because we need new mod_def files for WW3. Can you copy from hera the newest WW3 Inputs files (/scratch1/NCEPDEV/nems/emc.nemspara/RT/NEMSfv3gfs/input-data-20210930/WW3_input_data_20210908) Do you need to run this exact version of ufs-weather-model/WW3 or is putting the updates in the develop of both okay? Because the new mod_defs would be for the develop branch. |
XSEDE collaborators are running 7c experiments (UFS hash |
@MinsukJi-NOAA sounds good. To include this into WW3 we need to merge the develop branch into your branch to resolve the conflicts. Another strategy could be that we close this PR and open a PR from the branch that I created that has the develop merged in so that the changes get put in but your branch stays as is. Let me know which you prefer. |
@JessicaMeixner-NOAA thank you. Can we do the second strategy and close this PR? For the conflics in:
|
Sounds good -- I'll close this after I open a new PR. |
Closing this PR. Please see it's replacement: #490 |
Pull Request Summary
Port WW3 to expanse
Description
Ports WW3 to the HPC expanse
Issue(s) addressed
Related to UFS PR: ufs-community/ufs-weather-model#850
Check list
Is your feature branch up to date with the authoritative repository (NOAA/develop)?
Make sure you have checked the checklist for a developer submitting to develop and updating version number
Please list appropriate labels code managers should add for this PR:
bug, documentation, enhancement, new feature, ..
Reviewers: @MinsukJi-NOAA
Commit Message
Testing