This page documents the steps to follow when a data provider plans to implement changes to their system, such as a new version of their model or a change in the configuration.
There can be two types of changes:
In both cases, data providers must update the documentation with what has changed, so users are able to follow the history of a model
Changes to the configuration
When a change affects the number of fields, we ask data providers to:
- Notify in advance ECMWF and CMA,
- Provide test data (if required)
- Update the documentation.
Notify in advance ECMWF and CMA
- ECMWF
- describe the change via ECMWF Service Desk form: https://www.ecmwf.int/en/about/contact-us
- Subject:: select last option "Other"
- Message: "system change for TIGGE archive" + description of the change
- it will result in creation of a Service Desk ticket which should be used in the following for all further communication (test data, docs update etc..)
- describe the change via ECMWF Service Desk form: https://www.ecmwf.int/en/about/contact-us
- CMA: TBD
Provide test data (if required)
If the change affects how fields are encoded, it is recommended to test the new encoding by ingesting test data in the TIGGE database, so ECMWF and CMA could adapt the ingestion suites if required.
This is achieved by naming files as test instead of prod, and by setting in the GRIB header Production status of data to 5:
Once you have a full cycle of test data, contact TIGGE support team for checking it.
Update the documentation
Models are documented in two places:
- Models summary, which contains an overview of the latest configurations
- Detailed description of each model (for example changes in ECMWF Model) where one would keep details of previous configurations, in particular the date of the change.