commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MATH-872) "inputSigma" specification in "CMAESOptimizer"
Date Mon, 01 Oct 2012 22:11:07 GMT

    [ https://issues.apache.org/jira/browse/MATH-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467244#comment-13467244
] 

Gilles commented on MATH-872:
-----------------------------

If there aren't any objections, I would add the accessor and deprecate the constructors that
set "inputSigma" (to be removed in 4.0).
                
> "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: 3.1, 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message