Hello, 

 Thanks for your quick response yesterday.  I have implemented the
patches you directed me to, but have run into some new (I believe
related) problems.

Once again, this rule seems to cause the problems

(defrule done-task  
 (declare (salience -2))  
 ?f <- (task (list ? $?rest))  
 =>  (modify ?f (list $?rest)) 
 ) 

 I think a trace of what happens when this rule fires with the same code
in version 4.44 compared to a trace of what happens with 5.0a5 would be
the best way to explain the problem.

Here it is in version 4.4 

FIRE [Defrule: done-task ; 1 patterns; salience: -2] f-283 <==  (task
(patient 14173) (visit 14285) (posture 14286) (menu 14287)(list
construct-menu check-counterindications output))
==> Activation: done-task :  f-300
==> Activation: twist-counterindicated-by-severe-elevation : 
f-300,f-296, f-167, f-245 
==> (task (patient 14173) (visit 14285) (posture 14286) (menu
14287)(list check-counterindications output))

;;; other rules fire

FIRE [Defrule: done-task ; 1 patterns; salience: -2] f-300 
<==  (task (patient 14173) (visit 14285) (posture 14286) (menu
14287)(list check-counterindications output))
==> Activation: done-task :  f-302==> Activation: output-routines : 
f-302 
==> (task (patient 14173) (visit 14285) (posture 14286) (menu
14287)(list output))

;;; other rules fire

FIRE [Defrule: done-task ; 1 patterns; salience: -2] f-302 
<==  (task (patient 14173) (visit 14285) (posture 14286) (menu
14287)(list output)) 
==> (task (patient 14173) (visit 14285) (posture 14286) (menu
14287)(list ))
TRUE
Jess> 

Now, this is what happens with version 5.0 a5

FIRE 98 done-task f-289
<== f-298 (task(patient 14173)(visit 14285)(posture 14286)(menu
14287)(list construct-menu check-counterindications output))
==> f-341 (task(patient 14173)(visit 14285)(posture 14286)(menu
14287)(list check-counterindications output))==> Activation: done-task :
f-341

;;; no other rules fire

FIRE 99 done-task f-341
<== f-341 (task(patient 14173)(visit 14285)(posture 14286)(menu
14287)(list check-counterindications output))
==> f-342 (task(patient 14173)(visit 14285)(posture 14286)(menu
14287)(list output))
==> Activation: done-task: f-342

;;; no other rules fire 
FIRE 100 done-task f-342
<== f-342 (task(patient 14173)(visit 14285)(posture 14286)(menu
14287)(list output))
==> f-343 (task(patient 14173)(visit 14285)(posture 14286)(menu
14287)(list))
==> Activation: done-task: f-343

FIRE 101 done-task f-342
<== f-343 (task(patient 14173)(visit 14285)(posture 14286)(menu
14287)(list))
==> f-344 (task(patient 14173)(visit 14285)(posture 14286)(menu
14287)(list))
==> Activation: done-task: f-344

FIRE 102 done-task f-343
<== f-344 (task(patient 14173)(visit 14285)(posture 14286)(menu
14287)(list))
==> f-345 (task(patient 14173)(visit 14285)(posture 14286)(menu
14287)(list))
==> Activation: done-task: f-345

into an endless loop.

Any input on this problem would be much appreciated

Thanks,

Benjamin Good
True Image Inc.
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list (use your own address!) List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------

Reply via email to