commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles (JIRA)" <>
Subject [jira] Resolved: (MATH-428) Simplify "DirectSearchOptimizer"
Date Mon, 25 Oct 2010 09:55:19 GMT


Gilles resolved MATH-428.

    Resolution: Fixed

I went on and committed the changes in revision 1027007, as none of the current tests can
demonstrate the necessity of the loop in the {{iterateSimplex}} method of {{MultiDirectional}}.

> Simplify "DirectSearchOptimizer"
> --------------------------------
>                 Key: MATH-428
>                 URL:
>             Project: Commons Math
>          Issue Type: Improvement
>            Reporter: Gilles
>            Assignee: Gilles
>            Priority: Minor
>             Fix For: 3.0
>         Attachments:, opt_direct.tar.gz
> This issue refers to classes in package {{}}.
> Currently the class {{NelderMead}} inherits from {{DirectSearchOptimizer}}. However the
method {{doOptimize}} is implemented in {{DirectSearchOptimizer}}. This is backwards from
the intended design (where an "optimizer" is defined as a class that implements a specific
algorithm within {{doOptimize}}). According to this "terminology", {{DirectSearchOptimizer}}
is the optimizer whereas {{NelderMead}} could be considered as a specific way to construct
a simplex. Indeed, that's what seems intended since it overrides the abstract method {{iterateSimplex}}.
> I suggest to create 2 classes that will make it clear the separation between the "optimizer"
and the "simplex manager".

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message