[
https://issues.jboss.org/browse/JBRULES-3577?page=com.atlassian.jira.plug...
]
Geoffrey De Smet edited comment on JBRULES-3577 at 7/13/12 3:09 AM:
--------------------------------------------------------------------
It needs to be fixed on an architectural level:
maybe each Score should have an unitialized entity count which counts as a higher score
level (harder than hard).
Planner must manage that unitialized entity count itself, it shouldn't force the users
to deal with that.
was (Author: ge0ffrey):
It needs to be fixed on an architectural level:
maybe each Score should have an unitialized entity count which counts as a higher score
level (harder than hard).
Planner must managed that unitialized entity count itself, it shouldn't force the
users to deal with that.
A custom phase which initializes the solution but doesn't provide
a better solution than the original should not get reverted
-----------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-3577
URL:
https://issues.jboss.org/browse/JBRULES-3577
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-planner
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
DefaultSolver.runSolverPhases() will go through each phase, and will revert
the changes if they're not better. Or, more exactly, here are lines 191-193:
if (it.hasNext()) {
// solverScope.setWorkingSolutionFromBestSolution();
}
Now, if this involved setting the planning variables for the first time,
those will be reverted.
--
View this message in context:
http://drools.46999.n3.nabble.com/Planner-Initialized-solution-local-sear...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira