2011/10/14 Geoffrey De Smet
> **
> In your doMove you're doing:
>
> crew.addActivity(activity);
> remainingActivities.remove(activity);
>
> If crew and/or remainingActivities are used by your score rules, the
> working memory should be notified of their changes.
> That's causing the corruption
>
In your doMove you're doing:
crew.addActivity(activity);
remainingActivities.remove(activity);
If crew and/or remainingActivities are used by your score rules, the
working memory should be notified of their changes.
That's causing the corruption
Extra advice:
I think you're making your moves
2011/10/14 Geoffrey De Smet
> **
> Probably you forgot to notify the workingMemory.update in the doMove
> method:
>
> public void doMove(WorkingMemory workingMemory) {
> FactHandle factHandle = workingMemory.getFactHandle(activity);
> activity.setAssignee(...);
> worki
Probably you forgot to notify the workingMemory.update in the doMove method:
public void doMove(WorkingMemory workingMemory) {
FactHandle factHandle = workingMemory.getFactHandle(activity);
activity.setAssignee(...);
workingMemory.update(factHandle, activity);
}
O
A corrupted score normally indicates a problem with the Move
implementation (or sometimes the score drl).
Basically this happened: for a number of moves, it did the move,
calculated the score and undo the move.
One of those move was associated with a score -10hard/0soft, that was
the best one.
Hi,
I've implemented a very simple application using drools planner consisting
of a bunch of activities. My rule file is very simple too and just counts
the number of activities not assigned. When I run Solver.solve(), I get the
following error message:
Exception in thread "AWT-EventQueue-0" java
