ParamHelpers (version 1.1-36)

addOptPathEl: Add a new element to an optimization path.

Description

Changes the argument in-place. Note that when adding parameters that have associated tranformations, it is probably best to add the untransformed values to the path. Otherwise you have to switch off the feasibility check, as constraints might now not hold anymore.

Usage

addOptPathEl(op, x, y, dob = getOptPathLength(op) + 1L,
    eol = as.integer(NA),
    check.feasible = !op$add.transformed.x)

Arguments

op

[OptPath] Optimization path.

x

[list] List of parameter values for a point in input space. Must be in same order as parameters.

y

[numeric] Vector of fitness values. Must be in same order as y.names.

dob

[integer(1)] Date of birth of the new parameters. Default is length of path + 1.

eol

[integer(1)] End of life of point. Default is NA.

check.feasible

[logical(1)] Should x be checked with isFeasible? Default is TRUE.

Value

• Nothing.

Details

Dependent parameters whose requirements are not satisfied must be represented by a scalar NA in the input.

Examples

ps <- makeParamSet(
  makeNumericParam("p1"),
  makeDiscreteParam("p2", values=c("a", "b"))
)
op <- makeOptPathDF(par.set=ps, y.names="y", minimize=TRUE)
addOptPathEl(op, x=list(p1=7, p2="b"), y=1)
addOptPathEl(op, x=list(p1=-1, p2="a"), y=2)
as.data.frame(op)