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

Planner Benchmarker should detect a bad BEST_SOLUTION_CHANGED graph and warn about it

XMLWordPrintable

      See the screenshot of the difference between a good graph and a bad graph.

      The quality of the graph can be determinated by taking the 10% of time Score relative to the (final Score minus the first feasible score)

      Extra difficulty is that this needs to be Score implementation agnostic.
      Use Score.toDoubleArray() to this on every level (notice that the first feasible score means the first feasible for that level).

        1. badBecauseScoreTrap.png
          37 kB
          Geoffrey De Smet
        2. good_vs_bad_graph.png
          45 kB
          Geoffrey De Smet

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

                Created:
                Updated: