1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/updates.R
\name{update.train}
\alias{update.train}
\title{Update or Re-fit a Model}
\usage{
\method{update}{train}(object, param = NULL, ...)
}
\arguments{
\item{object}{an object of class \code{\link{train}}}
\item{param}{a data frame or named list of all tuning parameters}
\item{\dots}{not currently used}
}
\value{
a new \code{\link{train}} object
}
\description{
\code{update} allows a user to over-ride the tuning parameter selection
process by specifying a set of tuning parameters or to update the model
object to the latest version of this package.
}
\details{
If the model object was created with version 5.17-7 or earlier, the
underlying package structure was different. To make old \code{\link{train}}
objects consistent with the new structure, use \code{param = NULL} to get
the same object back with updates.
To update the model parameters, the training data must be stored in the
model object (see the option \code{returnData} in
\code{\link{trainControl}}. Also, all tuning parameters must be specified in
the \code{param} slot. All other options are held constant, including the
original pre-processing (if any), options passed in using code... and so on.
When printing, the verbiage "The tuning parameter was set manually." is used
to describe how the tuning parameters were created.
}
\examples{
\dontrun{
data(iris)
TrainData <- iris[,1:4]
TrainClasses <- iris[,5]
knnFit1 <- train(TrainData, TrainClasses,
method = "knn",
preProcess = c("center", "scale"),
tuneLength = 10,
trControl = trainControl(method = "cv"))
update(knnFit1, list(.k = 3))
}
}
\seealso{
\code{\link{train}}, \code{\link{trainControl}}
}
\author{
Max Kuhn
}
\keyword{models}
|
