HelinWei-NOAA
commented
6 months ago Made the changes following the instructions provided by Kate:
Since the GFSv16 still sources the GLDAS scripts from the GLDAS repo, but we removed the scripts last year as part of absorbing scripts into global-workflow develop, we'll need to make a branch in GLDAS from the hash that is in operations now and before the last set of commits. Please do the following: Create a "production" branch off of the hash that is in ops now: https://github.com/NOAA-EMC/GLDAS/tree/fd8ba62275bb27b0beecbc7c6985c1d61537f299) Check out the GLDAS master branch at that hash:
git checkout https://github.com/NOAA-EMC/GLDAS.git ./master cd master git checkout fd8ba62275bb27b0beecbc7c6985c1d61537f299 Create a new branch from that hash with your clone: git checkout -b production/gfs.v16 Push that new branch up to the auth repo: git push origin production/gfs.v16 Now that we've saved the production version...create a new release branch for the requested updates from that new production branch. You can do that via the "New branch" button in GitHub or follow these steps: git checkout -b production/gfs.v16 https://github.com/NOAA-EMC/GLDAS.git ./production-gfs.v16 cd production-gfs.v16 git checkout -b release/gfs.v16.3_gldas git push origin release/gfs.v16.3_gldas Then we can make the requested changes to the release/gfs.v16.3_gldas branch for items #1 and #2
This is part of the global-workflow issue #2503 Kate opened to address the failure of gldas in the ops GFS due to the missing of daily CPC gauge data