<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
In your doMove you're doing:<br>
<br>
crew.<span class="me1">addActivity</span><span class="br0">(</span>activity<span
class="br0">)</span>;<br>
remainingActivities.<span class="me1">remove</span><span class="br0">(</span>activity<span
class="br0">)</span>;<br>
<br>
If crew and/or remainingActivities are used by your score rules, the
working memory should be notified of their changes.<br>
That's causing the corruption<br>
<br>
<br>
Extra advice:<br>
I think you're making your moves too complex and your domain model
too complex.<br>
If you upgrade to 5.3, it will be hard to identify the planning
entities. There will be many (and I doubt you need more than 1).<br>
Read<br>
<a class="moz-txt-link-freetext" href="http://docs.jboss.org/drools/release/5.3.0.CR1/drools-planner-docs/html_single/index.html#d0e1411">http://docs.jboss.org/drools/release/5.3.0.CR1/drools-planner-docs/html_single/index.html#d0e1411</a><br>
and specificly this note in that chapter:<br>
<blockquote type="cite">
<p><span class="emphasis"><a id="d0e1519"><em>Do not create
unnecessary planning entity classes.</em></a></span><a
id="d0e1519"> This leads to difficult <code class="literal">Move</code>
implementations and slower score calculation.</a></p>
<p><a id="d0e1519">For example, do not create a planning entity
class to hold the total free time of a teacher, which needs to
be kept up to date as the <code class="literal">Lecture</code>
planning entities change. Instead, calculate the free time in
the score constraints and put the result per teacher into a
logically inserted score object.</a></p>
<p><a id="d0e1519">If historic data needs to be considered too,
then create problem fact to hold the historic data up to, but
<span class="emphasis"><em>not including</em></span>, the
planning window (so it doesn't change when a planning entity
changes) and let the score constraints take it into account.</a></p>
</blockquote>
<br>
<br>
<br>
Op 14-10-11 15:48, Guilherme Kunigami schreef:
<blockquote
cite="mid:CAK0MeX5OM3jdSphoQy7ZG3fEexkMJADKw4-bnCLeJBA5-hA9SQ@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">2011/10/14 Geoffrey De Smet <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:ge0ffrey.spam@gmail.com">ge0ffrey.spam@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff"> Probably you forgot to
notify the workingMemory.update in the doMove method:<br>
<br>
public void doMove(WorkingMemory workingMemory) {<br>
FactHandle factHandle =
workingMemory.getFactHandle(activity);<br>
activity.setAssignee(...);<br>
workingMemory.update(factHandle, activity);<br>
}<br>
<br>
Op 14-10-11 09:21, Geoffrey De Smet schreef:
<div>
<div class="h5">
<blockquote type="cite"> A corrupted score normally
indicates a problem with the Move implementation (or
sometimes the score drl).<br>
<br>
Basically this happened: for a number of moves, it did
the move, calculated the score and undo the move.<br>
One of those move was associated with a score
-10hard/0soft, that was the best one.<br>
Now, it does that move (which is now called the
"step") and when it calculates the score it's a
different score 0hard/0soft.<br>
<br>
Try TRACE environment and see if it crashes sooner.
Copy paste your Move implementation here.<br>
</blockquote>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Using the TRACE environment gave the same results of DEBUG.</div>
<div><br>
</div>
<div>Here's my move implementation, as well as the snipet of
drools rule file that calculates the score based on remaining
activities:</div>
<div> </div>
<div><a moz-do-not-send="true"
href="http://pastebin.mozilla.org/1355014">http://pastebin.mozilla.org/1355014</a></div>
<div> </div>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff">
<div>
<div class="h5">
<blockquote type="cite"> In Planner 5.4 there will be 2
out-of-the-box Move implementations to use, so writing
Move's become optional.<br>
</blockquote>
</div>
</div>
</div>
</blockquote>
<div>Cool!</div>
<div><br>
</div>
<div>By the way, I'm using Drools 5.2.0 final.</div>
<div><br>
</div>
<div>Thanks,</div>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff">
<div>
<div class="h5">
<blockquote type="cite"> <br>
Op <a moz-do-not-send="true" href="tel:13-10-11%2016"
value="+13101116" target="_blank">13-10-11 16</a>:37,
Guilherme Kunigami schreef:
<blockquote type="cite">
<div>Hi,</div>
<div><br>
</div>
<div>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:</div>
<div><br>
</div>
<div><font face="'courier new', monospace">Exception
in thread "AWT-EventQueue-0"
java.lang.IllegalStateException: The
presumedScore (-10hard/0soft) is corrupted
because it is not the realScore (0hard/0soft).</font></div>
<div><font face="'courier new', monospace"><br>
</font></div>
<div><font face="'courier new', monospace">Presumed
workingMemory:</font></div>
<div><font face="'courier new', monospace"> Score
rule (remainingActivitiesCount) has count (1)
and weight total (11).</font></div>
<div><font face="'courier new', monospace">Real
workingMemory:</font></div>
<div><font face="'courier new', monospace"> Score
rule (remainingActivitiesCount) has count (1)
and weight total (0).</font></div>
<div><font face="'courier new', monospace"><br>
</font></div>
<div><font face="arial, helvetica, sans-serif">I've
tracked down this message and found this piece
of code
@DefaultLocalSearchSolver.solveImplementation():</font></div>
<div><font face="'courier new', monospace"><br>
</font></div>
<div>
<div style="font-family: 'courier new',monospace;">
<div>// there is no need to recalculate the
score, but we still need to set it</div>
<div>localSearchSolverScope.getWorkingSolution().setScore(localSearchStepScope.getScore());</div>
<div>if (assertStepScoreIsUncorrupted) {</div>
<div>
localSearchSolverScope.assertWorkingScore(localSearchStepScope.getScore());</div>
<div>}</div>
</div>
<div style="font-family: 'courier new',monospace;"><br>
</div>
<div><font face="arial, helvetica, sans-serif">It
seems that the working score is never updated
along the algorithm, but the score in the
working memory changes. Thus, when we use the
DEBUG environment,
assertStepScoreIsUncorrupted is turned on and
the assertion fails. </font></div>
</div>
<div><font face="arial, helvetica, sans-serif"><br>
</font></div>
<div><font face="arial, helvetica, sans-serif">Should
the score be updated or am I using the library
incorrectly?</font></div>
<div><font face="arial, helvetica, sans-serif"><br>
</font></div>
<div><font face="arial, helvetica, sans-serif">Thanks,</font></div>
<pre><fieldset></fieldset>
_______________________________________________
rules-users mailing list
<a moz-do-not-send="true" href="mailto:rules-users@lists.jboss.org" target="_blank">rules-users@lists.jboss.org</a>
<a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a>
</pre>
</blockquote>
<br>
<pre cols="72">--
With kind regards,
Geoffrey De Smet</pre>
<pre><fieldset></fieldset>
_______________________________________________
rules-users mailing list
<a moz-do-not-send="true" href="mailto:rules-users@lists.jboss.org" target="_blank">rules-users@lists.jboss.org</a>
<a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a>
</pre>
</blockquote>
<br>
<pre cols="72">--
With kind regards,
Geoffrey De Smet</pre>
</div>
</div>
</div>
<br>
_______________________________________________<br>
rules-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/rules-users"
target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
<br>
</blockquote>
</div>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
rules-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
With kind regards,
Geoffrey De Smet</pre>
</body>
</html>