Uploaded image for project: 'Commons Math'
  1. Commons Math
  2. MATH-428

Simplify "DirectSearchOptimizer"

Rank to TopRank to BottomBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersConvert to sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 3.0
    • None
    • None

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

      Attachments

        1. opt_direct.tar.gz
          7 kB
          Gilles Sadowski
        2. MultiDirectionalSimplex.java
          7 kB
          Gilles Sadowski

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            erans Gilles Sadowski
            erans Gilles Sadowski
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment