Versions Compared

Old Version 5

changes.mady.by.user Manuel Fuentes

Saved on

compared with

New Version 6

changes.mady.by.user Manuel Fuentes

Saved on

Key

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

This page aims at documenting the steps to follow when a data provider plans to implement changes to their system, such as a new version of their model.

There can be two types of upgrades when introducing a new version of a modelchanges:

Info
iconfalse
  1. A change that 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 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...

...

  • notify in advance ECMWF and CMA about their change,
  • provide test data, and
  • update the Models summary page.

Provision of 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 hindcastreforecast) we ask you to contact s2s.support@lists.ecmwf.int.