向车辆路径问题添加新的规划变量

Question

I'm trying to add a new variable to the Vehicle Routing Problem to represent a vehicle (bus) picking up people and let them in locations with match some facts (these resources must attend one customer each). I have created a new class called Resource and declared a new resource variable inside the Customer class, so when a new move is made, I want the solver to select a new Customer to a Vehicle (route) and a Resource from the list (which eventually will be also in the vehicle, as well). In the Customer.java:

@PlanningVariable(valueRangeProviderRefs = {"resourceRange"})
public Resource getResource() {
    return resource;
}

public void setResource(Resource resource) {
    this.resource = resource;
}

And in the VehicleRoutingSolution.java:

protected List<Resource> resourceList;

[...]

@ProblemFactCollectionProperty
@ValueRangeProvider(id = "resourceRange")
public List<Resource> getResourceList() {
    return resourceList;
}

public void setResourceList(List<Resource> resourceList) {
    this.resourceList = resourceList;
}

Finally I have made some changes to the vehicleRoutingSolverConfig.xml:

<?xml version="1.0" encoding="UTF-8"?>
<solver>
  <!--<environmentMode>FAST_ASSERT</environmentMode>-->
  <solutionClass>com.ezentis.mplanner.vehiclerouting.domain.VehicleRoutingSolution</solutionClass>
  <entityClass>com.ezentis.mplanner.vehiclerouting.domain.Standstill</entityClass>
  <entityClass>com.ezentis.mplanner.vehiclerouting.domain.Customer</entityClass>
  <entityClass>com.ezentis.mplanner.vehiclerouting.domain.timewindowed.TimeWindowedCustomer</entityClass>

  <scoreDirectorFactory>
    <!--<easyScoreCalculatorClass>com.ezentis.mplanner.vehiclerouting.solver.score.VehicleRoutingEasyScoreCalculator</easyScoreCalculatorClass>-->
    <incrementalScoreCalculatorClass>com.ezentis.mplanner.vehiclerouting.solver.score.VehicleRoutingIncrementalScoreCalculator</incrementalScoreCalculatorClass>
    <!-- scoreDrl>com/ezentis/mplanner/vehiclerouting/solver/vehicleRoutingScoreRules.drl</scoreDrl-->
    <!--<assertionScoreDirectorFactory>-->
      <!--<easyScoreCalculatorClass>com.ezentis.mplanner.vehiclerouting.solver.score.VehicleRoutingEasyScoreCalculator</easyScoreCalculatorClass>-->
    <!--</assertionScoreDirectorFactory>-->
    <initializingScoreTrend>ONLY_DOWN</initializingScoreTrend>
  </scoreDirectorFactory>

  <termination>
    <minutesSpentLimit>5</minutesSpentLimit>
  </termination>
  <constructionHeuristic>
    <constructionHeuristicType>FIRST_FIT</constructionHeuristicType>
        <!--  <queuedEntityPlacer>
          <entitySelector id="placerEntitySelector">
            <entityClass>com.ezentis.mplanner.vehiclerouting.domain.Customer</entityClass>
            <cacheType>PHASE</cacheType>
            <selectionOrder>SORTED</selectionOrder>
            <sorterManner>DECREASING_DIFFICULTY</sorterManner>
          </entitySelector>
          <cartesianProductMoveSelector>
            <changeMoveSelector>
              <entitySelector mimicSelectorRef="placerEntitySelector"/>
              <valueSelector variableName="vehicleRange">
                <downcastEntityClass>com.ezentis.mplanner.vehiclerouting.domain.Vehicle</downcastEntityClass>
                <cacheType>PHASE</cacheType> -->
                <!--<selectionOrder>SORTED</selectionOrder>-->
                <!--<sorterManner>INCREASING_STRENGTH</sorterManner>-->
              <!-- </valueSelector>
            </changeMoveSelector>
            <changeMoveSelector>
              <entitySelector mimicSelectorRef="placerEntitySelector"/>
              <valueSelector variableName="resourceRange">
                <cacheType>PHASE</cacheType>
                <selectionOrder>SORTED</selectionOrder>
                <sorterManner>INCREASING_STRENGTH</sorterManner>
              </valueSelector>
            </changeMoveSelector>
          </cartesianProductMoveSelector>
        </queuedEntityPlacer> -->
    
  </constructionHeuristic>
  <localSearch>
        <unionMoveSelector>
      <changeMoveSelector>
        <entitySelector id="entitySelector1"/>
        <valueSelector>
          <nearbySelection>
            <originEntitySelector mimicSelectorRef="entitySelector1"/>
            <nearbyDistanceMeterClass>com.ezentis.mplanner.vehiclerouting.domain.solver.nearby.CustomerNearbyDistanceMeter</nearbyDistanceMeterClass>
            <parabolicDistributionSizeMaximum>40</parabolicDistributionSizeMaximum>
          </nearbySelection>
        </valueSelector>
      </changeMoveSelector>
      <swapMoveSelector>
        <entitySelector id="entitySelector2"/>
        <secondaryEntitySelector>
          <nearbySelection>
            <originEntitySelector mimicSelectorRef="entitySelector2"/>
            <nearbyDistanceMeterClass>com.ezentis.mplanner.vehiclerouting.domain.solver.nearby.CustomerNearbyDistanceMeter</nearbyDistanceMeterClass>
            <parabolicDistributionSizeMaximum>40</parabolicDistributionSizeMaximum>
          </nearbySelection>
        </secondaryEntitySelector>
      </swapMoveSelector>
      <tailChainSwapMoveSelector>
        <entitySelector id="entitySelector3"/>
        <valueSelector>
          <nearbySelection>
            <originEntitySelector mimicSelectorRef="entitySelector3"/>
            <nearbyDistanceMeterClass>com.ezentis.mplanner.vehiclerouting.domain.solver.nearby.CustomerNearbyDistanceMeter</nearbyDistanceMeterClass>
            <parabolicDistributionSizeMaximum>40</parabolicDistributionSizeMaximum>
          </nearbySelection>
        </valueSelector>
      </tailChainSwapMoveSelector>
    </unionMoveSelector>
    <acceptor>
      <lateAcceptanceSize>200</lateAcceptanceSize>
    </acceptor>
    <forager>
      <acceptedCountLimit>1</acceptedCountLimit>
    </forager>
  </localSearch>
</solver>

But when I upload the problem and start the solver, I get this error:

java.lang.IllegalStateException: Multiple EntityMimicRecorders (usually EntitySelectors) have the same id (entitySelector1).

I am really stuck with this as I'm not able to include the new Planning Variable. I have tried a lot of another code configurations, although I think this is the more clear. Any help would be really appreciated.

Answer 1

I am not sure if this will really work but when you do something like that you won't get the error.

<valueSelector variableName="variableName">

I only need the nearbySelection for the chained variable.

If you want the nearby selection for both variables you could try to have two <changeMoveSelector> with each one nearby config.