Chris,
I haven't tried your code, but just looking at the rule, there is no
temporal correlation between DataReading and ReconfigEvent, so if I am not
mistaken, that will create a required interval of infinite time when the
temporal reasoning is applied, meaning the engine has to keep the
Edson,
I was under the impression that this:
declare ReconfigEvent
@role( event )
@expires ( 5s )
end
would cover that, meaning that every ReconfigEvent would expire after
5s, thus causing to no longer be needed by the engine.
Thanks,
Chris
On 7/25/2011 12:17 PM, Edson Tirelli
Chris
That defines the expiration policy for ReconfigEvent, but it does not
define the relationship between ReconfigEvent and DataReading. Imagine a
timeline, dotted with ReconfigEvents... what your rule is saying is for each
DataReading event, match it with all the periods where there is
Ok, well how to make them marry only those alive(100 years old) and
ensure all those over 100 years old go out of memory?
Chris
On 7/25/2011 2:32 PM, Edson Tirelli wrote:
Chris
That defines the expiration policy for ReconfigEvent, but it does
not define the relationship between
Hi Chris,
Best way is to explicitly define the relationship with a temporal
constraint (although there are other ways). E.g.:
when
$dr: DataReading(reading 10.0) from entry-point My Stream
not(DataReading(reading 10.0, this after[0s,3s] $dr) from entry-point
My Stream)
