On Wednesday 02 April 2003 21:57, [EMAIL PROTECTED] wrote:
> Yes, although that's really quite not how Jess is meant to be used;
> you can add all the Consumer objects at once, and the rule will fire
> only for those for which is applies, then extract all the results;
> this will be more efficient.
>From your comment and the manual I think I am getting the picture: Is
Jess meant to be used like this?
- Assert initial facts, rules, etc.
- run
where run makes somehow changes in the knowledge base via asserts in the
RHSs and so several runs fire rules? It's like the idea is that you are
expected to keep a unique instance of the the engine which makes the
knowledge base evolve.
If that was case I need to rethink the approach we are evaluating.
Our aim was to implement part of the behaviour of agents as (a very
vague idea of) "rules". For the sake of flexibility we would implement
different profiles of behavious in text files with Jess code. The set
up of the model would instantiate populations (say, 20% with that
behaviour, 15% with that other and so on). In each tick of time the
state of the model and agents (running all in a single virtual machine)
would change as a result of applying them (and probably some further
pure Java code). Each set of rules could potentially be different for
each individual. And the sets could change between executions.
Does that make any sense?
-- fxn
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
