Versions Compared

Key

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

...

Info

1. Brief  description:

Wrong soil initial data has been used in the real-time forecasts. Please refer to the below graphs and maps illustrating the issue (see soil initial fields and comparison of forecast anomalies).

soil initial data.pngcomparison of forecast anomaly(realtime - reforecast).png

2. Recommendation:

If KMA real-time data from the given runs was downloaded in the period 9-25.6.2019, it should be deleted and the correct version of the data downloaded again.

...

Info

1. Brief  description:

The sea-ice values from two hindcast years 2016 and 2017 are not correct in all Thursday's ECCC hindcasts outputs in the period 20.9.-13.12. 2018. Other hindcast years were not affected.

2. Recommendation:

Users should not use the affected data.

ECMWF (ecmf)

issue with accumulated fields at day 16
Info

1. Brief  description:

There is an issue in the "accumulated" fields at day 16 which occurs when the IFS model resolution changes. This creates a discontinuity in the data (it can be seen also in the data on the native model grid so it's not specifically a result of the regridding to the 1.5 degree S2S resolution) which manifests itself when one "deaccumulates" the data to create six hourly accumulations for example. Specifically, one will see discontinuities between the (T+360 - T+354) and (T+366 - T+360) accumulations (most people note large negative total precipitation values but it also affects the radiation parameters).

2. Recommendation:

Users should consider that issue when using the accumulated fields.

Regrettably, there is not much it can be do about this for the S2S data which has already been regridded from the native model grid to a 1.5 degree.  It would need the deaccumulation to be performed using two different values at T+360, one based on the higher resolution grid which is  used to compute  (T+360 - T+354) and one on the lower resolution grid which is used to compute  (T+366 - T+360).

Read more about the issue:

Hindcast data need to be re-computed with the new cycle after the system  change (4 runs only on 13., 17., 20. and 24.6. 2019). Fixed 25th June 2019

...