Versions Compared

Old Version 8

changes.mady.by.user Manuel Fuentes

Saved on

compared with

New Version 9

changes.mady.by.user Manuel Fuentes

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
iconfalse
  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 the new version of the 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

In the second case above, where there is a change of configurationWhen 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.

...

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.