Versions Compared

Key

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

...

centre=centre, model=model_id, d=yyyymm, t=time, s=forecast_step, st=station_id, lat=latitude, lon=longitude, lam= model_grid_latitude , lom= model_grid_longitude , se=station_elevation, me=model_orography_elevation, par=parameter, sc=score, evth=event_thresholds, n=sample_size, v=mean_value

...

Code Block
centre=ecmf,model=0001_fc,d=201410,t=0,s=24,st=11520,lat=50.02,lon=14.38,se=302,me=248,par=tp24,sc=me,ev=na,n=31,v=0.95
s=48,v=1.15
s=24,sc=ct,evth=val>55,v=1,16,12,2
s=48,v=3,/13,/11,/4

Values of keys

  • centre (4-characters string) is the WMO identifier of the originating centre (ammc, cwao, ecmf, edzw, egrr, kwbc, lfpw, rjtd, rksl, rums etc);
  • model_id (a string, not containing a comma or vertical bar) is free model identifier assigned by the originating centre (to distinguish between potentially different models provided by the centre);

  • yyyymm is the month of the mean, where yyyy is the year and mm is the month (01-12);
  • time is the validity time (in hours UTC) of the forecasts verified;
  • forecast_step is the length of the forecast (in hours);
  • station_id (a number) is the WMO ID of the observation station verifying the forecasts;
  • latitude is the latitude of the observation station verifying the forecasts;
  • longitude is the longitude of the observation station verifying the forecasts;
  • model_grid_latitude (non-mandatory) is the latitude of the model grid point used to extract the forecast at the observation location;
  • model_grid_longitude (non-mandatory) is the longitude of the model grid point used to extract the forecast at the observation location;
  • station_elevation is the elevation of the observation station above the mean sea level in meters;
  • model_orography_elevation is the elevation of the model orography at the observation location;
  • parameter is the verified model output parameter:

...

  • score is the name of the verification score or statistic:
the 4 values are C, A, D, B (in this order!)
scoredescription 
me

mean error (bias)

 
maemean absolute error 
rmseroot mean square error 
ct

contingency table values,

 observednot observed
forecastA (hits)B (false alarms)
not forecastC (misses)D (correct non-events)

 

  • event is the name of the event (for contingency tables)


scanned from bottom up, then left to right

The rank of a contingency table is defined by number of values in the key event_thresholds
(rank_of_ct = len(event_thresholds)+1)

 

NB. Please note how those contingency tables are constructed.
For an event like "10m wind speed >15m/s" a corresponding contingency
table would traditionally be

 obsnon-obs
fcHF
non-fcMR

but following the definition of 2x2 contingency table on the left the table should be

 ob<1515≤ob
fc<15RM
15≤fcFH
2x2ob<th1th1≤ob
fc<th1AB
th1≤fcCD

v=C/A/D/B

3x3ob<th1th1≤ob<th2th2≤ob
ob<th1ABC
th1≤ob<th2DEF
th2≤obGHI

v=G/D/A/H/E/B/I/F/C

4x4ob<th1th1≤ob<th2th2≤ob<th3th3≤ob
ob<th1ABCD
th1≤ob<th2EFGH
th2≤ob<th3IJKL
th3≤obMNOP

v=M/I/E/A/N/J/F/B/O/K/G/C/P/L/H/D

 

  • event_thresholds is a value or values of threshold(s) defining events for contingency tables; number of values in event_thresholds defines the rank of the contingency table; multiple values are separated by a forward slash /
event_thresholddescription
15threshold for a 2x2 contingency table, e.g. if par=ff10m this is an event of 10m wind speed
5/10/15thresholds for a 4x4 contingency table for 10m wind speed
eventdescription
val>thrforecast/observed value greater than a threshold value of the forecast parameter, e.g. for wind speed >15 m/s: val>15
val<=thrforecast/observed value smaller than or equal to a threshold value of the forecast parameter, e.g. for cloudiness of 0-2 okta: val<=2

 

  • sample_size is number of observations used to compute the monthly mean at the given station;
  • mean_value is the value or values of the score mean computed based on the forecast initiating at time time UTC, verifying in the month yyyymm, for the forecast length forecast_step hours; in case of nxn contingency table these are the 4 n2 values delimited by commas forward slashes (see the score table above)

...