Or, just a thought, you could use a goal-oriented approach such that
the first CE of the rule is a Goal object with a Name, usually a
literal equal to a integer for speed considerations and to avoid the
String.equals(String) method. All of the rules having to do with one
stage would ask "if th
I think that Ross Judson said:
>> There are a couple of additional techniques you can use to control rule
firing order.
FYI - There are two more ways:
1. Flip the order in which Jess fires facts on the agenda (first activated
= first to fire) by using the (set-strategy breadth) command -- a depth
There are a couple of additional techniques you can use to control rule
firing order. The main one is introducing additional "state" facts into
the fact base; another is using modules. A very crude example is:
(deftemplate state (slot current))
(assert (state (current 0)))
In your MAIN module
PROTECTED]
CC:
Onderwerp: JESS: hi All
Hi All
Is there a way to control the rule firing order with out using salience?
I have three rules checking three different conditions on the same set of
facts. The order in which the rules
PROTECTED]On Behalf Of
SubrahmanyamSent: Monday, August 11, 2003 5:46 AMTo:
[EMAIL PROTECTED]Subject: JESS: hi All
Hi
All
Is there a way to control the rule
firing order with out using salience?
I have three rules checking three
different conditions on the same set of facts.
Hi All
Is there a way to control the rule firing order with out
using salience?
I have three rules checking three different conditions on
the same set of facts. The order in which the rules fire is important(rule1
, then 2 then 3). Can this be achieved with out using salience?
Than
