[MATH-428] Simplify "DirectSearchOptimizer"

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.0
• Assignee: Gilles Sadowski
• Reporter: Gilles Sadowski
• Created: 21/Oct/10 11:09
• Updated: 24/Mar/12 16:16
• Resolved: 25/Oct/10 09:53

Description

This issue refers to classes in package optimization.direct.

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".