On Feb 27, 2014, at 1:01 AM, Wolfgang Laun <wolfgang.laun(a)gmail.com&gt; wrote: The correct way to ascertain that something hasn't happened for a certain interval must be based on "staking out" this interval. One way is by means of two distinct events: when $r1: Reading( reading >90 ) $r2: Reading( reading > 90, this after[30s] $r1 ) not Reading( reading <= 90, this after $r1 && before $r2 ) then Clearly, this will only work if Readings arrive regularly, and you may have a certain amount of delay at the end. Another way would be to use a sliding window over time: when not Reading( reading <= 90 ) over window:time( 30s ) then Here's a snag, too: If there are no readings at all, you'll also get an alert. And then you'll have to think about the seconds following the 30th second: should another alert be emitted repeatedly... Most of the time, it's not an issue in CEP ;-) -W > On 27/02/2014, lin.lin <lin.lin(a)comcast.net&gt; wrote: > Hi, > > I tried to create a rule that gives an alert when a machine reading is high > for 30 seconds. I modeled the machine reading input as events. The > following is the rule: > > rule "rule1" > dialect "mvel" > when > $rd1 : mReading( reading >90 ) from entry-point ReadingStream > not ($rd2 : mReading (reading<=90 , this before [0s, 30s] $rd1 ) > from entry-point ReadingStream ) > then > System.out.print ("alert: Reading high for 30 seconds \n"); > end > > This does not detect detect the bad reading. However, If I changed the > rule > to be following (change second condition from "not" to "exists"), it > detects > all readings that are good. > > rule "rule1" > dialect "mvel" > when > $rd1 : mReading( reading >90 ) from entry-point ReadingStream > exists ($rd2 : mReading (reading<=90 , this before [0s, 30s] $rd1 ) > from entry-point ReadingStream ) > then > System.out.print ("alert: Reading high for 30 seconds \n"); > End > > > Is this an issue in CEP or did I do something wrong? > > Thanks a lot! > Lily > > > > -- > View this message in context: > http://drools.46999.n3.nabble.com/sliding-window-question-tp4028367.html > 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 _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

On Feb 27, 2014, at 4:06 PM, "lin.lin [via Drools]" < ml-node+s46999n4028396h13(a)n3.nabble.com&gt; wrote: Hi Thanks again for the pointers!! I modified the code but the sliding window rule does not seem to be working as how I want it to be(copied shown in the following). I injected 6 events, one event every 10 seconds, the first one is less than 90, the rest are more than 90. I am expecting getting 3 alerts at 4th event, 5th event and 6 event. But instead I only get one alert. when not Reading( reading <= 90 ) over window:time( 30s ) from entry-point ReadingStream then System.out.print ("alert: Reading high for 30 seconds \n"); So I used the other way as you suggested. It works and gives me 3 alerts. However if I added the accumulate pattern (copied below) , no alert is generated at all. If I removed the first 3 patterns, just leave the last pattern, it does print the average of last 30 seconds event every time when a new event is injected. What else did I do wrong? when $r1: Reading( reading >90 ) from entry-point HeartrateStream $r2: Reading( reading > 90, this after[30s,30s] $r1 ) from entry-point HeartrateStream not (Reading( reading <= 90, this after $r1, this before $r2 ) from entry-point HeartrateStream) $averg: Number() from accumulate( Reading ( $r:reading) over windiw:time(30s) from entry-point HeartrateStream, average($r) ) then System.out.print ("alert: Reading high for 30 seconds, average reading"+$averg+"\n"); Thanks a lot!!! Lin ------------------------------ If you reply to this email, your message will be added to the discussion below: http://drools.46999.n3.nabble.com/sliding-window-question-tp4028367p40283... To unsubscribe from sliding window question, click here<http://drools.46999.n3.nabble.com/template/NamlServlet.jtp?macro=... . NAML<http://drools.46999.n3.nabble.com/template/NamlServlet.jtp?macro=... _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

From: "lin.lin [via Drools]" <ml-node+s46999n4028540h77(a)n3.nabble.com&gt; Date: March 5, 2014 at 10:47:14 AM CST To: "lin.lin" <lin.lin(a)comcast.net&gt; Subject: Re: [rules-users] sliding window question Hi Walfgang, Thanks a lot for the pointers. My goal is to try detect a situation when readings about a user is consistent high for the last 30 seconds. The reading comes every 10 seconds. I have tried many different ways and still can not get it working. Here are a list of things that I found not working, I am wondering whether anyone has encountered some of this before or whether there is a known issue related to some of this or whether there is some configuration that I am missing in my environment. Also, what is a good way to find out whether a event has expired or still in working memory? I am stuck, please help. 1) the following rule does not work, according to drools book, this should work. rule "rule1" dialect "mvel" when $user: mUser(status==true) not (Reading ($user.userid== userid, reading<=90) over window :time (30s) from entry-point ReadingStream then 2) the following rules work on its own, (that is if I only include one rule in the .drl file), but when I put both rules in the .drl file, only the acumtest rule works but nothing comes out from "rule1" rule "acumtest" dialect "mvel" when accumulate( Reading( $r:reading) over windiw:time(30s) from entry-point ReadingStream, $sum : sum($r)) then System.out.print ("sum=" +$sum+"\n"); end rule "rule1" dialect "mvel" when $user: mUser(status==true) $hr1 : Reading ($user.userid==$hr1.userid, reading>90) from entry-point ReadingStream $hr2 : Reading ($user.userid==$hr2.userid, reading>90, this after [30s,30s] $hr1) from entry-point ReadingStream not Reading ($user.userid == userid, reading<=90, this after $hr1, this before $hr2) from entry-point ReadingStream then 3) The following rule does not work, but if I comment out the accumulate line in the condition, it works. Somehow, the accumulate function does not work with other rules or making event expired ?? rule "rule1" dialect "mvel" when $user: mUser(status==true) $hr1 : Reading ($user.userid==$hr1.userid, reading>90) from entry-point ReadingStream $hr2 : Reading ($user.userid==$hr2.userid, reading>90, this after [30s,30s] $hr1) from entry-point ReadingStream not Reading ($user.userid == userid, reading<=90, this after $hr1, this before $hr2) from entry-point ReadingStream $test: Number( doubleValue>0 ) from accumulate ( Reading( userid==$user.userid, $r:reading) over window:time(30s) from entry-point ReadingStream, sum($r)) then 4) This does work, but if I uncomment out the $hr4 line, then it does not work anymore rule "rule1" dialect "mvel" when $user: mUser(status==true) $hr1 : Reading ($user.userid==$hr1.userid, reading>90) from entry-point ReadingStream $hr2 : Reading ($user.userid==$hr2.userid, reading>90, this after [10s,10s] $hr1) from entry-point ReadingStream $hr3 : Reading ($user.userid==$hr3.userid, reading>90, this after [10s,10s] $hr2) from entry-point ReadingStream // $hr4 : Reading ($user.userid==$hr4.userid, reading>90, this after [10s,10s] $hr3) from entry-point ReadingStream $test: Number( doubleValue>0 ) from accumulate ( Reading( userid==$user.userid, $r:reading) over window:time(30s) from entry-point ReadingStream, sum($r)) then Thanks a lot! Lin If you reply to this email, your message will be added to the discussion below: http://drools.46999.n3.nabble.com/sliding-window-question-tp4028367p40285... To unsubscribe from sliding window question, click here. NAML