commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gilles Sadowski <>
Subject Re: AW: [math] CMA-ES optimization algorithm
Date Fri, 26 Nov 2010 13:23:53 GMT

> > [...]
> > Question is how reconfigure() is configured?
> It is entirely up to the user who implements it, and it depends on the
> algorithm he chose. If the algorithm does have some setXxx() setter, he
> could do:
>  public DifferentiableMultivariateVectorialOptimizer
>      reconfigure(DifferentiableMultivariateVectorialOptimizer optimizer,
>                  RandomGenerator r) {
>   optimizer.setXxx(r.nextDouble());
>   return optimizer;
>  }
> otherwise (i.e. if the optimizer is immutable, which is the best thing
> to do), he would simply create a new instance.

Indeed, all the parameters should be passed to the constructor(s).

Please note that this is not a simple change since it departs from the
current semantics of "MultiStartOptimizer" where the restart are handled
by multiple calls to the "optimize" method (with a different start value)
whereas, it would now be handled by multiple instantiations of the
underlying optimizer.

> [...]


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message