You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gilles (JIRA)" <ji...@apache.org> on 2015/08/20 22:06:45 UTC

[jira] [Resolved] (MATH-872) "inputSigma" specification in "CMAESOptimizer"

     [ https://issues.apache.org/jira/browse/MATH-872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gilles resolved MATH-872.
-------------------------
    Resolution: Fixed

Probably fixed some time ago: no deprecated code remains.

> "inputSigma" specification in "CMAESOptimizer"
> ----------------------------------------------
>
>                 Key: MATH-872
>                 URL: https://issues.apache.org/jira/browse/MATH-872
>             Project: Commons Math
>          Issue Type: Improvement
>    Affects Versions: 3.0
>            Reporter: Gilles
>            Assignee: Gilles
>            Priority: Minor
>             Fix For: 4.0
>
>
> The interface to the CM optimizers was designed to allow multiple "optimize" calls to the same optimizer with
> * different functions (even with a different number of parameters),
> * different start points,
> * different boundaries.
> "inputSigma" however depends on the number of parameters, and possibly on the start point and on the values of the upper and lower bounds. Specifying it at construction is slightly inconsistent with the intent of the API.
> One workaround is to have a separate accessor:
> {code}
> public void setSigma(double[] sigma)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)