Op 19-01-13 21:08, Michiel Vermandel schreef:

Hi,

I am still struggling to find why my simple unit test cannot be solved to a zero score solution.

It is easily to see the solution on sight and if I feed it with the prepared solution (in a custom solver phase) it "finds" the optimal solution right away.

If you can easily see the solution on sight, you should also be able to easily see which move it should do to reach that optimal solution.
What does logging with level TRACE print? Can you find the move it should do in that log? What score does the log say that move has?

I'm trying everything and try to review everything I have written.

It is during that review that I noticed that the equals and hashcode methods of my solution implementation class are never called.

Obviously the solutionEquals and solutionHashCode methods of my planning entity are never called either.

solutionEquals/HashCode is only called with <solutionTabuSize>, which is worthless when scaling out (unlike entityTabuSize).
A solution's equals/hashCode is never called.

<entityTabuSize> should be calling the planning entity's equals/hashcode, at least in Planner 5.5-.
For Planner 6.0 I am looking into stop relying on the entity's equals/hashcode, in case users have overwritten the default java.lang.Object behavior in a way that's incompatible for Planner.

What should I conclude out of that?

Is this a crucial issue? If so, what should I check/change?

I am running Drools Planner 5.5.0.Final on java 1.7.0 on a Windows 7 64bit machine.

Thanks,

Michiel Vermandel

-----------------
http://www.codessentials.com - Your essential software, for free!
Follow us at http://twitter.com/#!/Codessentials
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users