OptaPlanner中的穷举搜索不适用于非常简单的示例

我们正在尝试创建一个简单的示例来测试OptaPlanner的function。 在下文中，我们展示了我们想出的东西。 我们的例子的问题在于，当我们选择详尽的搜索算法来解决问题时，OptaPlanner会以错误的答案快速终止，即使零不是ValueRangeProvider提供的可能解决方案，也是零。 此外，在使用本地搜索时，不会在求解期间设置PlanningVariable。

我们尝试更改OptaPlanner（例如TSP）附带的示例中的算法，该算法有效。 因此我们的问题是：为什么我们的代码不起作用？

MyPlanningEntity.java：

import org.optaplanner.core.api.domain.entity.PlanningEntity; import org.optaplanner.core.api.domain.variable.PlanningVariable; @PlanningEntity public class MyPlanningEntity { @PlanningVariable(valueRangeProviderRefs = {"myListValueRangeProvider"}) private int myPlanningVariable; public int getMyPlanningVariable() { return myPlanningVariable; } public void setMyPlanningVariable(int myPlanningVariable) { this.myPlanningVariable = myPlanningVariable; } } 

MySolution.java：

 import org.optaplanner.core.api.domain.solution.PlanningEntityProperty; import org.optaplanner.core.api.domain.solution.PlanningSolution; import org.optaplanner.core.api.domain.solution.Solution; import org.optaplanner.core.api.domain.valuerange.CountableValueRange; import org.optaplanner.core.api.domain.valuerange.ValueRangeFactory; import org.optaplanner.core.api.domain.valuerange.ValueRangeProvider; import org.optaplanner.core.api.score.buildin.simple.SimpleScore; import java.util.ArrayList; import java.util.Collection; import java.util.List; @PlanningSolution public class MySolution implements Solution { @PlanningEntityProperty private MyPlanningEntity myPlanningEntity; private SimpleScore score; public MyPlanningEntity getMyPlanningEntity() { return myPlanningEntity; } public void setMyPlanningEntity(MyPlanningEntity myPlanningEntity) { this.myPlanningEntity = myPlanningEntity; } @ValueRangeProvider(id = "myListValueRangeProvider") public List getListValueRange(){ List list = new ArrayList(); list.add(1); list.add(2); list.add(3); list.add(4); return list; } @Override public SimpleScore getScore() { return score; } @Override public void setScore(SimpleScore simpleScore) { this.score = simpleScore; } @Override public Collection getProblemFacts() { return null; } } 

MyScoreCalculator.java：

 import org.optaplanner.core.api.score.Score; import org.optaplanner.core.api.score.buildin.simple.SimpleScore; import org.optaplanner.core.impl.score.director.easy.EasyScoreCalculator; public class MyScoreCalculator implements EasyScoreCalculator{ @Override public Score calculateScore(MySolution mySolution) { // The higher the input, the higher the output int value = mySolution.getMyPlanningEntity().getMyPlanningVariable(); return SimpleScore.valueOf(value); } } 

ESTest.java：

 import org.optaplanner.core.api.solver.Solver; import org.optaplanner.core.api.solver.SolverFactory; public class ESTest { public static void run(){ SolverFactory solverFactory = SolverFactory.createFromXmlResource("resources/myPlanningProblem.xml"); Solver solver = solverFactory.buildSolver(); MySolution mySolution = new MySolution(); MyPlanningEntity myPlanningEntity = new MyPlanningEntity(); mySolution.setMyPlanningEntity(myPlanningEntity); solver.solve(mySolution); MySolution bestSolution = (MySolution) solver.getBestSolution(); System.out.println("Best solution: " + bestSolution.getMyPlanningEntity().getMyPlanningVariable()); } public static void main(String args[]){ run(); } } 

myPlanningProblem.xml：

      SIMPLE MyScoreCalculator   <!----> <!--FIRST_FIT--> <!---->   BRUTE_FORCE  100    <!----> <!--HILL_CLIMBING--> <!----> <!--10--> <!----> <!---->  

我们正在使用OptaPlanner 6.3 Final。

这是OptaPlanner启动此配置时得到的结果：

 14:58:58.742 [main] INFO oocore.impl.solver.DefaultSolver - Solving started: time spent (4), best score (0), environment mode (REPRODUCIBLE), random (JDK with seed 0). 14:58:58.745 [main] INFO oocieDefaultExhaustiveSearchPhase - Exhaustive Search phase (0) ended: step total (0), time spent (7), best score (0). 14:58:58.745 [main] INFO oocore.impl.solver.DefaultSolver - Solving ended: time spent (7), best score (0), average calculate count per second (285), environment mode (REPRODUCIBLE). Best solution: 0 Process finished with exit code 0 

Answer 1

计划变量应该是Integer ，而不是int 。 它应该从null开始。 如果它从0开始，则OptaPlanner假设它已经初始化并且 – 默认情况下 – 不会在CH或ES中重新初始化该变量。

也许我们应该禁止原始类型来规划变量？