Description Usage Arguments Details Value Author(s) Examples
container for information specifying a cross-validated machine learning exercise
1 2 3 |
type |
a string, "LOO" indicating leave-one-out cross-validation, or "LOG" indicating leave-out-group, or "NOTEST", indicating the entire dataset is used in a single training run. |
niter |
numeric specification of the number of
cross-validation iterations to use. Ignored if |
partitionFunc |
function, with parameters data (bound
to data.frame), clab (bound to character string), iternum (bound
to numeric index into sequence of 1: |
fsFun |
function, with parameters formula, data. The function must return a formula suitable for defining a model on the basis of the main input data. A candidate fsFun is given in example for fsHistory function. |
If type == "LOO"
, no other parameters are inspected.
If type == "LOG"
a value for partitionFunc
must be
supplied. We recommend using balKfold.xvspec(K)
. The
values of niter
and K
in this usage must be the same.
This redundancy will be removed in a future upgrade.
If the parallel
package is attached and symbol mc_fork
is loaded, cross-validation will
be distributed to cores using mclapply
.
An instance of classifierOutput
, with a special
structure. The RObject
return slot is populated with a
list of niter
cross-validation results. Each element of this list
is itself a list with two elements: test.idx
(the indices
of the test set for the associated cross-validation iteration,
and mlans
, the classifierOutput
generated at
each iteration. Thus there are classifierOutput
instances nested within the main classifierOutput
returned
when a xvalSpec
is used.
Vince Carey <stvjc@channing.harvard.edu>
1 2 3 4 5 6 7 8 9 10 11 12 |
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.