Expose CMAEvolutionStrategy sigma0?

Open anicusan opened this issue 6 months ago • 1 comments

The "only" CMA-ES hyperparameter normally set by users is hardcoded as 0.1 in the code below:

https://github.com/SciML/Optimization.jl/blob/master/lib/OptimizationCMAEvolutionStrategy/src/OptimizationCMAEvolutionStrategy.jl#L112C1-L113C1

Is this deliberate, or is there some internal parameter rescaling I don't see?

If not, I am happy to submit a pull request to expose this as a keyword argument to the CMAEvolutionStrategyOpt constructor.

Oct 23 '25 08:10 anicusan

Not deliverate. It should be elevated to being an algorithm argument

Oct 23 '25 09:10 ChrisRackauckas