I think that this discussion about salience may be related to other post

Re: JESS: Using a rule engine for plan recognition

if you need to change order of rule firing you may establish control facts that would trigger or de-trigger executions.

Dusan Sormaz

At 10:25 AM 1/13/2006, you wrote:
I think Yura wrote:
[Charset koi8-r unsupported, filtering to ASCII...]
> > (set-salience-evaluation every-cycle)
> I think that would be really slow.

Only if the agenda is large, but yes, it could slow things down.

> However the problem is quite common, so probably we may use some
> Java API to reevaluate the salience just once. The question is which
> one.

The problem is that if you reevaluate the salience of a single
activated rule, then the whole agenda has to be recomputed. You
actually wouldn't gain much, assuming these salience changes were

An alternative to every-cycle is when-activated, which will evaluate
the salience of a rule each time that rule is placed on the
agenda. Thus salience changes will affect new firings, but not
activations that existed before the change. This might be just fine.

Ernest Friedman-Hill 
Advanced Software Research          Phone: (925) 294-2154
Sandia National Labs                FAX:   (925) 294-2234
PO Box 969, MS 9012                 [EMAIL PROTECTED]
Livermore, CA 94550         http://herzberg.ca.sandia.gov

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]

* Dušan Šormaz, PhD, Associate Professor                     
* Ohio University
* Industrial and Manufacturing Systems Engineering Department
* 277 Stocker Center, Athens, OH 45701-2979
* phone: (740) 593-1545
* fax:   (740) 593-0778 
* url: http://www.ent.ohiou.edu/~sormaz

Reply via email to