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

Nearby entity selection to select 2 entities that are somehow related (close to each other for example)

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Blocker
    • 6.2.0.Final
    • None
    • optaplanner-core
    • None

    Description

      In VRP, when there are 150 000 customers, there's little point in swapping customer A and Z if they are on oppose ends of the region. So when A is selected as primary entity, we want to have a high chance of selecting a secondary entity close to A (although the chance to select something far should be almost zero but not zero).

      Configuration might look something like this:

      <swapMoveSelector>
  <primary entitySelector id="leader"/>
  <secondary nearByEntitySelector>
     <mimicEntitySelector ref="leader"/>
     <nearByFinderClass>...NearByFinder</>
     <randomDistribution>NORMAL || GAUSS</>
   </>
</>

      The same system might be reused in exam scheduling for course grained moves where one of the entities is a leader:

      <cartesianMoveSelector>
  <changeMoveSelector>
    <entitySelector id="leader"/>
  </>
  <changeMoveSelector>
    <nearByEntitySelector>
       <mimicEntitySelector ref="leader"/>
       <nearByFinderClass>...MyNearByFinder</>
       <randomDistribution>NORMAL || GAUSS</>
     </>
   </>
</>

      MyNearByFinder could have an interface something like this

      Object nearByEntity(Object mainEntity, ScoreDirector scoreDirector);

      but what I really want is to have planner configuration deal with the NORMAL || GAUSS randomDistribution directly, so I want this too:

       // 0 < nearByIndex < entityCount
// nearByIndex has a a high chance of being 1, 2, ... and a low chance of being ..., entityCount - 2, entityCount - 1.
Object nearByEntity(Object mainEntity, int nearByIndex);

      Attachments

        Issue Links

          is related to

          Feature Request - Feature requests from customers and/or users PLANNER-289 Nearby selection for declarative value ranges (required for financial optimization)

          • Critical - To be worked on immediately following BLOCKER issues.
          • Open
          relates to

          Feature Request - Feature requests from customers and/or users PLANNER-187 Support 3opt+ move selectors out-of-the-box for VRP

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) PLANNER-211 Beta distribution (Guassian/gauss distribution) in random selection on a ValueRange

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) PLANNER-228 Chained variables should support value range from entity too

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Open

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: