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
Currently, all HAFS related changes/developments for UPP have been merged back to UPP develop after this PR (NOAA-EMC/UPP/pull/418). So HAFS can switch to point UPP develop branch directly.
Proposed solution
When we plan our next round of update of the hafs_post.fd submodule inside HAFS, we can just directly point to the UPP develop branch. Beside, UPP is also becoming a submodule of ufs-weather-model/FV3/upp (see NOAA-EMC/fv3atm/pull/421), so we can also consider to just symbolically link upp from sorc/hafs_forecast.fd/FV3/upp into sorc/hafs_post.fd.
Related to (optional)
addressed by hafs-community/hafs/pull/<pr_number>
The text was updated successfully, but these errors were encountered:
Description
Currently, all HAFS related changes/developments for UPP have been merged back to UPP develop after this PR (NOAA-EMC/UPP/pull/418). So HAFS can switch to point UPP develop branch directly.
Proposed solution
When we plan our next round of update of the hafs_post.fd submodule inside HAFS, we can just directly point to the UPP develop branch. Beside, UPP is also becoming a submodule of ufs-weather-model/FV3/upp (see NOAA-EMC/fv3atm/pull/421), so we can also consider to just symbolically link upp from sorc/hafs_forecast.fd/FV3/upp into sorc/hafs_post.fd.
Related to (optional)
The text was updated successfully, but these errors were encountered: