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

If 2 planning variables share elements in their value range, tabu'ing a value for 1 variable should not tabu it for the other variable.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • Future
    • None
    • None

      AKA Tabu should be namespaced per variable.

      Entity class: Foo
      Entities:

      {A, B, C}

      Variables on Foo:

      {alpha, beta}

      Value range for alpha:

      {1, 2, 3}

      Value range for beta:

      {1, 2, 4}

      If a picked move moves alpha to value 2, making value 2 tabu,
      then it should only be tabu for variable alpha, not for variable beta too.
      Currently, the implementation throws all tabu values on 1 big pile, making them tabu for all variables.

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

              Created:
              Updated: