You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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: