Re: [rules-users] Truth maintenance and RHS variables

It works (5.3.0), but there's other things that can go awry. These are the settings I use: //... kBaseConfig.setOption( EventProcessingOption.STREAM ); //... kSessionConfig.setOption( ClockTypeOption.get("pseudo") ); //... clock = kSession.getSessionClock(); StateEvent se1 = new StateEvent( "door.1" ); kSession.insert( se1 ); kSession.fireAllRules(); clock.advanceTime( 60, TimeUnit.SECONDS ); kSession.fireAllRules(); clock.advanceTime( 1, TimeUnit.SECONDS ); kSession.fireAllRules(); clock.advanceTime( 1, TimeUnit.SECONDS ); StateEvent se2 = new StateEvent( "presence.2" ); kSession.insert( se2 ); clock.advanceTime( 25, TimeUnit.SECONDS ); StateEvent se3 = new StateEvent( "presence.2" ); kSession.insert( se3 ); clock.advanceTime( 40, TimeUnit.SECONDS ); kSession.fireAllRules(); And this is the output (according to println's in the three rules): created Monitor for door.1 not working: door.1 created Monitor for presence.2 stopped Monitor for presence.2 created Monitor for presence.2 A retract of an old StateEvent should be added to "stop monitoring": rule "stop monitoring" when $se: StateEvent( $in: itemName ) $m: Monitor( $ose: stateEvent != $se, itemName == $in ) then retract( $m ); retract( $ose ); System.out.println( "stopped Monitor for " + $in ); end -W On 07/02/2012, juankera <juankera(a)gmail.com&gt; wrote: