Op 14-01-13 13:08, Michiel Vermandel schreef:

Hi,

I wrote a quite simple unit test which I expected to succeed.

But it does not, it ends with a negative score.

Enable logging trace (logging != environmentMode) and check if you can see the moves that it should take and why it doesn't take them.
A very small problem can't work with entityTabuSize 7 for example.
There are some idea's to auto-tweak the entityTabuSize or at least automatically lower it if there are too little entities.
Feel free to make an issue about this.

Though, it is easy to see on sight that there is a zero-score solution possible.

So... something must be wrong in some of my rules.

I was wondering if it is possible to manually set all planning variables to what I expected them to be and then see which rule(s) break(s)?

Yes, see Solver.getScoreDirectorFactory (see docs).

So planning variables should not be changed anymore while solving.

I'm using drools planner 5.5.0.Final.

Thanks,

Michiel

-----------------
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