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
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)
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
Action items
Charalampos Karvelis / Eduardo Penabad Create a set of C3S data in GRIB2 following the encoding described for reforecasts (modelVersionDate, generatingProcessIdentifier,typeOfGeneratingProcess,...)
Eduardo Penabad set up next meeting in ~4 weeks time (slot booked for 13th July)
From previous meetings
Sebastien Villaume Create some DGOV space (JIRA? Confluence?) to monitor these discussions