metrV | R Documentation |
Calculate the metric metrV proposed in Zhu et al (2011), which is a linear combination of the square root of the sum of squared error between two binary fields, and the mean error distance (Peli and Malah, 1982); or the difference in mean error distances between two forecast fields and the verification field, if the comparison is performed between two forecast models against the same verification field.
metrV(x, ...)
## Default S3 method:
metrV(x, xhat, xhat2 = NULL, thresholds, lam1 = 0.5, lam2 = 0.5,
distfun = "distmapfun", a = NULL, verbose = FALSE, ...)
## S3 method for class 'SpatialVx'
metrV(x, time.point = 1, obs = 1, model = 1, lam1 = 0.5, lam2 = 0.5,
distfun = "distmapfun", verbose = FALSE, ...)
## S3 method for class 'metrV'
print(x, ...)
x |
Either a list object as returned by |
xhat , xhat2 |
(xhat2 is optional) matrix representing a forecast grid. |
thresholds |
q X 2 or q X 3 (if |
lam1 |
numeric giving the weight to be applied to the square root of the sum of squared errors of binary fields term in metrV. |
lam2 |
numeric giving the weight to be applied to the mean error distance term in metrV. |
distfun |
character naming a function with which to calculate the shortest distances between each point x in the grid and the set of events. Default is the Euclidean distance metric (see the help file for |
a |
list object giving certain information about the verification set. These are the attributes of the “SpatailVx” object. May be used here to include information (as attributes of the returned object) that would otherwise not be available to the |
time.point |
numeric or character indicating which time point from the “SpatialVx” verification set to select for analysis. |
obs , model |
numeric indicating which observation/forecast model to select for the analysis. May have length one or two. If it has length two, the second value is taken to be the second forecast model (i.e., |
verbose |
logical, should progress information be printed ot the screen. |
... |
Optional arguments to the |
The binary location metric proposed in Zhu et al. (2011) is a linear combination of two measures: the amount of overlap between events in two fields, given by distOV
(simply the square root of sum of squared errors between two binary fields), and (if there are events in both fields) the mean error distance described in Peli and Malah (1982); see also Baddeley (1992). The metric can be computed between a forecast field, M1, and the verificaiton field, V, or it can be compared between two foreast models M1 and M2 with reference to V. That is,
metrV(M1,M2) = lam1*distOV(I.M1,I.M2) + lam2*distDV(I.M1,I.M2),
where I.M1 (I.M2) is the binary field determined by M1 >= threshold (M2 >= threshold), distOV(I.M1,I.M2) = sqrt( sum( (I.M1 - I.M2)^2)), distDV(I.M1,I.M2) = abs(distob(I.V,I.M1) - distob(I.V,I.M2)), where distob(A,B) is the mean error distance between A and B, given by:
e(A,B) = 1/(N(A))*sqrt( sum( d(x,B)), where the summation is over all the points x corresponding to events in A, and d(x,B) is the minimum of the shortest distance from the point x to each point in B. e(A,B) is calculated by using the distance transform as calculated by the distmap
function from package spatstat
for computational efficiency.
Note that if there are no events in both fields, then by definition, the term distob(A,B) = 0, and if there are no events in one and only one of the two fields, then a large constant (here, the maximum dimension of the field), is returned. In this way, distob differs from the mean error distance described in Peli and Malah (1982).
If comparing between the verification field and one forecast model, then the distDV term simplifies to just distob(I.V,I.M1).
One final note is that Eq (6) that defines distOV
in Zhu et al. (2011) is correct (or rather, what is used in the paper). It is not, as is stated below Eq (6) in Zhu et al. (2011) the root *mean* square error, but rather the root square error. This function computes Eq (6) as written.
list object of class “metrV” with components:
OvsM1 |
k by 3 matrix whose rows represent thresholds and columns give the component distOV, distob and metrV between the verification field and the forecast model 1. |
OvsM2 |
If object2 supplied, k by 3 matrix whose rows represent thresholds and columns give the component distOV, distob and metrV between the verification field and the forecast model 2. |
M1vsM2 |
If object2 supplied, k by 3 matrix whose rows represent thresholds and columns give the component distOV, distob and metrV between model 1 and model 2. |
May also contain attributes as passed by either the a argument or the “SpatialVx” object.
Eric Gilleland
Baddeley, A. J. (1992) An error metric for binary images. In Robust Computer Vision Algorithms, W. Forstner and S. Ruwiedel, Eds., Wichmann, 59–78.
Peli, T. and Malah, D. (1982) A study on edge detection algorithms. Computer Graphics and Image Processing, 20, 1–21.
Zhu, M., Lakshmanan, V. Zhang, P. Hong, Y. Cheng, K. and Chen, S. (2011) Spatial verification using a true metric. Atmos. Res., 102, 408–419, doi:10.1016/j.atmosres.2011.09.004.
distob
, distmap
, im
, solutionset
, deltametric
, locmeasures2d
, make.SpatialVx
A <- B <- B2 <- matrix( 0, 10, 12)
A[2,3] <- 3
B[4,7] <- 400
B2[10,12] <- 17
hold <- make.SpatialVx( A, list(B, B2), thresholds = c(0.1, 3.1, 500),
field.type = "contrived", units = "none",
data.name = "Example", obs.name = "A",
model.name = c("B", "B2") )
metrV(hold)
metrV(hold, model = c(1,2) )
## Not run:
data( "geom000" )
data( "geom001" )
testobj <- make.SpatialVx( geom000, geom001, thresholds = 0,
projection = TRUE, map = TRUE, loc = ICPg240Locs, loc.byrow = TRUE,
field.type = "Precipitation", units = "mm/h",
data.name = "ICP Geometric Cases", obs.name = "geom000",
model.name = "geom001" )
metrV(testobj)
# compare above to results in Fig. 2 (top right panel)
# of Zhu et al. (2011). Note that they differ wildly.
# Perhaps because an actual elliptical area is taken in
# the paper instead of finding the values from the fields
# themselves?
## End(Not run)
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.