The hardware and bandwidth for this mirror is donated by dogado GmbH, the Webhosting and Full Service-Cloud Provider. Check out our Wordpress Tutorial.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]dogado.de.
optimsimplex
packageoptimsimplex
is a R port of a module originally developed for Scilab version 5.2.1 by Michael Baudin (INRIA - DIGITEO). Information about this software can be found at www.scilab.org. The following documentation as well as the content of the functions .Rd files are adaptations of the documentation provided with the original Scilab optimsimplex module.
The goal of this package is to provide a building block for optimization algorithms based on a simplex. The optimsimplex
package may be used in the following optimization methods:
This set of commands allows to manage a simplex made of \(k\ge n+1\) points in a \(n\)-dimensional space. This component is the building block for a class of direct search optimization methods such as the Nelder-Mead algorithm or Torczon’s Multi-Dimensionnal Search.
A simplex is designed as a collection of \(k\ge n+1\) vertices. Each vertex is made of a point and a function value at that point.
The simplex can be created with various shapes. It can be configured and queried at will. The simplex can also be reflected or shrinked. The simplex gradient can be computed with a order 1 forward formula and with a order 2 centered formula.
The optimsimplex
function allows to create a simplex. If vertices coordinates are given, there are registered in the simplex. If a function is provided, it is evaluated at each vertex. Several functions allow to create a simplex with special shapes and methods, including axes-by-axes (optimsimplex.axes
), regular (optimsimplex.spendley
), randomized bounds simplex with arbitrary \(nbve\) vertices (optimsimplex.randbounds
) and an heuristical small variation around a given point (optimsimplex.pfeffer
).
In the functions provided in this package, simplices and vertices are, depending on the functions either input or output arguments. The following general principle have been used to manage the storing of the coordinates of the points.
Most functions in the optimsimplex
package accept a fun
argument, which corresponds to the function to be evaluated at the given vertices. The function is expected to have the following input and output arguments:
myfunction <- function(x, this){
...
return(list(f=f,this=this))
}
where x
is a row vector, f
is the function value, and this
an optional user-defined data passed to the function. If data is provided, it is passed to the callback function both as an input and output argument. data
may be used if the function uses some additional parameters. It is returned as an output parameter because the function may modify the data while computing the function value. This feature may be used, for example, to count the number of times that the function has been called.
In the following example, one creates a simplex with known vertices coordinates and queries the new object. The function values at the vertices are unset.
coords <- matrix(c(0,1,0,0,0,1),ncol=2)
tmp <- optimsimplex(coords=coords)
s1 <- tmp$newobj
s1
## Dimension: n=2
## Number of vertices: nbve=3
## Empty simplex (zero function values)
## NA NA
optimsimplex.getallx(s1)
## [,1] [,2]
## [1,] 0 0
## [2,] 1 0
## [3,] 0 1
optimsimplex.getn(s1)
## [1] 2
optimsimplex.getnbve(s1)
## [1] 3
In the following example, one creates a simplex with in the 2D domain \(c(-5, 5)^{}2\), with c(-1.2, 1.0) as the first vertex. One uses the randomized bounds method to generate a simplex with 5 vertices. The function takes an additional argument this
, which counts the number of times the function is called. After the creation of the simplex, the value of this$nb
is 5, which is the expected result because there is one function call by vertex.
rosenbrock <- function(x){
y <- 100*(x[2]-x[1]^2)^2+(1-x[1])^2
}
mycostf <- function(x, this){
y <- rosenbrock(x)
this$nb <- this$nb+1
return(list(f=y,this=this))
}
mystuff <- list(nb=0)
tmp <- optimsimplex(x0=c(-1.2,1.0), fun=mycostf, method='randbounds',
boundsmin=c(-5.0,-5.0), boundsmax=c(5.0,5.0), nbve=5,
data=mystuff)
tmp$newobj
## Dimension: n=2
## Number of vertices: nbve=5
## Vertex #1/5 : fv=2.420000e+01, x=-1.200000e+00 1.000000e+00
## Vertex #2/5 : fv=2.327215e+04, x=3.471708e+00 -3.200451e+00
## Vertex #3/5 : fv=6.661542e+04, x=4.689782e+00 -3.813266e+00
## Vertex #4/5 : fv=2.592133e+03, x=9.946533e-01 -4.101964e+00
## Vertex #5/5 : fv=1.037489e+03, x=2.391469e+00 2.501126e+00
tmp$data
## $nb
## [1] 5
cat(sprintf("Function evaluations: %d\n",tmp$data$nb))
## Function evaluations: 5
In this section, we analyse the various initial simplex which are provided in this component.
It is known that direct search methods based on simplex designs are very sensitive to the initial simplex. This is why the current component provides various ways to create such an initial simplex.
The first historical simplex-based algorithm is the one presented in “Sequential Application of Simplex Designs in Optimisation and Evolutionary Operation” by W. Spendley, G. R. Hext and F. R. Himsworth. The “spendley” simplex creates the regular simplex which is presented in the paper [1].
The “randbounds” simplex is due to M.J. Box in “A New Method of Constrained Optimization and a Comparison With Other Methods” [2].
Pfeffer’s method is an heuristic which is presented in “Global Optimization Of Lennard-Jones Atomic Clusters” by E. Fan [3]. It is due to L. Pfeffer at Stanford and it is used in the fminsearch
function from the neldermead
package.
optimsimplex
functionsThe network of functions provided in optimsimplex
is illustrated in the network map given in the neldermead
package.
The functions distributed in optimsimplex
are also based upon the work from Nelder and Mead [4], Kelley [5], Han and Neumann [6], Torczon torczon_1989, Burmen et al. [7], and Price and al. [8].
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.