I've seen the recommendations on when to use a rule base system (RBS) (re.
thread "JESS: Need of a Rule Based System!!!" started by Sachin and the thread
"JESS: Data constraint management " started by Robert Quillen.) I wonder,
though, about when you have a REALLY big system. I am now working
Certainly the COLLECTING of the transaction information is simple and easy.
That doesn't necessarily need an expert system. But the PROCESSING of the
transactions once collected is complex. We deal mostly with hospitals, so there
are issues of shift differentials, overtime, bonuses, etc. And
Thomas,
I'm curious to know about the system you developed. How complex it is and the
approximate performance of that system?
Approximately how many facts/rules are there? What type of computing boxes are
you using? How many rules are applied against how many facts at any given
time? How
Please forgive me if this is a misguided missive. I am trying to understand how
to use a rule based system, and as such I am sure I am operating under many
misunderstandings and misconceptions. I am trying to clear them up, and I would
appreciate any corrections to my thoughts below.
I have p
I'm trying to figure out the best way to handle this situation.
My program has two "modes". In the first, the program collects "instructions",
and in the second, the instructions are "processed". Now the program shouldn't
go into the second mode until all the instructions are received. There
I've got a question about when things happen in JESS.
If I have a rule that asserts two facts, does the engine go see if any other
rules fire after the first assertion or after both assertions?
For example, if I have
(deffacts base-facts
(a (value true))
(b (value true))
(c (va
> I think Michael McConnell wrote:
>
>> Jess> (batch AVIS\\avis-proto.clp)
>> Jess reported an error in routine ValueVector.get
>> while executing (batch
>> AVIS\avis-rules-proto-rules.clp)
>> while executing (batch AVIS\avis-proto.clp).
>> Message: Bad index -3 in call to get
