[JBoss JIRA] Created: (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
10:17 a.m.
Sliding window of length type does not accumulate/collect correctly with multiple objects
in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://jira.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Mark Proctor
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly in
DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X number
of samples averaged or summed. I've tried two mechanism, the accumulate/from, and the
collect, and they both behave similarly wrong (or different than I expect), but this was
much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but they
perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:39 a.m.
New subject: [JBoss JIRA] Assigned: (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
[
https://jira.jboss.org/browse/JBRULES-2823?page=com.atlassian.jira.plugin...
]
Edson Tirelli reassigned JBRULES-2823:
--------------------------------------
Assignee: Edson Tirelli (was: Mark Proctor)
Sliding window of length type does not accumulate/collect correctly
with multiple objects in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://jira.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Edson Tirelli
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly
in DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X
number of samples averaged or summed. I've tried two mechanism, the accumulate/from,
and the collect, and they both behave similarly wrong (or different than I expect), but
this was much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but
they perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:43 a.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
[
https://jira.jboss.org/browse/JBRULES-2823?page=com.atlassian.jira.plugin...
]
Edson Tirelli updated JBRULES-2823:
-----------------------------------
Labels: fusion_roadmap (was: )
Fix Version/s: 5.2.0.M1
Priority: Critical (was: Major)
Drools should scope behavior implementations (like Sliding windows) by the left tuple
instead of by patter. Beta constraints should be applied before applying the behavior.
This is also a requirement to support sliding windows over CEs instead of only over
patterns.
Sliding window of length type does not accumulate/collect correctly
with multiple objects in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://jira.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Edson Tirelli
Priority: Critical
Labels: fusion_roadmap
Fix For: 5.2.0.M1
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly
in DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X
number of samples averaged or summed. I've tried two mechanism, the accumulate/from,
and the collect, and they both behave similarly wrong (or different than I expect), but
this was much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but
they perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:08 a.m.
New subject: [JBoss JIRA] Commented: (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
[
https://issues.jboss.org/browse/JBRULES-2823?page=com.atlassian.jira.plug...
]
Wolfgang Laun commented on JBRULES-2823:
----------------------------------------
Given an event sequence A, A, B,..., the
rule AB
when
A() over window:length(1)
B() over window:length(1)
then ... end
pairs the last B with *each* A, whereas the rule
rule AB
when
B() over window:length(1)
A() over window:length(1)
then ... end
appears to work correctly. (I think this confirms Edson's analysis.)
Sliding window of length type does not accumulate/collect correctly
with multiple objects in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://issues.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Edson Tirelli
Priority: Critical
Labels: fusion_roadmap
Fix For: 5.2.0.M1
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly
in DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X
number of samples averaged or summed. I've tried two mechanism, the accumulate/from,
and the collect, and they both behave similarly wrong (or different than I expect), but
this was much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but
they perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:44 a.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
[
https://issues.jboss.org/browse/JBRULES-2823?page=com.atlassian.jira.plug...
]
Mark Proctor updated JBRULES-2823:
----------------------------------
Fix Version/s: 5.2.0.CR1
(was: 5.2.0.M1)
Sliding window of length type does not accumulate/collect correctly
with multiple objects in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://issues.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Edson Tirelli
Priority: Critical
Labels: fusion_roadmap
Fix For: 5.2.0.CR1
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly
in DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X
number of samples averaged or summed. I've tried two mechanism, the accumulate/from,
and the collect, and they both behave similarly wrong (or different than I expect), but
this was much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but
they perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:42 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
[
https://issues.jboss.org/browse/JBRULES-2823?page=com.atlassian.jira.plug...
]
Mark Proctor updated JBRULES-2823:
----------------------------------
Fix Version/s: 5.3.0.M1
(was: 5.2.0.CR1)
Sliding window of length type does not accumulate/collect correctly
with multiple objects in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://issues.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Edson Tirelli
Priority: Critical
Labels: fusion_roadmap
Fix For: 5.3.0.M1
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly
in DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X
number of samples averaged or summed. I've tried two mechanism, the accumulate/from,
and the collect, and they both behave similarly wrong (or different than I expect), but
this was much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but
they perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:41 a.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
[
https://issues.jboss.org/browse/JBRULES-2823?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2823:
--------------------------------------
Fix Version/s: 5.3.0.CR1
(was: 5.3.0.Beta1)
Sliding window of length type does not accumulate/collect correctly
with multiple objects in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://issues.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Edson Tirelli
Priority: Critical
Labels: fusion_roadmap
Fix For: 5.3.0.CR1
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly
in DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X
number of samples averaged or summed. I've tried two mechanism, the accumulate/from,
and the collect, and they both behave similarly wrong (or different than I expect), but
this was much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but
they perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:04 a.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
[
https://issues.jboss.org/browse/JBRULES-2823?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2823:
--------------------------------------
Fix Version/s: 5.3.0.Final
(was: 5.3.0.CR1)
Sliding window of length type does not accumulate/collect correctly
with multiple objects in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://issues.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Edson Tirelli
Priority: Critical
Labels: fusion_roadmap
Fix For: 5.3.0.Final
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly
in DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X
number of samples averaged or summed. I've tried two mechanism, the accumulate/from,
and the collect, and they both behave similarly wrong (or different than I expect), but
this was much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but
they perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:02 a.m.
New subject: [JBoss JIRA] (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
[
https://issues.jboss.org/browse/JBRULES-2823?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2823:
--------------------------------------
Fix Version/s: 5.4.0.Beta1
(was: 5.3.0.Final)
Sliding window of length type does not accumulate/collect correctly
with multiple objects in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://issues.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Edson Tirelli
Priority: Critical
Labels: fusion_roadmap
Fix For: 5.4.0.Beta1
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly
in DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X
number of samples averaged or summed. I've tried two mechanism, the accumulate/from,
and the collect, and they both behave similarly wrong (or different than I expect), but
this was much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but
they perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:34 a.m.
New subject: [JBoss JIRA] (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
[
https://issues.jboss.org/browse/JBRULES-2823?page=com.atlassian.jira.plug...
]
Edson Tirelli commented on JBRULES-2823:
----------------------------------------
As previously mentioned, this is a limitation on how sliding windows work up to Drools
5.3, i.e., first they apply filters, then the window, then the join.
As we speak, I am working on the full implementation of named windows and the support to
additional window types, that will remove this limitation.
I am closing this ticket.
Sliding window of length type does not accumulate/collect correctly
with multiple objects in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://issues.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Edson Tirelli
Priority: Critical
Labels: fusion_roadmap
Fix For: 5.4.0.Beta1
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly
in DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X
number of samples averaged or summed. I've tried two mechanism, the accumulate/from,
and the collect, and they both behave similarly wrong (or different than I expect), but
this was much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but
they perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:34 a.m.
New subject: [JBoss JIRA] (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
[
https://issues.jboss.org/browse/JBRULES-2823?page=com.atlassian.jira.plug...
]
Edson Tirelli resolved JBRULES-2823.
------------------------------------
Resolution: Out of Date
Sliding window of length type does not accumulate/collect correctly
with multiple objects in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://issues.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Edson Tirelli
Priority: Critical
Labels: fusion_roadmap
Fix For: 5.4.0.Beta1
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly
in DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X
number of samples averaged or summed. I've tried two mechanism, the accumulate/from,
and the collect, and they both behave similarly wrong (or different than I expect), but
this was much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but
they perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:34 a.m.
New subject: [JBoss JIRA] (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
[
https://issues.jboss.org/browse/JBRULES-2823?page=com.atlassian.jira.plug...
]
Edson Tirelli closed JBRULES-2823.
----------------------------------
Sliding window of length type does not accumulate/collect correctly
with multiple objects in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://issues.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Edson Tirelli
Priority: Critical
Labels: fusion_roadmap
Fix For: 5.4.0.Beta1
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly
in DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X
number of samples averaged or summed. I've tried two mechanism, the accumulate/from,
and the collect, and they both behave similarly wrong (or different than I expect), but
this was much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but
they perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:32 p.m.
New subject: [JBoss JIRA] (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
[
https://issues.jboss.org/browse/JBRULES-2823?page=com.atlassian.jira.plug...
]
Markus Merder commented on JBRULES-2823:
----------------------------------------
Edson, is there another issue adressing this case?
Could you also update the reference guide: It says:
For instance, if the user wants to consider only the last 10 IBM Stock Ticks, independent
of how old they are, the pattern would look like this:
StockTick( company == "IBM" ) over window:length( 10 )
Actually it shold be: "For instance, if the user wants to consider only IBM Stock
Ticks within the last 10 Stock Ticks"
Sliding window of length type does not accumulate/collect correctly
with multiple objects in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://issues.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Edson Tirelli
Priority: Critical
Labels: fusion_roadmap
Fix For: 5.4.0.Beta1
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly
in DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X
number of samples averaged or summed. I've tried two mechanism, the accumulate/from,
and the collect, and they both behave similarly wrong (or different than I expect), but
this was much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but
they perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:41 p.m.
New subject: [JBoss JIRA] (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
[
https://issues.jboss.org/browse/JBRULES-2823?page=com.atlassian.jira.plug...
]
Edson Tirelli commented on JBRULES-2823:
----------------------------------------
Markus, the guide is correct. The pattern will select the last 10 IBM tickets as the
filter is applied before the sliding window as of Drools 5.3.
The new work on the sliding windows is being done under ticket JBRULES-2623 and will be
part of Drools 5.4.
Sliding window of length type does not accumulate/collect correctly
with multiple objects in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://issues.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Edson Tirelli
Priority: Critical
Labels: fusion_roadmap
Fix For: 5.4.0.Beta1
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly
in DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X
number of samples averaged or summed. I've tried two mechanism, the accumulate/from,
and the collect, and they both behave similarly wrong (or different than I expect), but
this was much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but
they perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:01 p.m.
New subject: [JBoss JIRA] (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
[
https://issues.jboss.org/browse/JBRULES-2823?page=com.atlassian.jira.plug...
]
Markus Merder commented on JBRULES-2823:
----------------------------------------
Thanks Edson, anyway it would have saved me a lot of time if you could mention beta nodes
are being applied after the window. In my rule I had an event which has a reference to
another object. My restriction was using this object, so it was no literal condition.
Am I right?
Sliding window of length type does not accumulate/collect correctly
with multiple objects in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://issues.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Edson Tirelli
Priority: Critical
Labels: fusion_roadmap
Fix For: 5.4.0.Beta1
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly
in DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X
number of samples averaged or summed. I've tried two mechanism, the accumulate/from,
and the collect, and they both behave similarly wrong (or different than I expect), but
this was much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but
they perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:17 p.m.
New subject: [JBoss JIRA] (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
[
https://issues.jboss.org/browse/JBRULES-2823?page=com.atlassian.jira.plug...
]
Edson Tirelli commented on JBRULES-2823:
----------------------------------------
That is correct and it is the main reason we are developing explicit window declarations
for version 5.4+: to make clear, specially for the rules authors and users, what is part
of the window definition and what is part of the rule, i.e., what is applied before and
after the window is defined.
Regarding the documentation, if you can provide a patch for the part that derailed you, it
would be great. Unfortunately, things that sometimes might seem clear for us, are not
clear for users. It won't recover the time you wasted to figure out the behavior, but
can prevent someone else from having the same problem.
Sliding window of length type does not accumulate/collect correctly
with multiple objects in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://issues.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Edson Tirelli
Priority: Critical
Labels: fusion_roadmap
Fix For: 5.4.0.Beta1
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly
in DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X
number of samples averaged or summed. I've tried two mechanism, the accumulate/from,
and the collect, and they both behave similarly wrong (or different than I expect), but
this was much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but
they perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:31 p.m.
New subject: [JBoss JIRA] (JBRULES-2823) Sliding window of length type does not accumulate/collect correctly with multiple objects in constraints
[
https://issues.jboss.org/browse/JBRULES-2823?page=com.atlassian.jira.plug...
]
Markus Merder commented on JBRULES-2823:
----------------------------------------
Hey Edson, see JBRULES-3312.
Thanks for your help!
Sliding window of length type does not accumulate/collect correctly
with multiple objects in constraints
--------------------------------------------------------------------------------------------------------
Key: JBRULES-2823
URL: https://issues.jboss.org/browse/JBRULES-2823
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Environment: Windows XP Java
Reporter: Mary Ellen Bench
Assignee: Edson Tirelli
Priority: Critical
Labels: fusion_roadmap
Fix For: 5.4.0.Beta1
When using sliding windows and a constraint that filters by an input object, it does not
properly create a window for each constraints, instead one window shared by both rules
which leads to undesirable affects (ie a shared sliding window filtered down to less #s).
Please also see the drools post:
http://drools-java-rules-engine.46999.n3.nabble.com/DROOLS-problem-with-s...
It is best to show the rule and output to explain it:
Background:
"I have been working with sliding windows, and they do not appear to work properly
in DROOLS 5.1.1 or I am misunderstanding how they work. My goal is to have the last X
number of samples averaged or summed. I've tried two mechanism, the accumulate/from,
and the collect, and they both behave similarly wrong (or different than I expect), but
this was much easier to follow so I've posted it for help.
The way I have the code structured, I receive values for two nodes, 1 and 2 every second
or two, which each contain random values. After each value received I pass the
CPUReportEvent and fire the rules. The results are bizarre. Sometimes it resets back to
1 count, sometimes it keeps the value to the previous one. It seems to also fire both
rules when really only one should've been triggered? Can someone explain the results
and how to adjust it to work for my specs? Thanks!
I can't see into the accumulate function, so here's the collect function, but
they perform identically. "
package com.sample
import com.sample.DroolsTest.Message;
import com.sample.DroolsInput;
import com.sample.CPUReportEvent;
import com.ComEntity;
import java.util.Iterator
import java.util.ArrayList
declare CPUReportEvent
// declare a fact type as an event, default is 'fact'
@role( event )
end
rule "collect with length window"
no-loop true
when
$comEntity : ComEntity()
$list : ArrayList () from collect(
CPUReportEvent(comEntity == $comEntity)
over window:length(3) )
then
System.out.print("Entity " + $comEntity.getName() + " fired of count
" + $list.size() + " value");
Double sum = 0.0;
Double count = 0.0;
for(Iterator it = $list.iterator();it.hasNext();) {
CPUReportEvent report = (CPUReportEvent) it.next();
System.out.print(" " + report.getAmount());
sum = sum + report.getAmount();
count = count + 1.0;
}
if (count > 0.0)
{
Double avg = (sum / count);
System.out.print(" - Sum " + sum + " avg " + avg + "
count " + count);
}
System.out.println();
end
RESULTS:
Node1 : 7.0
Entity Node2 fired of count 0 value
Entity Node1 fired of count 1 value 7.0 - Sum 7.0 avg 7.0 count 1.0
Node2 : 94.0
Entity Node2 fired of count 1 value 94.0 - Sum 94.0 avg 94.0 count 1.0
Node1 : 43.0
Entity Node1 fired of count 2 value 7.0 43.0 - Sum 50.0 avg 25.0 count 2.0
Node2 : 85.0
Entity Node2 fired of count 2 value 94.0 85.0 - Sum 179.0 avg 89.5 count 2.0
Entity Node1 fired of count 1 value 43.0 - Sum 43.0 avg 43.0 count 1.0
Node1 : 88.0
Entity Node2 fired of count 1 value 85.0 - Sum 85.0 avg 85.0 count 1.0
Entity Node1 fired of count 2 value 43.0 88.0 - Sum 131.0 avg 65.5 count 2.0
Node2 : 47.0
Entity Node2 fired of count 2 value 85.0 47.0 - Sum 132.0 avg 66.0 count 2.0
Entity Node1 fired of count 1 value 88.0 - Sum 88.0 avg 88.0 count 1.0
Node1 : 39.0
Entity Node2 fired of count 1 value 47.0 - Sum 47.0 avg 47.0 count 1.0
Entity Node1 fired of count 2 value 88.0 39.0 - Sum 127.0 avg 63.5 count 2.0
Node1 : 0.0
Entity Node1 fired of count 2 value 39.0 0.0 - Sum 39.0 avg 19.5 count 2.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4778
days inactive
5148
days old
16 comments
10 participants
participants (10)
-
Edson Tirelli (Closed) (JIRA) -
Edson Tirelli (Commented) (JIRA)
-
Edson Tirelli (JIRA)
-
Edson Tirelli (Resolved) (JIRA)
-
Geoffrey De Smet (JIRA)
-
Geoffrey De Smet (Updated) (JIRA)
-
Mark Proctor (JIRA)
-
Markus Merder (Commented) (JIRA)
-
Mary Ellen Bench (JIRA)
-
Wolfgang Laun (JIRA)