This rule fires:
(defrule count-icd9-codes-in-a-group-for-zip
(declare (salience 5))
(granularity
(gran "ZIP"))
(ICD9_COUNTING_GROUP
(id ?id)
(codes $?codes))
?factV <- (ICD9_CODE (ICD91 ?code))
(test (neq (member$ ?factV $?codes) FALSE))
(analysis_wi
Interesting.. I definately am finding cases where I have rules that
have all their conditions met on the LHS.. there is NOTHING for the
accumulate part to match on.. and the rule doesn't fire heh.
I'll try to find a concrete example with some facts I can display
etc. Basically if I add 'junk' to
All pattern-matching has to be driven by *some* change to working
memory. A few CEs (not, test, accumulate) can pass when they match no
facts at all. Therefore, these CEs need a little help to know when to
fire. If any of them appear first on the LHS of a rule, Jess inserts a
pattern "(initial-fact
Yes, that's how you
can sweep a lot of data of different type together in one rule. The rule still
fires of some types are not present.
Martijn
From:
Roger Studner [mailto:[EMAIL PROTECTED]
Sent: vrijdag 2 december 2005
13:19
To: jess-users@sandia.gov
Subject: JESS: Accumul
