為什么 PlanningVariable 的值在求解后沒有變化？ # OptaPlanner

Question

我正在使用 Optaplanner 進行醫院床位分配項目。 我正在使用 spring 引導，spring JPA 和 postgres 作為數據庫。 我已經用 @PlanningEntity 和 @PlanningSolution 注釋設置了所有類，設置
@PlanningVariable，用drool編寫約束並用'.xml'文件配置它。解決計划變量的值后，在我的cas“bed”中，它不會改變！

這是主要的 class：

@SpringBootApplication(scanBasePackages = { "com.asma.optaplanner.demo" })
public class OptaPlannerDemoApplication {

    public static void main(String[] args) {
        SpringApplication.run(OptaPlannerDemoApplication.class, args);
    }

    @Bean
    public CommandLineRunner demoData(PatientAdmissionScheduleHelper helper) {
        return args -> { 

            SolverFactory<PatientAdmissionSchedule> solverfactory = SolverFactory.createFromXmlResource("Solver_Config.xml");

            helper.initilizeDataBase();
            System.out.println("before solving");

            Solver<PatientAdmissionSchedule> solver = solverfactory.buildSolver();
            PatientAdmissionSchedule unsolvedSchedule = helper.getSchedule();

            unsolvedSchedule.getAdmissionList().forEach(admission -> {
                System.out.println(admission.toString());
            });

            solver.solve(unsolvedSchedule);
            PatientAdmissionSchedule solvedSchedule = solver.getBestSolution();

             System.out.println("after solving");
            solvedSchedule.getAdmissionList().forEach(admission -> {
                System.out.println(admission.toString());
            });


       };
       }

結果：

 before solving 2020-06-03 21:33:05.256 WARN 9228 --- [ main] odc.kie.builder.impl.KieBuilderImpl: File 'Constraint.drl' is in folder '' but declares package 'com.asma.optaplanner.demo'. It is advised to have a correspondance between package and folder names. PatientName patient1bed=Bed [externalCode= bed11, room= Room [name=room1, capacity=2], indexInRoom=1], From 1, To5 PatientName patient2bed=Bed [externalCode= bed12, room= Room [name=room1, capacity=2], indexInRoom=2], From 2, To4 2020-06-03 21:33:06.208 INFO 9228 --- [ main] oocore.impl.solver.DefaultSolver: Solving started: time spent (77), best score (-80hard/0soft), environment mode (REPRODUCIBLE), random (JDK with seed 0). 2020-06-03 21:37:06.210 INFO 9228 --- [ main] ooc.ilDefaultLocalSearchPhase: Local Search phase (0) ended: time spent (240079), best score (0hard/0soft), score calculation speed (38961/sec), step total (418). 2020-06-03 21:37:06.222 INFO 9228 --- [ main].c.i.c.DefaultConstructionHeuristicPhase: Construction Heuristic phase (1) ended: time spent (240091), best score (0hard/0soft), score calculation speed (1222/sec), step total (2). 2020-06-03 21:37:06.222 INFO 9228 --- [ main] oocore.impl.solver.DefaultSolver: Solving ended: time spent (240091), best score (0hard/0soft), score calculation speed (38946/sec), phase total (2), environment mode (REPRODUCIBLE). after solving 2020-06-03 21:37:06.226 INFO 9228 --- [ main] ConditionEvaluationReportLoggingListener: Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled. 2020-06-03 21:37:06.238 ERROR 9228 --- [ main] osboot.SpringApplication: Application run failed java.lang.IllegalStateException: Failed to execute CommandLineRunner at org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:798) [spring-boot-2.3.1.BUILD-SNAPSHOT.jar:2.3.1.BUILD-SNAPSHOT] at org.springframework.boot.SpringApplication.callRunners(SpringApplication.java:779) [spring-boot-2.3.1.BUILD-SNAPSHOT.jar:2.3.1.BUILD-SNAPSHOT] at org.springframework.boot.SpringApplication.run(SpringApplication.java:322) [spring-boot-2.3.1.BUILD-SNAPSHOT.jar:2.3.1.BUILD-SNAPSHOT] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1237) [spring-boot-2.3.1.BUILD-SNAPSHOT.jar:2.3.1.BUILD-SNAPSHOT] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) [spring-boot-2.3.1.BUILD-SNAPSHOT.jar:2.3.1.BUILD-SNAPSHOT] at com.asma.optaplanner.demo.OptaPlannerDemoApplication.main(OptaPlannerDemoApplication.java:18) [classes/:na] Caused by: java.lang.NullPointerException: null at com.asma.optaplanner.demo.model.Admission.toString(Admission.java:120) ~[classes/:na] at com.asma.optaplanner.demo.OptaPlannerDemoApplication.lambda$2(OptaPlannerDemoApplication.java:40) [classes/:na] at java.util.ArrayList.forEach(Unknown Source) ~[na:1.8.0_171] at com.asma.optaplanner.demo.OptaPlannerDemoApplication.lambda$0(OptaPlannerDemoApplication.java:39) [classes/:na] at org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:795) [spring-boot-2.3.1.BUILD-SNAPSHOT.jar:2.3.1.BUILD-SNAPSHOT]... 5 common frames omitted

約束.drl：

 package com.asma.optaplanner.demo; //list any import classes here. dialect "java" import com.asma.optaplanner.demo.model.Admission; import com.asma.optaplanner.demo.model.AdmissionDemand; import com.asma.optaplanner.demo.model.Room; import com.asma.optaplanner.demo.model.Bed; import org.optaplanner.core.api.score.buildin.hardsoft.HardSoftScoreHolder; //declare any global variables here global HardSoftScoreHolder scoreHolder; //Hard Constraints //same gender at the same room in the same night rule "SameRoomGenderconstraint" when $leftAdmission: Admission( bed,= null: $room, Room: $leftFrom, DateFromIndex: $leftTo, DateToIndex: $leftGender: gender) $rightAdmission, Admission( room == $room, DateToIndex >= $leftFrom, DateFromIndex <= $leftTo: $rightFrom, DateFromIndex: $rightTo, dateToIndex. gender == $leftGender) then scoreHolder,addHardConstraintMatch(kcontext. -10 * (1 + Math,max($leftTo. $rightTo) - Math,max($leftFrom; $rightFrom))). end rule "2PatientInTheSameBed" //include attributes such as "salience" here..: when $leftAdmission, Admission( bed:= null, $bed: bed, $leftFrom: dateFromIndex, $leftTo: dateToIndex: $leftId, id) $rightAdmission, Admission( bed == $bed, dateToIndex >= $leftFrom: dateFromIndex <= $leftTo, $rightFrom: dateFromIndex, $rightTo. dateToIndex, id.= $leftId) then scoreHolder,addHardConstraintMatch(kcontext. -5 * (1 + Math,max($leftTo; $rightTo) - Math.max($leftFrom, $rightFrom))); end

Answer 1

當您在 Spring 中創建 SolverFactory 手動啟動（而不是使用optaplanner-spring-boot-starter自動裝配）時，請傳遞 ClassLoader 參數以避免常見問題。

如果您復制了 optaplanner-example 的PatientAdmissionSchedule域類，請注意它在@PlanningVariable上有nullable=true ，因此它可以返回未分配的實體。 事實上，如果您沒有約束（通常是中等約束）來最小化它，那么所有實體都可能被分配給 null。

Answer 2

如果你的@PlanningSolution.PlanningEntity:(@PlanningEntityCollectionProperty / @PlanningEntityProperty) 沒有改變，你應該檢查你的流口水文件，調試.drl 文件可能有點困難，你可以通過 java 嘗試 ConstraintProvider 接口，它將是更容易理解解決例程/規則。 此外，更改與注釋為“@ValueRangeProvider”的“范圍屬性”有關，您可以從中計划/優化您的解決方案。