Note that in the RHS of any rule you can use
   kcontext.getRule().getName()
and
   kcontext.getMatch().getObjects()
to explain which rules were fired with which match objects.


On 04-10-13 10:49, Esteban Aliverti wrote:
Let me add that you can also use a custom AgendaEventListener to keep track of all the rules that were executed.

Regards,


XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Esteban Aliverti
- Blog @ http://ilesteban.wordpress.com


On Fri, Oct 4, 2013 at 10:20 AM, rjr201 <rich.j.riley@gmail.com> wrote:
This is a statement about the nature of rules engines in general. Rules
engines are made up of human readable rules, as opposed to say a neural
network where the knowledge isn't explicitly represented (it's a big black
box of maths). A rules engine is symbolic, a neural network sub-symbolic. A
neural network can give you an answer, but not a justification of why.
People like rules engines because (when done properly) they can see why it
has given the answer it has given.

To answer your question, to get a explanation of what the rules engine did,
you could insert a logging object as a global into your rules session and
then add a log statement in the conclusion of each rule.



--
View this message in context: http://drools.46999.n3.nabble.com/How-does-drools-provides-an-explanation-of-how-the-solution-was-arrived-tp4026253p4026263.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users



_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users