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

Vehicle Routing etc: simplify the domain model @PlanningCollectionVariable(type = DISTINCT_LIST) - VRP simplification (Phase 1)

XMLWordPrintable

    • VRP simplification 1
    • Done
    • 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26
    • NEW
    • NEW

      For Vehicle Routing and project job scheduling users want to use this model:

      @PlanningEntity // No longer a shadow
      public class  Vehicle {
         @PlanningVariableCollection(type = DISTINCT_LIST)
         List<Customer> customerList; // genuine!
      }
      
      @PlanningEntity // Now a shadow
      public class Customer {
        @AnchorShadowVariable Vehicle vehicle;
      }
      

      Although this might have a small performance loss in basic setups (think 2opts on not-anymore linked lists), it might have a lower gain too (think pillar and subchain swaps)

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

                Created:
                Updated:
                Resolved: