-
Notifications
You must be signed in to change notification settings - Fork 7
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
Update paths for GFSv17/GEFSv13 COM reorg #1
Comments
WalterKolczynski-NOAA
added a commit
to WalterKolczynski-NOAA/TC_tracker
that referenced
this issue
Apr 10, 2023
The upcoming update to GFS v17 will substantially change the COM paths for the GFS package. When called within global workflow, `$COMINgfs` now contains the full path to the desired directories. This requires changes to how the look-behind and look-ahead are done. Now instead of constructing the path itself, the lookbehind and look-ahead now do a substitution of `${PDY}/${cyc}` with the new desired values for the other cycles. Additional changes will be needed to the j-jobs to match the updated `$COMINgfs` pattern for GFS v17 in order to run this as a seperate system (as in ops). Also, not all GFS tracker jobs are currently available in the global workflow, so changes for FSU genesis have not been tested. Additional changes will also be needed for GEFS v13, which is making similar changes to COM. Refs: NOAA-EMC#1 Refs: NOAA-EMC/global-workflow#761
These updates aren't going to be made all at once, so I've created a new branch, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
GFS is completely reorganizing its COM directory for v17, and GEFS v13 will be making similar changes. These changes require changes to how
$COMINgfs
is defined in the j-jobs and how look-back and look-ahead paths are produced. The$COMINgfs
produced when run as part of global-workflow now contains the full path, including the cycle and component.See also: NOAA-EMC/global-workflow#761, NOAA-EMC/global-workflow#1421
The text was updated successfully, but these errors were encountered: