I'm finding that opening a Jess .clp file that has errors (e.g., it doesn't
find a (requires*.) file, or there is no template defined for a rule
trigger) causes Eclipse to freeze. This only happens if I use the Jess
editor-I can open the .clp file in Eclipse by right clicking on it and
choosing to
Debasish,
If you want to create an explicit template, it should look like this:
(deftemplate MAIN::opposite-of
(slot entity-A)
(slot entity-B))
Then the facts would be declared as:
(opposite-of (entity-A shore-1) (entity-B shore-2))
However, you'd also have to assert
Jess is a rule language whose basic mechanism is pattern matching, which
binds pattern variables to constants. If you have a fact of the form
(person (name Fred) (age 22))
then you can issue a query of the form
(person (name ?name) (age ?age))
and it will bind ?name to Fred and ?age to 22 (if
Derek,
The year is young, but this may be a contender for Most Open Ended Question
of 2011. As a first step, you'll need to define your Jess data structures.
Assuming that you'll be pulling employee data from an RDBMS, you'll probably
want to start with the relevant schema from there. Then
I’m using Jess on a large DARPA project, and I find it to be a mature and
stable platform. The mailing list goes quiet but responds quickly when people
ask questions. The Jess language is a subset of LISP, which is an obvious
touchpoint for religious debates, so if you’re looking for a “reason”
If truth maintenance is a central part of your architecture, I recommend
Building Problem Solvers, by Kenneth Forbus and Johan de Kleer. It's on
Amazon:
http://www.amazon.com/Building-Problem-Solvers-Artificial-Intelligence/dp/02
62061570/ref=sr_1_1?ie=UTF8qid=1307815663sr=8-1
and you can find
In this situation, you might want to investigate the use of the logical
conditional element to link dependent objects in your game state. Taking
the example from the Jess manual on page 42, you assert that (water-flowing)
is dependent on (faucet-open). Then if you assert or retract (faucet-open)
