This function draws validation plots of a GP, DGP, or linked (D)GP emulator.
Usage
# S3 method for class 'dgp'
plot(
x,
x_test = NULL,
y_test = NULL,
dim = NULL,
method = "mean_var",
sample_size = 50,
style = 1,
min_max = TRUE,
normalize = TRUE,
color = "turbo",
type = "points",
verb = TRUE,
M = 50,
force = FALSE,
cores = 1,
...
)
# S3 method for class 'lgp'
plot(
x,
x_test = NULL,
y_test = NULL,
dim = NULL,
method = "mean_var",
sample_size = 50,
style = 1,
min_max = TRUE,
color = "turbo",
type = "points",
M = 50,
verb = TRUE,
force = FALSE,
cores = 1,
...
)
# S3 method for class 'gp'
plot(
x,
x_test = NULL,
y_test = NULL,
dim = NULL,
method = "mean_var",
sample_size = 50,
style = 1,
min_max = TRUE,
color = "turbo",
type = "points",
verb = TRUE,
M = 50,
force = FALSE,
cores = 1,
...
)Arguments
- x
can be one of the following emulator classes:
the S3 class
gp.the S3 class
dgp.the S3 class
lgp.
- x_test
same as that of
validate().- y_test
same as that of
validate().- dim
if
dim = NULL, the index of an emulator's input within the design will be shown on the x-axis in validation plots. Otherwise,dimindicates which dimension of an emulator's input will be shown on the x-axis in validation plots:If
xis an instance of thegpofdgpclass,dimis an integer.If
xis an instance of thelgpclass,dimis an integer referring to the dimension of the global input to the linked emulator system.
This argument is only used when
style = 1. Defaults toNULL.- method
same as that of
validate().- sample_size
same as that of
validate().- style
either
1or2, indicating two different plotting styles for validation.- min_max
a bool indicating if min-max normalization will be used to scale the testing output, RMSE, predictive mean and std from the emulator. Defaults to
TRUE. This argument is not applicable to DGP emulators with categorical likelihoods.- normalize
a bool indicating if normalization will be used to scale the counts in validation plots of DGP emulators with categorical likelihoods when
style = 2. Defaults toTRUE.- color
a character string indicating the color map to use when
style = 2:'magma'(or'A')'inferno'(or'B')'plasma'(or 'C')'viridis'(or'D')'cividis'(or'E')'rocket'(or'F')'mako'(or'G')'turbo'(or'H')
Defaults to
'turbo'(or'H').- type
either
'line'or'points, indicating whether to draw testing data in the OOS validation plot as a line or individual points when the input of the emulator is one-dimensional andstyle = 1. This argument is not applicable to DGP emulators with categorical likelihoods. Defaults to'points'- verb
a bool indicating if trace information on plotting will be printed during execution. Defaults to
TRUE.- M
same as that of
validate().- force
same as that of
validate().- cores
same as that of
validate().- ...
N/A.
Details
See further examples and tutorials at https://mingdeyu.github.io/dgpsi-R/.
Note
plot()callsvalidate()internally to obtain validation results for plotting. However,plot()will not export the emulator object with validation results. Instead, it only returns the plotting object. For small-scale validations (i.e., small training or testing data points), direct execution ofplot()works well. However, for moderate- to large-scale validation, it is recommended to first runvalidate()to obtain and store validation results in the emulator object, and then supply the object toplot().plot()checks the object'slooandoosslots prior to callingvalidate()and will not perform further calculation if the required information is already stored.plot()will only use stored OOS validation ifx_testandy_testare identical to those used byvalidate()to produce the data contained in the object'soosslot, otherwiseplot()will re-evaluate OOS validation before plotting.The returned patchwork::patchwork object contains the ggplot2::ggplot2 objects. One can modify the included individual ggplots by accessing them with double-bracket indexing. See https://patchwork.data-imaginist.com/ for further information.
