COM changes for GFSv17 COM reorganization #17
Comments
|
All bufr dumps (*.bufr_d) and various flavors of prepbufr files are written in the same directory, so this should be a coordinated GFSv17 - obsproc/prepobs/bufr-dump update. @WalterKolczynski-NOAA, when you say COM do you mean $COMROOT/gfs/{gfs_ver}/... ? Just to be clear. We can change the path from: |
|
@ilianagenkova This is more about the location of the GFS files moving than anything about the location of obs. For development purposes, we also link in obs from the dump archive and that is also changing, but that shouldn't matter for prepobs/obsproc. I believe the only change will be to |
|
@WalterKolczynski-NOAA, I got it...it's you impacting us, thanks! Not long ago there was a separate convo about merging /atmos and /wave observations to just /obs , so I jumped to conclusions. Yes, let us know where the guess fields end up so we update getges. Thank you! |
The upcoming update to GFS v17 will substantially change the COM paths
for the GFS package. This requires updates to the lookback capability of
getges_driver where it checks previous cycles. Rather than add additional
logical branches to handle new COM patterns, the process is generalized by
instead doing a string substitution to replace the current day and cycle
with those for the prior cycle. This method is backwards compatible and
should work for any path as long as it contains `${PDY}/${cyc}`.
Additional changes will likely be needed for GFSv17 to run prepobs stand-
alone (as in ops) to match the new `$COMINgdas` and `$COMINgfs`, but
these changes work when running prepobs as part of global workflow in
development.
Also, I have not otherwise modified the existing style of the scripts,
redefining `$COMINgdas` and `$COMINgfs`. However, this will need to be
changed before GFSv17 to stop overwriting these variables to meet NCO
requirements (see NOAA-EMC/global-workflow#293).
Refs: NOAA-EMC#17
Refs: NOAA-EMC/global-workflow#761
|
Completed via PR #19. Closing as complete. |
As part of the GFSv17 upgrade the structure of COM is changing. Companion changes are needed in prepobs. See more in the global-workflow issue: NOAA-EMC/global-workflow#761
@ilianagenkova When a prepobs release branch is created for the GFSv17 implementation these changes should be included. Will hold in a feature branch (feature/GFSv17_com_reorg) until that point for use by GFS developers running cycled experiments. Will keep the feature branch synced with operational updates as needed until release branch for v17 is created.
Changes provided by @WalterKolczynski-NOAA from his COM reorg testing.
The text was updated successfully, but these errors were encountered: