Date
Attendees
- Harris, Edu, Manuel, Seb V., Robert
Discussion items
- Archiving needs: MARS structure for these projects (ASPECT/CERISE) data
- Are new MARS classes enough?
- In principle yes
- But streams might differ depending on the reforecast encoding
- Are new MARS classes enough?
- Encoding
- Reforecast encoding
- 'modelVersionDate' can be used in the same way it's used for S2S systems with "fixed" reforecast datasets
- instead of using "system" (MARS specific) use "generatingProcessIdentifier"
- but a mapping can exist in MARS from those values to something called "system" (?)
- what values use for "generatingProcessIdentifier"?
- for ECMWF data the proposal would be to use the code for the corresponding IFS cycle. NOTE: The appropriateness of this needs to be double-checked with RD/seasonal (Tim, Stephanie)
- for all other providers we could directly put there the value of "system"
- also use "typeOfGeneratingProcess"=15 ("hindcast" according to code table 4.3)
- Reforecast encoding
- Plans for SEAS6:
- During the meeting it was mentioned a Confluence page summarizing the agreements with management on the plans for ECMWF SEAS6 configuration
SEAS6 configuration - final choice
- During the meeting it was mentioned a Confluence page summarizing the agreements with management on the plans for ECMWF SEAS6 configuration
Action items
- (Harris/Edu) Create a set of C3S data in GRIB2 following the encoding described for reforecasts (modelVersionDate, generatingProcessIdentifier,typeOfGeneratingProcess,...)
- (Edu) set up next meeting in ~4 weeks time
From previous meetings
- (SebV) Create some DGOV space (JIRA? Confluence?) to monitor these discussions