location

Home>Data & Plot>System Configuration Information>Moscow

System Configuration Information

These information can be changed if the corresponding operational model is modified.

GPC Moscow

GPC Moscow
When was the current long-range forecast system implemented? April 2012
Is it a coupled forecast system? No
Is it a Tier-2 forecast system? Yes
Atmospheric model resolution Semi-Lagrangian, 1.125° lat × 1.40625°lon/L28
Ocean model (if applicable) N/A
Source of atmospheric initial conditions NCEP Reanalysis 2 (hindcast) / HMC data assimilation system (forecast)
Source of ocean initial conditions Reynolds-Smith OI
If Tier-2, what is the source of SST predictions? Persisting SST anomaly atop annual cycle
Hindcast Period 1981-2010
Ensemble size for the hindcasts 10
How is the hindcast ensemble configured 2 per day (5 last days of the month prior to current, 12 hr. steps. For example, hindcast for JJA: from 00 hr. 26th Apr. to 12 hr. 30th Apr with 12 hour step)
Ensemble size for the forecast 20
How is the forecast ensemble configured? Original and perturbed (breeding of fast growing modes) analysis fields from the date 2 days prior to current month (For example, for JJA it is 12 hr. 28th April)
Length of forecasts 4 months (seasonal/three month forecast with one month lead time)
Data format GRIB 1
What is the latest date predicted anomalies for the next month/season become available 30th of the month prior to current. For example, forecast for JJA is available on 30th April
How are the forecast anomalies constructed? Forecast minus model 30 yr. climatology from hindcasts
URL where forecast are displayed http://wmc.meteoinfo.ru
Point of Contact

Vladimir Kryjov (kryjov@yahoo.co.uk)