-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
6.1.0.CR1
-
None
-
Code zip can be found in the 3rd post here: http://drools.46999.n3.nabble.com/Strange-behaviour-with-maximumSecondsSpend-termination-in-combination-with-PlanningVariableListener-td4030128.html#a4030135
Run the Unittest class "AgendaTest" method "public void differentObservationSize()". With either the first or the 2nd termination configuration in the solverConfig.xml
There is file generated "visualisation.html" in the project map, open it in your browser.
If ran with "scoreAttained" as termination it never shows a M in the lowest row in the "visualisation.html". However if you run it with the "maximumSecondsSpend" termination it sometimes
shows an M in the lowest row.(background)
This should not be possible since this means that the period is planned without an appointment assigned to it. The variableListener solves this but appearently not with maximumSecondsSpend.Code zip can be found in the 3rd post here: http://drools.46999.n3.nabble.com/Strange-behaviour-with-maximumSecondsSpend-termination-in-combination-with-PlanningVariableListener-td4030128.html#a4030135 Run the Unittest class "AgendaTest" method "public void differentObservationSize()". With either the first or the 2nd termination configuration in the solverConfig.xml There is file generated "visualisation.html" in the project map, open it in your browser. If ran with "scoreAttained" as termination it never shows a M in the lowest row in the "visualisation.html". However if you run it with the "maximumSecondsSpend" termination it sometimes shows an M in the lowest row. (background) This should not be possible since this means that the period is planned without an appointment assigned to it. The variableListener solves this but appearently not with maximumSecondsSpend.
<termination>
<scoreAttained>0hard/-2soft</scoreAttained>
</termination>
</termination>
<maximumSecondsSpend>5</maximumSecondsSpend>
<termination>
The 2nd of the above 2 terminations does not always fire the PlanningVariableListener as opposed to the 1st termination which always gives me fires the listener and thus gives me a valid solution.
