Conversation
Its main purpose is to be able to work with COSMO-1E, COSMO-2E, ICON-CH1-EPS, ICON-CH2-EPS, and KENDA-I1 data: - define stream by typeOfGeneratingProcess and backgroundProcess - define model by generatingProcessIdentifier (and additional keys for the COSMO/KENDA-1 case, since KENDA-1 uses the same generatingProcessIdentifier as COSMO-1E) - define type by productDefinitionTemplateNumber (and further, template-dependent keys, if necessary)
…ocessIdentifier for KENDA-CH1
|
just some remarks on using this branch for the GRIB_DEFINITION_PATH for archiving the single COSMO run to FDB: using this schema:
|
|
Thanks @victoria-cherkas |
|
Also can you give more details concerning 1. ? On which data number and level are not defined ? |
|
For example printing the mars keys with -m we see there is no number, or level :
but those MARS keys share their names with GRIB keys perhaps which is why you see them with |
|
The stream is only 'unknown' for some records in |
|
At least I had checked the model with the COSMO-1E data in /project/s83c/rz+/mars and the script, before I pushed the branch, because my goal was to make it work at least for the COSMO forecasts. KENDA is another subject. |
|
I see, I was just trying to ingest everything in /opr/vcherkas/COSMO-1E/23020103_409. |
|
Ah, then it is clear, why there are records with unknown stream - the directories there als contain the initial condition, which contains data that is produced by the LETKF, and the First Guess. I have not yet added any rule for the First Guess to the scheme. Maybe we can just omit the laf-files, and use only forecast data for this PoC. The KENDA case can be tested separately. |
|
So maybe the missing level types also occurred in the KENDA data. |
|
Sounds good to me, I will omit the laf files, and retry |
|
Ok so apologies for all the confusion - now I have sorted my environment, there are no unknowns! The only issue I see is that no mars keys are defined for |
|
At least number should be a valid MARS key, see for example this sample request for the perturbed forecasts of ECMWF ENS: I, however, set the self-defined type=cpf', but use stream='enfo', which is also defined by ECMWF. Maybe there is some logic requiring the usage of type='pf' to get the number? |
|
It looks as if MARS uses the key 'levelist' instead of 'level'. |
|
And actually, the key'level' is not on this list: https://confluence.ecmwf.int/display/UDOC/Keywords+in+MARS+and+Dissemination+requests |
|
Exactly levelist rather than level. It seems that number is defined for only some productionStatusOfProcessedData (eccodes/definitions/grib2/template.4.eps.def). productionStatusOfProcessedData=2 in the data I ingested, I believe. |
|
The keyword quantile, however, exists, although it is not in the list, e.g. this request for ENS extended range data: |
FDB expects at retrieval time that expver comes in a canonical way (4 chars) instead of 1 integer. However at write time, it does not imposes checks nor transform, it will take grib encoding directly. This generates inconsistency between read and write.
set number
expver as string
|
@cosunae out of curiosity, how did you arrive at the various levels in the marsLevelConcept file? Did you find these defined somewhere else already? |
Fix duplicate class definition
…#8) * Define mars.step by stepRange for stream enfo, type ememb * Add mars aliases for stream enfo, types emean, and estdv * Remove centre-specific definitions from local.78.def
add echoTopInDBZ in grib2/marsLevtypeConcept.def
No description provided.