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

Workbench: support every generic move selector

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Won't Do
    • Icon: Minor Minor
    • Future
    • None
    • optaplanner-wb
    • None
    • NEW
    • NEW

      In the solver editor, in a CH or LS solver phase, allow specifying the exact move selectors used. Most users do this (especially on non-trivial use cases).

      Don't allow to select tailChainSwapMoveSelector if there is no chained variable in the data model.
      http://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#moveAndNeighborhoodSelection

      Here's that list currently:

      • 7.2.1. changeMoveSelector
      • 7.2.2. swapMoveSelector
      • 7.2.3. pillarChangeMoveSelector
      • 7.2.4. pillarSwapMoveSelector
      • 7.2.5. tailChainSwapMoveSelector or 2-opt (chained variables only)
      • 7.2.6. subChainChangeMoveSelector (chained variables only)
      • 7.2.7. subChainSwapMoveSelector (chained variables only)

              jlocker Jiří Locker (Inactive)
              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: