Consistent time-stamps in restarts across various ufs-weather-model components. #1577
Closed
Description
Description
The coupled ufs-weather-model produces restarts for its components at a user chosen frequency. The restart filenames have the following formats:
Component | Intermediate restart | Endpoint restart |
---|---|---|
FV3 | YYYYMMDD.HHMMSS.file_type.tile{n}.nc |
file_type.tile{n}.nc |
MOM6 | MOM.res.YYYY-MM-DD-HH-MM-SS.nc |
MOM.res.nc |
CICE6 | iced.YYYY-MM-DD-SECONDS_FROM_00000.nc |
N/A |
WW3 | YYYYMMDD.HHMMSS.restart.${ww3grid} |
N/A |
CMEPS | ufs.cpld.cpl.r.YYYY-MM-DD-SECONDS_FROM_00000.nc |
N/A |
Other components could be added to this table where relevant.
All these files are moved around in their respective application workflows between experiment and run directories.
Having a consistent datetime format makes handling of these files easier and less prone to errors.
This feature requests:
- writing out the restarts across the UFS-weather-model components in a consistent and unified format.
- writing out the restarts at the endpoints in FV3 and MOM6 with a time-stamp.
For more information on the files needed to restart a coupled model, please see this wiki link.
Solution
The restarts would look like the following (assuming the adopted format is from FV3 and WW3):
Component | Intermediate restart | Endpoint restart |
---|---|---|
FV3 | YYYYMMDD.HHMMSS.file_type.tile{n}.nc |
YYYYMMDD.HHMMSS.file_type.tile{n}.nc |
MOM6 | YYYYMMDD.HHMMSS.MOM.res.nc |
YYYYMMDD.HHMMSS.MOM.res.nc |
CICE6 | YYYYMMDD.HHMMSS.cice_model.res.nc |
YYYYMMDD.HHMMSS.cice_model.res.nc |
WW3 | YYYYMMDD.HHMMSS.restart.${ww3grid} |
YYYYMMDD.HHMMSS.restart.${ww3grid} |
CMEPS | YYYYMMDD.HHMMSS.ufs.cpld.cpl.r.nc |
YYYYMMDD.HHMMSS.ufs.cpld.cpl.r.nc |