You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

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:

  1. A change that  does not affect the number of fields ingested in the database, for example, a change in resolution or an improved version of the model.
  2. A change in the configuration that affects the number of fields. This could be in the form of:
    1. change to the frequency of time-steps or extend/shorten the length of the forecast
    2. addition/removal of parameters
    3. change to the number of ensembles
    4. change to the frequency of the forecast (eg, from once a week to twice a week), etc...

In both cases, data providers must document what has changed, so users are able to follow the history of a model (see as an example the changes in ECMWF Model).

Changes to the configuration

When the change affects the number of fields, we ask data providers to:

  • Notify in advance ECMWF and CMA,
  • Provide test data, and
  • Update the Models summary page.

Notify in advance ECMWF and CMA

Send an e-mail to s2s.support@lists.ecmwf.int. describing the change.

Provide test data

ECMWF and CMA would like to have access to test data in advance, so the ingestion suites can be adapted.

This is achieved by naming files as test instead of prod, and by setting in the GRIB header Production status of data to 7:

table 1.3 Production status of data

6: S2S operational products
7: S2S test products

Once you have a full cycle of test data (whether real-time and/or reforecast) we ask you to contact s2s.support@lists.ecmwf.int.

Update the documentation

This is usually in two places:

  • Models summary, which contains an overview of the latest configuration
  • A page describing in detail each model (for example, changes in ECMWF Model), where one would keep details of previous configurations, in particular the date of the change.

 

  • No labels