
These functions calculate the npv()
(negative predictive value) of a
measurement system compared to a reference result (the "truth" or gold standard).
Highly related functions are spec()
, sens()
, and ppv()
.
npv(data, ...)# S3 method for data.frame
npv(
data,
truth,
estimate,
prevalence = NULL,
estimator = NULL,
na_rm = TRUE,
...
)
npv_vec(
truth,
estimate,
prevalence = NULL,
estimator = NULL,
na_rm = TRUE,
...
)
Either a data.frame
containing the truth
and estimate
columns, or a table
/matrix
where the true class results should be
in the columns of the table.
Not currently used.
The column identifier for the true class results
(that is a factor
). This should be an unquoted column name although
this argument is passed by expression and supports
quasiquotation (you can unquote column
names). For _vec()
functions, a factor
vector.
The column identifier for the predicted class
results (that is also factor
). As with truth
this can be
specified different ways but the primary method is to use an
unquoted variable name. For _vec()
functions, a factor
vector.
A numeric value for the rate of the "positive" class of the data.
One of: "binary"
, "macro"
, "macro_weighted"
,
or "micro"
to specify the type of averaging to be done. "binary"
is
only relevant for the two class case. The other three are general methods for
calculating multiclass metrics. The default will automatically choose "binary"
or "macro"
based on estimate
.
A logical
value indicating whether NA
values should be stripped before the computation proceeds.
A tibble
with columns .metric
, .estimator
,
and .estimate
and 1 row of values.
For grouped data frames, the number of rows returned will be the same as the number of groups.
For npv_vec()
, a single numeric
value (or NA
).
There is no common convention on which factor level should
automatically be considered the "event" or "positive" result.
In yardstick
, the default is to use the first level. To
change this, a global option called yardstick.event_first
is
set to TRUE
when the package is loaded. This can be changed
to FALSE
if the last level of the factor is considered the
level of interest by running: options(yardstick.event_first = FALSE)
.
For multiclass extensions involving one-vs-all
comparisons (such as macro averaging), this option is ignored and
the "one" level is always the relevant result.
Macro, micro, and macro-weighted averaging is available for this metric.
The default is to select macro averaging if a truth
factor with more
than 2 levels is provided. Otherwise, a standard binary calculation is done.
See vignette("multiclass", "yardstick")
for more information.
Suppose a 2x2 table with notation:
Reference | ||
Predicted | Positive | Negative |
Positive | A | B |
Negative | C | D |
The formulas used here are:
See the references for discussions of the statistics.
The positive predictive value (ppv()
) is defined as the percent of
predicted positives that are actually positive while the
negative predictive value (npv()
) is defined as the percent of negative
positives that are actually negative.
Altman, D.G., Bland, J.M. (1994) ``Diagnostic tests 2: predictive values,'' British Medical Journal, vol 309, 102.
Other class metrics:
accuracy()
,
bal_accuracy()
,
detection_prevalence()
,
f_meas()
,
j_index()
,
kap()
,
mcc()
,
ppv()
,
precision()
,
recall()
,
sens()
,
spec()
# NOT RUN {
# Two class
data("two_class_example")
npv(two_class_example, truth, predicted)
# Multiclass
library(dplyr)
data(hpc_cv)
hpc_cv %>%
filter(Resample == "Fold01") %>%
npv(obs, pred)
# Groups are respected
hpc_cv %>%
group_by(Resample) %>%
npv(obs, pred)
# Weighted macro averaging
hpc_cv %>%
group_by(Resample) %>%
npv(obs, pred, estimator = "macro_weighted")
# Vector version
npv_vec(two_class_example$truth, two_class_example$predicted)
# Making Class2 the "relevant" level
options(yardstick.event_first = FALSE)
npv_vec(two_class_example$truth, two_class_example$predicted)
options(yardstick.event_first = TRUE)
# }
Run the code above in your browser using DataLab