-
Notifications
You must be signed in to change notification settings - Fork 177
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
Issue building pre/post wave jobs with latest ufs-weather-model #3110
Comments
g-w is not using a UFS hash with this issue and the issue looks to be contained within UFS. Is there a reason we need a g-w issue for this (e.g. some change to the build script will be needed)? |
It's common for people to update the ufs-weather-model on their own - for example: #3106 therefore, communicating that this will be an issue seems like a good idea for everyone's awareness. Do you have a better method of communicating that this will be an issue? |
PR to ufs-weather-model to address this issue is here: ufs-community/ufs-weather-model#2512 Branch of g-w used to test is here: https://github.com/JessicaMeixner-NOAA/global-workflow/tree/bug/addPIOswitch |
This PR updates ufs-weather-model hash to the latest commit which addresses an issue seen in an earlier commit (see: NOAA-EMC#3110) Note this includes the PR that enables PIO for WW3, however additional work is required to use this feature. Another notable PR update is for a PIO finalize bug in CICE which also required updates to ice_in Resolves NOAA-EMC#3110
What is wrong?
FYI - There is an issue (seen here: #3106 (comment)) when building the wave model if you update to the latest ufs-weather-model. Fix for this is being tracked here: ufs-community/ufs-weather-model#2502
Just posting here so others know about this problem.
What should have happened?
WW3 pre/post jobs should build.
What machines are impacted?
All or N/A
What global-workflow hash are you using?
adding newest ufs-weather-model
Steps to reproduce
Update ufs-weather-model to latest PR and try to build ww3 pre/post.
Additional information
No response
Do you have a proposed solution?
No response
The text was updated successfully, but these errors were encountered: