Due to historical reason analysis date and time values are currently encoded incorrectly in MACC_GFAS file and directory names so dates :
- Date in directory
...
- name does not match
...
- date in file name.
- Step value is encoded incorrectly in current GRIB files.
Here is
...
a file name and content of
...
recent GFAS analysis:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
/DATA/MACC_GFAS/20170913> ls *frpfire.grib -rw-r--r-- 1 anonymou ec 25920120 Sep 13 05:30 z_macc_c_ecmf_20170912120000_gfas_an_sfc_frpfire.grib /DATA/MACC_GFAS/20170913> grib_ls -p date,time,step z_macc_c_ecmf_20170912120000_gfas_an_sfc_frpfire.grib date time step 20170912 1200 0 |
This file contains 00:00 - 23:59 analysis from the 12 Sep.
To make fix the incorrect directory and file names more compliant with ECMWF practices, we've created a new parallel stream called CAMS_GFAS with . The new stream contains exactly the same GFAS data but using uses a more consistent logical file naming and date convention.
The same data from the above example is available in this file in the new stream under new file name:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
/DATA/CAMS_GFAS/20170912> ls *frpfire.grib -rw-r--r-- 1 anonymou ec 25920120 Sep 13 05:29 z_cams_c_ecmf_20170912000000_gfas_an_sfc_frpfire.grib /DATA/CAMS_GFAS/20170912> grib_ls -p date,time,step z_cams_c_ecmf_20170912000000_gfas_an_sfc_frpfire.grib date time step 20170912 0 0-24 |
The data will become available in the new stream at the same time as in the existing MACC_GFAS stream until December 2017 July 2018, when old MACC_GFAS stream will be phased discontinued out.