|
All
jess commands have an equilvalent java command. For run-until-halt,
simply call the Rete method runUntilHalt(). I am by far no expert
but I think you might have to write your rules differently to handle
conflicts.
Greetings,
I have only been using JESS for a month or so and
I have successfully get it to run with a simple example using Java(which reads
from .clp files and get executed to obtain the results).
Here come my questions:
(1)
What I have done was some how a "one-shot"
process. How do I get the engine to run continuously and reacts to changes in
the knowledge info(or rules) to generate new results? In other
words, I want the engine to "monitor" a set of variables and fire rules
when the values of those variables have changed.
I understand there is "run-until-halt". How do
I use it in my Java code to do what I wanted.
(2)
How do I resolve conflicting rules? In
a system with hundreds of rules, there is a chance that some rules might
result in a conflicting decision. How do I deal with this possibility in JESS?
Do I have to create other rules to deal with this? or do I use
"set-salience-evaluation" for the rules? How do I keep track of all the rules
to see that(conflict)?
I would appreciate if anyone can help me out or
point me to other resources that could.
Thanks a lot.
Guu
|
