If you double-click a join node in the "view" display, it shows you
the contents of both memories in that node; in theory, this is
equivalent to the information you're looking for, if not so
convenient. The (matches) command give out this same information. Both
(matches) and (view) get their information from Node2.displayMemory(),
so that would be one place to look. But be warned that using
package-protected interfaces to get at the contents of the Rete nodes
is dangerous business, as things do change quite a bit between
releases -- both the interfaces and the data representation may
change.

The only public interface to what happens inside the Rete network is
an event-based one. Every jess.Node object support JessListeners. You
can add a JessListener to a node and it will send you an event
whenever a token is delivered to it. Unfortunately there's no publi
API for getting the nodes in a rule; but cheating and using
HasLHS.getNodes() should be pretty safe.


I think Steve Webster wrote:
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> All,
> 
> I'm interested in writing a utility that's similar to the (view) command,
> with a bit of a twist. I'm interested understanding which predicates are
> matched, failing a rule activitation. However, I'm having difficulty
> understanding where to instrument the Rete network in order to trap these
> partial matches. Any approaches to this problem would be greatly
> appreciated.
> 
> Much obliged,
> Steve
> 


---------------------------------------------------------
Ernest Friedman-Hill  
Distributed Systems Research        Phone: (925) 294-2154
Sandia National Labs                FAX:   (925) 294-2234
Org. 8920, MS 9012                  [EMAIL PROTECTED]
PO Box 969                  http://herzberg.ca.sandia.gov
Livermore, CA 94550

--------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use your own address!) List problems? Notify [EMAIL PROTECTED]
--------------------------------------------------------------------

Reply via email to