vxstats | R Documentation |

Calculates some common traditional forecast verification statistics.

```
vxstats(X, Xhat, which.stats = c("bias", "ts", "ets", "pod",
"far", "f", "hk", "bcts", "bcets", "mse"), subset =
NULL)
```

`X` , `Xhat` |
k by m matrix of verification and forecast values, resp. |

`which.stats` |
character vector giving the names of the desired statistics. See Details below. |

`subset` |
numeric vector indicating a subset of the verification set over which to calculate the verification statistics. |

Computes several traditional verification statistics (see Wilks, 2006, Ch. 7; Jolliffe and Stephenson, 2012 for more on these forecast verification statistics)
The possible statistics that can be computed, as determined by `which.stats`

are:

“bias” the number of forecast events divided by the number of observed events (sometimes called frequency bias).

“ts” threat score, given by hits/(hits + misses + false alarms)

“ets” equitable threat score, given by (hits - hits.random)/(hits + misses + false alarms - hits.random), where hits.random is the number of observed events times the number of forecast events divided by the total number of forecasts.

“pod” probability of detecting an observed event (aka, hit rate). It is given by hits/(hits + misses).

“far” false alarm ratio, given by (false alarms)/(hits + false alarms).

“f” false alarm rate (aka probability of false detection) is given by (false alarms)/(correct rejections + false alarms).

“hk” Hanssen-Kuipers Score is given by the difference between the hit rate (“pod”) and the false alarm rate (“f”).

“bcts”, “bcets”, Bias Corrected Threat Score (Equitable Threat Score) as introduced in Mesinger (2008); see also Brill and Mesinger (2009). Also referred to as the dHdA versions of these scores.

“mse” mean square error (not a contingency table statistic, but can be used with binary fields). This is the only statistic that can be calculated here that does not require binary fields for `Fcst`

and `Obs`

.

A list with components determined by which.stats, which may include any or all of the following.

`bias` |
numeric giving the frequency bias. |

`ts` |
numeric giving the threat score. |

`ets` |
numeric giving the equitable threat score, also known as the Gilbert Skill Score. |

`pod` |
numeric giving the probability of decking an event, also known as the hit rate. |

`far` |
numeric giving the false alarm ratio. |

`f` |
numeric giving the false alarm rate. |

`hk` |
numeric giving the Hanssen and Kuipers statistic. |

`bcts` , `bcets` |
numeric giving the bias corrected version of the threat- and/or equitable threat score. |

`mse` |
numeric giving the mean square error. |

It is up to the user to provide the appropriate type of fields for the given statistics to be computed. For example, they must be binary for all types of which.stats except mse.

See the web page: https://www.cawcr.gov.au/projects/verification/ for more details about these statistics, and references.

Eric Gilleland

Brill, K. F. and Mesinger, F. (2009) Applying a general analytic method for assessing bias sensitivity to bias-adjusted threat and equitable threat scores. *Wea. Forecasting*, **24**, 1748–1754.

Jolliffe, I. T. and Stephenson, D. B., Edts. (2012) *Forecast Verification: A Practitioner's Guide in Atmospheric Science*, 2nd edition. Chichester, West Sussex, U.K.: Wiley, 274 pp.

Mesinger, F. (2008) Bias adjusted precipitation threat scores. *Adv. Geosci.*, **16**, 137–142.

Wilks, D. S. (2006) *Statistical Methods in the Atmospheric Sciences*. 2nd Edition, Academic Press, Burlington, Massachusetts, 627pp.

`hoods2d`

```
# Calculate the traditional verification scores for the first geometric case
# of the ICP.
data( "geom001" )
data( "geom000" )
rmse <- sqrt(vxstats( geom001, geom000, which.stats="mse")$mse)
rmse
vxstats( geom001 > 0, geom000 > 0, which.stats=c("bias", "ts", "ets", "pod", "far", "f", "hk"))
data( "geom005" )
vxstats( geom005 > 0, geom000 >0, which.stats=c("ts","ets","bcts","bcets"))
```

Embedding an R snippet on your website

Add the following code to your website.

For more information on customizing the embed code, read Embedding Snippets.