Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
programming_languages:r:parameter_description [2017/03/19 18:23] – [train method] phreazer | programming_languages:r:parameter_description [2017/03/26 18:26] (current) – [dtw] phreazer | ||
---|---|---|---|
Line 4: | Line 4: | ||
Issues: | Issues: | ||
- | * Documenting the possible entries is not easy, because a single model description already contains a lot of information. When many models must be described in help, the help page of the function becomes | + | * Documenting the possible entries is not easy, because a single model description already contains a lot of information. When many models must be described in help, the help page of the function becomes |
* The model description itself should be structured. | * The model description itself should be structured. | ||
Line 22: | Line 22: | ||
- | preProcess: a string vector that defines a pre-processing of the | + | |
predictor data. Current possibilities are " | predictor data. Current possibilities are " | ||
" | " | ||
Line 30: | Line 30: | ||
adjust them. Pre-processing code is only designed to work | adjust them. Pre-processing code is only designed to work | ||
when ‘x’ is a simple matrix or data frame. | when ‘x’ is a simple matrix or data frame. | ||
+ | |||
+ | |||
+ | getModelInfo shows infos about models and packages that are accessible via ‘train’ | ||
+ | |||
+ | Usage: | ||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | Value: | ||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | label : a tuning parameter label (used in plots) | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | Returned info from getModelInfo is a rather cryptic list. | ||
preProcess is a function which has it's own different method types. The methods are explained in the details section of the perProcess help page. | preProcess is a function which has it's own different method types. The methods are explained in the details section of the perProcess help page. | ||
+ | |||
trainControl is also a function, where different possible values for methods are listed, but not explained. Only hints which methods should be used under which circumstances. | trainControl is also a function, where different possible values for methods are listed, but not explained. Only hints which methods should be used under which circumstances. | ||
+ | |||
+ | ===== proxy ===== | ||
+ | |||
+ | # summary of available distance measures | ||
+ | summary(pr_DB) | ||
+ | # particular info about one distance measure | ||
+ | pr_DB$get_entry(" | ||
+ | | ||
+ | ===== dtw ===== | ||
+ | # directly print stepPattern (it's a class) | ||
+ | print(symmetric2) | ||
+ | | ||
+ | ===== arules ===== | ||
+ | object of class APparameter or named list. | ||