bundle.H2OAutoML {bundle} | R Documentation |
Bundle an h2o
object
Description
Bundling a model prepares it to be saved to a file and later restored for prediction in a new R session. See the 'Value' section for more information on bundles and their usage.
Usage
## S3 method for class 'H2OAutoML'
bundle(x, id = NULL, n = NULL, ...)
## S3 method for class 'H2OMultinomialModel'
bundle(x, ...)
## S3 method for class 'H2OBinomialModel'
bundle(x, ...)
## S3 method for class 'H2ORegressionModel'
bundle(x, ...)
Arguments
x |
An object returned from modeling functions in the h2o package. |
id |
A single character. The |
n |
An integer giving the position in the leaderboard of the model
to bundle. Applies to AutoML output only. Will be ignored if |
... |
Not used in this bundler and included for compatibility with the generic only. Additional arguments passed to this method will return an error. |
Value
A bundle object with subclass bundled_h2o
.
Bundles are a list subclass with two components:
object |
An R object. Gives the output of native serialization methods from the model-supplying package, sometimes with additional classes or attributes that aid portability. This is often a raw object. |
situate |
A function. The |
Bundles are R objects that represent a "standalone" version of their
analogous model object. Thus, bundles are ready for saving to a file; saving
with base::saveRDS()
is our recommended serialization strategy for bundles,
unless documented otherwise for a specific method.
To restore the original model object x
in a new environment, load its
bundle with base::readRDS()
and run unbundle()
on it. The output
of unbundle()
is a model object that is ready to predict()
on new data,
and other restored functionality (like plotting or summarizing) is supported
as a side effect only.
The bundle package wraps native serialization methods from model-supplying packages. Between versions, those model-supplying packages may change their native serialization methods, possibly introducing problems with re-loading objects serialized with previous package versions. The bundle package does not provide checks for these sorts of changes, and ought to be used in conjunction with tooling for managing and monitoring model environments like vetiver or renv.
See vignette("bundle")
for more information on bundling and its motivation.
See Also
These methods wrap h2o::h2o.save_mojo()
and
h2o::h2o.saveModel()
.
Other bundlers:
bundle.keras.engine.training.Model()
,
bundle.luz_module_fitted()
,
bundle.model_fit()
,
bundle.model_stack()
,
bundle.recipe()
,
bundle.step_umap()
,
bundle.train()
,
bundle.workflow()
,
bundle.xgb.Booster()
,
bundle()
Examples
# fit model and bundle ------------------------------------------------
library(h2o)
set.seed(1)
h2o.init()
cars_h2o <- as.h2o(mtcars)
cars_fit <-
h2o.glm(
x = colnames(cars_h2o)[2:11],
y = colnames(cars_h2o)[1],
training_frame = cars_h2o
)
cars_bundle <- bundle(cars_fit)
# then, after saveRDS + readRDS or passing to a new session ----------
cars_unbundled <- unbundle(cars_fit)
predict(cars_unbundled, cars_h2o[, 2:11])
h2o.shutdown(prompt = FALSE)