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

ScoreDirector's constraintMatchEnabled should be false when possible: performance speedup for DRL based score calculation

    XMLWordPrintable

Details

    • Enhancement
    • Status: Resolved (View Workflow)
    • Critical
    • Resolution: Done
    • 6.1.0.CR1
    • 6.2.0.Beta1
    • None
    • None

    Description

      "it immediately adds 10 % average calculate count to my solver, without any score corruption."

      Here's why I didn't turn it on at the time immediately:
      We can't turn constraintMatchEnabled to false all the time,
      because without it, there's no justification, which is needed in 2 cases:

      • In OptaPlanner Examples GUI, when you click "constraint match" on the bottom right,
        it needs to explain what is violating which constraints.
        That uses Solver.getScoreDirectorFactory() and needs justification for that ScoreDirector.
      • Guided Local Search (= a well established LS variant), Tainted Search (= my unimplemented invention)
        need justification too. For example: focus on moving the queen that breaks most constraints.

      I am thinking that constraintMatchEnabled is true by default, but for solver with no phases that require justification,
      it can be turned off.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: