...
| Info |
|---|
1. Brief description: The CMA reforecasts after model change in November 2019 were wrongly encoded as the fixed type. Since the run 2020-06-25 the encoding was fixed to the correct on-the-fly type. The period Nov 2019 - Jun 2020 will need to be fixed so that all reforecast data is encoded the same way (on-the-fly type, not fixed one) 2. Recommendation: Users should be aware of that situation, when CMA reforecast encoding is mixed until the fix is completed for the whole period. The affected reforecast data (2019-11-11....2020-06-22) can be re-downloaded if needed to have consistent encoding once the fix is finished. A simple fix can be applied also on user's side on already downloaded affected data. Please contact us for more details if needed. |
...
CNR-ISAC (
...
isac)
...
Numerical artifacts in reforecasts with model version date 20231016
| 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 There are numerical errors affecting only few grid cells here and there in the fixed reforecast set produced with model version dated 20231016. Only pressure level parameters U/V components, geopotential height and temperature are occasionally affected. 2. Recommendation: Users should not use the affected data. |
U and V components on pressure levels and at the 10m (period 11.7.2019-9.1.2020). Fixed during 7-18 May 2020
consider this when using affected parameters. |
ECCC (cwao)
Sea-ice cover values in some re-forecast data (period 20.9.-13.12. 2018).
| Info |
|---|
1. Brief description: See an example of meridional wind at 200 hPa for the ECCC forecast initialized on 7 Nov. 2019 (incorrect contours around 40E and 200E). This interpolation error affects both real-time and reforecast data.
2. Recommendation: If you downloaded the affected data before 18 May 2020, get the fixed data available in the archive now instead. |
ECMWF (ecmf)
issue with accumulated fields at day 16
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. |
U and V components on pressure levels and at the 10m (period 11.7.2019-9.1.2020). Fixed during 7-18 May 2020
| Info |
|---|
1. Brief description: See an example of meridional wind at 200 hPa for the ECCC forecast initialized on 7 Nov. 2019 (incorrect contours around 40E and 200E). This interpolation error affects both real-time and reforecast data.
2. Recommendation: If you downloaded the affected data before 18 May 2020, get the fixed data available in the archive now instead. |
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'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:
|
...
| Info |
|---|
1. Brief description: After the latest CNRM model change in October 2020, the CNRM grid is inverted, i.e. j-dimension scans positively (south to north) instead of negatively (north to south) as per the S2S requirement Encoding#Gridandresolution As the related GRIB 2 scanningMode changed from 0 to 64, such GRIB 2 encoding is correct in principle. Still it is not desirable for reasons of consistency with the previous encoding of CNRM data, and in addition may cause problems for users. https://jira.ecmwf.int/servicedesk/customer/portal/4/SD-92894 2. Recommendation: Users should be aware of this when processing CNRM data from the affected period. |
...
NCEP (
...
kwbc)
Errors in the real-time data (3 runs only on 27.8., 3.9. and 10.9. 2020). Fixed 19th October 2020
| Info |
|---|
1. Brief description: There were some errors in the RHMC real-time outputs for the period 20200827-20200910. 2. Recommendation: If RHMC real-time data from the given runs was downloaded before 19.10. 2020, it should be deleted and the correct version of the data downloaded again. |
NCEP (kwbc)
Missing steps 0 and 0-24
| Info |
|---|
|
Identical control forecast and ensemble members 1, 2 and 3 for some reforecast dates
Missing steps 0 and 0-24
| Info |
|---|
|
Identical control forecast and ensemble members 1, 2 and 3 for some reforecast dates
| Info |
|---|
For some re-forecast dates, only the 0Z runs could be recovered, which means that the control, ensemble members 1, 2 and 3 are identical and correspond to the 0Z run.
|
RHMC (rums)
Errors in the real-time data (3 runs only on 27.8., 3.9. and 10.9. 2020). Fixed 19th October 2020
| Info |
|---|
1. Brief description: There were some errors in the RHMC real-time outputs for the period 20200827-20200910. 2. Recommendation: If RHMC real-time data from the given runs was downloaded before 19.10. 2020, it should be deleted and the correct version of the data downloaded again. |
| Info |
For some re-forecast dates, only the 0Z runs could be recovered, which means that the control, ensemble members 1, 2 and 3 are identical and correspond to the 0Z run. |