Faq get different cross validation results from command line crossval routine compared to Analysis window

From Eigenvector Research Documentation Wiki
Revision as of 09:51, 19 December 2018 by imported>Lyle (Created page with "===Issue:=== Why do I get different cross-validation results from the command-line crossval routine compared to the Analysis window? ===Possible Solutions:=== There are two...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Issue:

Why do I get different cross-validation results from the command-line crossval routine compared to the Analysis window?

Possible Solutions:

There are two possible causes of this:

Preprocess Option Unassigned

The most common cause is that you have not set the same preprocessing in the crossval function (see the "preprocessing" option) as you are using in the Analysis window. You should use the preprocess function to define the same preprocessing you are using in Analysis and pass this into the crossval function via the preprocessing option.

Preprocessing Outside Cross-Validation

The next possible cause is that you are doing the preprocessing outside of cross-validation. Preprocessing should always be done inside of cross-validation to help avoid over-fitting models.


Still having problems? Please contact our helpdesk at helpdesk@eigenvector.com