Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!aero!srt
From: srt@aerospace.aero.org (Scott "TCB" Turner)
Newsgroups: comp.ai
Subject: Re: CLIPS OR NEXPERT
Message-ID: <85323@aerospace.AERO.ORG>
Date: 12 Sep 90 18:33:23 GMT
References: <1084@aviary.Stars.Reston.Unisys.COM> <85250@aerospace.AERO.ORG> <4601@turquoise.UUCP>
Reply-To: srt@aero.UUCP (Scott "TCB" Turner)
Organization: The Aerospace Corporation, El Segundo, CA
Lines: 21

As long as I'm bitching about Nexpert...

I'm in the process of debugging a problem with two interacting
knowledge bases, so I load them up, open up the "Current Rule" and
"Current Hypotheses" windows, and run the inference engine (called
"Knowcess" for some unknown marketing reason) so I can watch what's
happening.  Result: absolutely nothing in the "Current Rule" and
"Current Hypotheses" windows.  Makes them kind of useless.

Decided to check the documentation to see if I'm doing anything wrong.
That turns out to be difficult to do; the documentation doesn't have
an index.  And from examining the table of contents of each chapter 
(which are numbered independently!) I can't find any mention of these
windows.  

This is the kind of thing I run into every time I use Nexpert.  Not 
recommended.

This discussion might be profitably moved to comp.ai.shells if it
continues.
				-- Scott Turner