8:26 a.m.
Hi there,
I'm working on a rule that will alert me when there is no events from the
sensors for a while.
So, first idea was to use time window and matches in condition side, to
match all types of sensors, and then to print that something is wrong.
rule "Alert if there is no activity"
when
not StateEvent(itemName matches "door.*|presence.*|luminosity.*") over
window:time( 1m ) from entry-point "EventStream"
then
System.out.println("Alert: one sensor is not working");
end
First change was to add a timer, as truth maintenance will fire this rule
the first time, but not forever. So i add a timer to fire the rule every 20
seconds, for example.
rule "Alert if there is no activity"
timer (cron:0/20 * * * * ?)
when
not StateEvent(itemName matches "door.*|presence.*|luminosity.*") over
window:time( 1m ) from entry-point "EventStream"
then
System.out.println("Alert: one sensor is not working");
end
The second thing i want to achieve is to print what specific sensor is not
working, but i understand that as there is no StateEvent, i can't declare a
variable, for example.
rule "Alert if there is no activity"
timer (cron:0/20 * * * * ?)
when
not $event: StateEvent(itemName matches
"door.*|presence.*|luminosity.*") over window:time( 1m ) from entry-point
"EventStream"
then
System.out.println("Alert: one sensor is not working: " +
$event.getItemName());
So, do you know how can i know which sensor is not working? must i rewrite
the rule to achieve this? is this possible?
Thanks for your help.
end
8:53 a.m.
Well, in fact the first idea was wrong.
If i use matches like this:
StateEvent(itemName matches "door.*|presence.*|luminosity.*")
and there is no door or presence events over time, but it receives some
luminosity events, rule doesn't fire.
So, any idea to put this to work?
Thanks
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Truth-maintenance-and-RHS-v...
Sent from the Drools: User forum mailing list archive at Nabble.com.
8:53 a.m.
Absence of facts (and events) is not a good foundation for rules, as you
have discovered.
Consider that the arrival of an event with some specific itemName is
another fact, and you want to monitor the aging of that secondary fact, or
cancel it as soon as yet another one arrives.
rule "start monitoring"
when
$se: StateEvent( $in: itemName )
then
Monitor m = new Monitor( $se, $in );
insert( m );
end
rule "stop monitoring"
when
$se: StateEvent( $in: itemName )
$m: Monitor( stateEvent != $se, itemName == $in )
then
retract( $m );
end
rule "nothing for 1m"
timer( int: 1m )
when
$m: Monitor( $in: itemName )
then
System.out.println( "not working: " + $in );
retract( $m );
end
Untested!
-W
2012/2/7 Juanker Atina <juankera(a)gmail.com>
Hi there,
I'm working on a rule that will alert me when there is no events from the
sensors for a while.
So, first idea was to use time window and matches in condition side, to
match all types of sensors, and then to print that something is wrong.
rule "Alert if there is no activity"
when
not StateEvent(itemName matches "door.*|presence.*|luminosity.*") over
window:time( 1m ) from entry-point "EventStream"
then
System.out.println("Alert: one sensor is not working");
end
First change was to add a timer, as truth maintenance will fire this rule
the first time, but not forever. So i add a timer to fire the rule every 20
seconds, for example.
rule "Alert if there is no activity"
timer (cron:0/20 * * * * ?)
when
not StateEvent(itemName matches "door.*|presence.*|luminosity.*") over
window:time( 1m ) from entry-point "EventStream"
then
System.out.println("Alert: one sensor is not working");
end
The second thing i want to achieve is to print what specific sensor is not
working, but i understand that as there is no StateEvent, i can't declare a
variable, for example.
rule "Alert if there is no activity"
timer (cron:0/20 * * * * ?)
when
not $event: StateEvent(itemName matches
"door.*|presence.*|luminosity.*") over window:time( 1m ) from entry-point
"EventStream"
then
System.out.println("Alert: one sensor is not working: " +
$event.getItemName());
So, do you know how can i know which sensor is not working? must i rewrite
the rule to achieve this? is this possible?
Thanks for your help.
end
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
10:10 a.m.
Thanks for your quick reply.
I can't say that your solution works because i'm facing a problem with
declared facts.
1. I have declared Monitor inside my drl file
2. I can insert monitor facts in "start monitoring" rule without problems.
And i've checked that it's fired.
But rule "nothing for 1m" is not working, even with the most basic LHS
rule "nothing for 1m"
when
$monitor : Monitor( )
then
System.out.println(
">>>>>>>>>>>>>>>>>>>>>>>
not working: " );
end
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Truth-maintenance-and-RHS-v...
Sent from the Drools: User forum mailing list archive at Nabble.com.
10:44 a.m.
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> wrote:
Thanks for your quick reply.
I can't say that your solution works because i'm facing a problem with
declared facts.
1. I have declared Monitor inside my drl file
2. I can insert monitor facts in "start monitoring" rule without problems.
And i've checked that it's fired.
But rule "nothing for 1m" is not working, even with the most basic LHS
rule "nothing for 1m"
when
$monitor : Monitor( )
then
System.out.println(
">>>>>>>>>>>>>>>>>>>>>>>
not working: " );
end
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Truth-maintenance-and-RHS-v...
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
9:03 a.m.
Thanks for your help... but i'm still trying to run the most basic example...
with no luck.
I can't see why second rule is not fired... as i understand, it will be
fired because of first rule action.
But i can't see anything. Any help will be appreciated.
declare Monitor
stateEvent : org.openhab.core.drools.event.StateEvent @key
itemName : String @key
end
rule "start monitoring sensors"
when
$se: StateEvent( $in: itemName )
then
org.openhab.demo.Monitor m = new Monitor( $se, $in );
insert( m );
System.out.println( "yikes¡");
end
rule "nothing for 1m"
when
$m: Monitor( $in: itemName )
then
System.out.println( "not working: " + $in );
end
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Truth-maintenance-and-RHS-v...
Sent from the Drools: User forum mailing list archive at Nabble.com.
9:19 a.m.
Use import and simple class names - the mixture is confusing.
Display a little more info in your printlns and show us what the
output really is.
If rule "start monitoring sensors" fires and there's no other rule, then
also
rule "nothing for 1m" must fire, immediately.
-W
On 08/02/2012, juankera <juankera(a)gmail.com> wrote:
Thanks for your help... but i'm still trying to run the most
basic
example...
with no luck.
I can't see why second rule is not fired... as i understand, it will be
fired because of first rule action.
But i can't see anything. Any help will be appreciated.
declare Monitor
stateEvent : org.openhab.core.drools.event.StateEvent @key
itemName : String @key
end
rule "start monitoring sensors"
when
$se: StateEvent( $in: itemName )
then
org.openhab.demo.Monitor m = new Monitor( $se, $in );
insert( m );
System.out.println( "yikes¡");
end
rule "nothing for 1m"
when
$m: Monitor( $in: itemName )
then
System.out.println( "not working: " + $in );
end
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Truth-maintenance-and-RHS-v...
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
10:34 a.m.
Sorry for the mess, i was trying different things.
1. I'm working with stateful session (no clocks, entry-points or events for
now).
2. I insert one StateEvent fact into working memory
3. Rules are fired.
4. I can see "yikes¡" in console
5. Nothing happens after that.
6. Rules are fired again
7. I can see "yikes¡" in console
8. Nothing happens after that.
I'm a newbie, but i understand that it must fire the second rule
inmediately.
Do you think that the rule engine is really working with this declared
fact?? Have i missed anything to register this declared fact?
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Truth-maintenance-and-RHS-v...
Sent from the Drools: User forum mailing list archive at Nabble.com.
11:28 a.m.
On 08/02/2012, juankera <juankera(a)gmail.com> wrote:
Sorry for the mess, i was trying different things.
1. I'm working with stateful session (no clocks, entry-points or events for
now).
2. I insert one StateEvent fact into working memory
3. Rules are fired.
4. I can see "yikes¡" in console
5. Nothing happens after that.
6. Rules are fired again
7. I can see "yikes¡" in console
This shouldn't happen. The first rule is triggered by the arrival of a
StateEvent,
and unless another one is inserted, it should not fire again - not in
the same session.
Looking at *all* of your code might solve this mystery.
-W
8. Nothing happens after that.
I'm a newbie, but i understand that it must fire the second rule
inmediately.
Do you think that the rule engine is really working with this declared
fact?? Have i missed anything to register this declared fact?
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Truth-maintenance-and-RHS-v...
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
11:36 a.m.
Sorry... big mistake. I forgot to mention that i'm inserting one StateEvent
after each rules firing.
So, these are the correct steps:
1. I'm working with stateful session (no clocks, entry-points or events for
now).
2. I insert one StateEvent fact into working memory
3. Rules are fired.
4. I can see "yikes¡" in console
5. Nothing happens after that.
2. I insert one new StateEvent fact into working memory (from code)
6. Rules are fired again
7. I can see "yikes¡" in console
8. Nothing happens after that.
Anyway, my code is as simple as that:
(..)
ksession.insert((RuleEvent) new StateEvent(item, state));
ksession.fireAllRules();
ksession.insert((RuleEvent) new StateEvent(item, state));
ksession.fireAllRules();
(...)
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Truth-maintenance-and-RHS-v...
Sent from the Drools: User forum mailing list archive at Nabble.com.
12:03 p.m.
Well, we'll have to look at the code, all of it.
-W
On 8 February 2012 18:36, juankera <juankera(a)gmail.com> wrote:
Sorry... big mistake. I forgot to mention that i'm inserting one
StateEvent
after each rules firing.
So, these are the correct steps:
1. I'm working with stateful session (no clocks, entry-points or events for
now).
2. I insert one StateEvent fact into working memory
3. Rules are fired.
4. I can see "yikes¡" in console
5. Nothing happens after that.
2. I insert one new StateEvent fact into working memory (from code)
6. Rules are fired again
7. I can see "yikes¡" in console
8. Nothing happens after that.
Anyway, my code is as simple as that:
(..)
ksession.insert((RuleEvent) new StateEvent(item, state));
ksession.fireAllRules();
ksession.insert((RuleEvent) new StateEvent(item, state));
ksession.fireAllRules();
(...)
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Truth-maintenance-and-RHS-v...
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
4:22 a.m.
Ok, i was working on cleaning the code and i've found the reason (now it will
be great to understand why :))
As i'm working with code from an open source platform, i have these lines in
my example:
KnowledgeAgentConfiguration aconf =
KnowledgeAgentFactory.newKnowledgeAgentConfiguration();
aconf.setProperty("drools.agent.newInstance", "false");
When i remove the second line, it works (i can see the "not working" rule
firing). When i put it back, the "not working" rule is not fired.
I've read that this property is related to new instances of KnowledgeBase
when resources changes...
c&p from:
http://grepcode.com/file/repository.jboss.org/maven2/org.drools/drools-ap...
/aconf.setProperty( "drools.agent.newInstance",
"true" ); // resource changes results in a new
instance of the KnowledgeBase being built,
// this cannot currently be set to false
for incremental building/
So, why is this property changing the behaviour of the rules?
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Truth-maintenance-and-RHS-v...
Sent from the Drools: User forum mailing list archive at Nabble.com.
2:12 a.m.
Please, any help will be appreciated.
Why this property is affecting the rules or the declared model?
Without changes in resources, i can't work with declared facts in rules if
this property (drools.agent.newInstance) is false.
Any idea?
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Truth-maintenance-and-RHS-v...
Sent from the Drools: User forum mailing list archive at Nabble.com.
4656
days inactive
4659
days old
12 comments
3 participants
participants (3)
-
Juanker Atina -
juankera
-
Wolfgang Laun