krigr_cross_validation: Multithreaded cross validation routine for Omic Kriging.

Description Usage Arguments Value

View source: R/omic_KRIGR.R


This is a flexible cross validation routine which wraps the Omic Kriging calculation. The user can specify the size of the test set, all the way to "Leave One Out" cross validation. Additionally, all relevant parameters in the okriging function are exposed. This function uses the doParallel package to distribute computation over multiple cores. If the phenotype is case/control, a ROCR AUC and GLM analysis is run and the results printed to screen.


krigr_cross_validation(cor.list, pheno.df, = 1, h2.vec,
  covar.mat = NULL, nfold = 10, ncore = "all", verbose = FALSE, ...)



A list of correlation matrices used in Kriging. rownames and colnames of cor should be IID list and include idtest and idtrain.


A data frame with rownames set as sample IDs and a column containing phenotype data.

The name of the column in pheno which contains phenotype data to test.


has weights for each RM relatednes matrix


Data frame of covariates with rownames() set to sample IDs.


Select the number of cross validation rounds to run. The value "LOOCV" will run one round of cross validation for each sample in your dataset. The value "ncore" will set the test set size such that a single round runs on each core specified in the ncore option. Any numeric value will be set to the test size. Default runs 10 rounds of cross validation.


The number of cores available to distribute computaition across If a numeric value is supplied, that number of cores is registered. If the value "all" is supplied, all available cores are used.


Report rounds on cross validation on standard out.


Optional and unnamed arguments.


A dataframe with three columns: sample ID, observed phenotype Ytest, and predicted phenotype Ypred

OmicKriging documentation built on May 19, 2017, 9:53 a.m.

Search within the OmicKriging package
Search all R packages, documentation and source code

Questions? Problems? Suggestions? Tweet to @rdrrHQ or email at

Please suggest features or report bugs in the GitHub issue tracker.

All documentation is copyright its authors; we didn't write any of that.