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

【问题标题】：Adding new Planning Variable to the Vehicle Routing Problem向车辆路径问题添加新的规划变量
【发布时间】：2020-08-25 20:19:11
【问题描述】：

我正在尝试向车辆路线问题添加一个新变量，以表示一辆载人的车辆（公共汽车）并让他们在符合某些事实的位置（这些资源必须每个人服务一个客户）。我创建了一个名为 Resource 的新类并在 Customer 类中声明了一个新的资源变量，因此当进行新的移动时，我希望求解器从列表中选择一个新的客户到车辆（路线）和一个资源（其中最终也将在车辆中）。在 Customer.java 中：

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

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

在 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;
}

最后我对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>

但是当我上传问题并启动求解器时，我得到了这个错误：

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

我真的坚持这一点，因为我无法包含新的计划变量。我已经尝试了很多其他代码配置，尽管我认为这更清楚。任何帮助将不胜感激。

【问题讨论】：

标签： optaplanner

【解决方案1】：

我不确定这是否真的有效，但是当您执行类似操作时，您不会收到错误消息。

<valueSelector variableName="variableName">

我只需要链式变量的附近选择。

如果您想要两个变量的附近选择，您可以尝试使用两个 <changeMoveSelector> 和每个附近的配置。

【讨论】：