renderYTraces

Can be used for only single-objective optimization paths. Useful
to compare runs of different algorithms on the same optimization problem. You
can add your own ggplot layers to the resulting plot object.

Functions for parameter descriptions and operations in
black-box optimization, tuning and machine learning. Parameters can be
described (type, constraints, defaults, etc.), combined to parameter
sets and can in general be programmed on. A useful OptPath object
(archive) to log function evaluations is also provided.

Martin Binder

ParamHelpers

Helpers for Parameters in Black-Box Optimization, Tuning and
Machine Learning

Bernd Bischl

Michel Lang

Jakob Richter

Jakob Bossek

Daniel Horn

Karin Schork

Pascal Kerschke

renderYTraces function

<dl><dt>opt.paths</dt>
<dd>[<code>OptPath()</code> | list of <code>OptPath()</code>] 
Object(s) to plot.</dd>
<dt>over.time</dt>
<dd><code><a href="/link/character?package=ParamHelpers&version=1.14.2" data-mini-rdoc="ParamHelpers::character">character</a></code> 
Should the traces be plotted versus the iteration number or the cumulated
execution time? For the later, the opt.path has to contain a extra column
names exec.time. Possible values are dob and exec.time, default is <code>dob</code>.</dd></dl>

Arguments

Plots Y traces of multiple optimization paths — renderYTraces

<dl>

<dt>opt.paths</dt>
<dd>[<code>OptPath()</code> | list of <code>OptPath()</code>] 
Object(s) to plot.</dd>


<dt>over.time</dt>
<dd><code><a href='https://rdrr.io/r/base/character.html'>character</a></code> 
Should the traces be plotted versus the iteration number or the cumulated
execution time? For the later, the opt.path has to contain a extra column
names exec.time. Possible values are dob and exec.time, default is <code>dob</code>.</dd>

</dl>

renderYTraces: Plots Y traces of multiple optimization paths

Description

Usage

Value

Arguments