Uploaded image for project: 'OptaPlanner'
  1. OptaPlanner
  2. PLANNER-305

Solver phases configuration should be optional

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • 6.3.0.Beta1
    • None
    • optaplanner-core
    • None

      Problem: too many choices in 6.1 scare users away, see the negative blog post here http://blog.clairvoyantsoft.com/2015/02/optaplanner/

      Default to a CH with FFD and a LS with LA 400.
      This also means that LS should get a LocalSearchType parameter.

      Refactor CloudBalancing example and tutorial accordingly.
      Clearly document that not specifying == subject yourself to our defaults even if they change during upgrades (which is usually for their best interest, but not always)

            gdesmet@redhat.com Geoffrey De Smet (Inactive)
            gdesmet@redhat.com Geoffrey De Smet (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: