spotPredictMCO: Meta Model Interface: Multi Criteria Modelling

Description Usage Arguments Value


This interface function is supposed to be used for Multi Criteria Problems. It can be employed when the user wants to specify different models for each of the objectives, instead of modelling all the objectives with the same technique. The user has therefore to specify a list of configurations, where the different models and their settings are specified.


spotPredictMCO(rawB, mergedB, design, spotConfig, fit = NULL)



unmerged data


merged data


new design points which should be predicted


global list of all options, needed to provide data for calling functions. The most important elements in this list are here:
spotConfig$mco.configs list of model configurations, e.g. =list(list(seq.predictionModel.func="spotPredictForrester",seq.forr.lambda.upval=-5),list(seq.predictionModel.func="spotPredictForrester",seq.forr.lambda.upval=-1))
In this example, two Kriging models are specified for each of two objectives, but with different settings for the lower boundary of lambda. Else, different models could be specified, e.g., =list(list(seq.predictionModel.func="spotPredictForrester"),list(seq.predictionModel.func="spotPredictLm"))


if an existing model fit is supplied, the model will not be build based on data, but only evaluated with the model fit (on the design data). To build the model, this parameter has to be NULL. If it is not NULL the parameters mergedB and rawB will not be used at all in the function.


returns the list spotConfig with two new entries:
spotConfig$seq.modelFit fit of the model used with the predictor functions
spotConfig$seq.largeDesignY the y values of the design, evaluated with the fit

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

Questions? Problems? Suggestions? or email at

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

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