Closed sebvi closed 10 months ago
https://github.com/wmo-im/CCT/wiki/Teleconference.6.7.June.2023
@sebvi add samples and update branch;
branch updated
@sebvi
Template 4.118 references note 99 in octetNo 64-67, but the note references different octets. Can we remove those references from the note?
note 99,"The reference and forecast times are successively set to their initial values plus or minus the increment, as defined by the type of time increment (one of octets 51, 63, 75, ...). For all but the innermost (last) time range, the next inner range is then processed using these reference and forecast times as the initial reference and forecast times."
I think we can remove the mention to octets from the note so that the note is more generic.
https://github.com/wmo-im/CCT/wiki/Teleconference.13.July.2023 notes:
@sebvi add samples @SibylleK validate
@sebvi
Template 4.118 references note 99 in octetNo 64-67, but the note references different octets. Can we remove those references from the note?
note 99,"The reference and forecast times are successively set to their initial values plus or minus the increment, as defined by the type of time increment (one of octets 51, 63, 75, ...). For all but the innermost (last) time range, the next inner range is then processed using these reference and forecast times as the initial reference and forecast times."
it looks like notes 95 to 110 are all identical except for the list of octets they reference....How do we proceed then? we should either continue with this practice or use a generic note for all these cases
a version of ecCodes able to encode/decode templates 4.117 and 4.118 can be found here:eccodes
I am also uploading samples for these 2 templates: large_eps.zip
I was able to read the entries in section 4 of the GRIB examples with a DWD GRIB reader software. The entries were the same as in an output of eccodes grib_dump, in particular 123456 for the perturbation number and 1234567 for number of forecasts in ensemble in both examples.
This should be sufficient for the validation of this proposal. From my point of view, the validation is done.
@amilan17 update notes in FT branch
Initial request
In the context of the emerging machine learning based forecasting, it is not unusual to run probabilistic forecasting system of thousands or tens of thousands ensemble members due to the relative cheap computation costs of each member.
As of today, the maximum ensemble size in GRIB2 in Templates 4.1 and 4.11 is 255 because both the ensemble number and total ensemble size are encoded on 1 octet each only. We are proposing to create 2 new templates to increase significantly this limit by encoding both on 4 octets each instead. The 2 following templates replicate templates 4.1 and 4.11 allocating more octets for the ensemble number and the ensemble size
Amendment details
Comments
No response
Requestor(s)
Sebastien Villaume (ECMWF)
Stakeholder(s)
ECMWF
Publication(s)
Manual on Codes (WMO-No. 306), Volume I.2, GRIB, section 4 template 4.117 (new) Manual on Codes (WMO-No. 306), Volume I.2, GRIB, section 4 template 4.118 (new)
Expected impact of change
MEDIUM
Collaborators
No response
References
No response
Validation
No response