• State Not Answered
  • Replies 6 replies
  • Subscribers 3 subscribers
  • Views 192 views
  • Users 0 members are here
Options
Related

Hi all, I'm having some trouble with the triggers of an Event Frame Generation Analysis. It seems like it lost some random trigger, but the strangest thing is that it seems that it lost only ending triggers.

michele.moschella

I have a simple EFG analysis:
EFG Analysis.png
It has only three trigger: 'Daily Trigger' which is a tag written everyday at 6:00 AM, but with a Timestamp of 12:00PM (so 6 hour before), 'Irr_alm' a flag tag used to identify day by night (is 1 during the day and 0 during the night, I don't think is important in this case), and the last one which is a calculated tag:


Mode_Calculated.png
Here, the trigger is only 'Mode' which is a tag given by our customer (it's coming from a PItoPI interface).

So that's the situation which is relative simple, now the issue I'm having is that for some days of August the EFG analysis seems to have lost some triggers from 'Mode_Calculated'.

Here are the EF generated in real time during that period:


EF generated.png
Here the EF I was expecting, based on Preview:


EF expected.png
Also the Time Series Data of 'Mode_Calculated':


expected values.png
 

I don't understand why it seems that on 02/08 and 05/08 the EFG analysis seems to lost the trigger of the mode_calculated, but only on the ending trigger, 'cause the start of the events is correct, also the end time on the real time generated events is perfectly aligned with the Daily Trigger. I really don't know what's happening here.

Also there is no Automatic Backfilling on the analyses.

 

Thanks for the help,

Michele

Parents
  • 0

    Hi Michelle,

     

    Let's understand the subtle difference of some triggers.

     

    In the first image, where you have a variable named DailyTrigger, it is not neccessarily a trigger just because it has "Trigger" in the name. Rather, the Analysis is defined as Event-Triggered in the lower left, in which case DailyTrigger is indeed A trigger. But what type of trigger is it? It is a trigger to have the Analysis execute, but it is not a trigger to cause an event frame to start or stop. The Analysis will execute and then examine the Start Trigger expressions. If the Start Trigger is false, no event frame is generated by the new DailyTrigger.

     

    Triggers to start or stop and event frame have their own set of expressions as is evident in your image. You may omit the End Trigger as it will be implied when the StartTrigger changes from True to False. That is to say that the default End Trigger is the simple negation of the Start Trigger.

     

    However, you have defined an End Trigger and I want to stress that it is NOT identical to the simple negation of the StartTrigger. Your end trigger is when 'Mode_Calculated' is no longer 1. The negation of the StartTrigger is EITHER when 'Mode_Calculated' is no longer 1 OR when 'IRR_alm' is no longer 1.

     

    Note also that an event frame will not be created just because 'Mode_Calculated' equals 1. 'IRR_alm' must also equal 1 for the start trigger to fire. While you have been gracious enough to include some recorded values for 'Mode_Calculated', you should also review the recorded values for 'IRR_alm' during the same time period.

     

    Hope this helps,

    Rick Davin

Reply
  • 0

    Hi Michelle,

     

    Let's understand the subtle difference of some triggers.

     

    In the first image, where you have a variable named DailyTrigger, it is not neccessarily a trigger just because it has "Trigger" in the name. Rather, the Analysis is defined as Event-Triggered in the lower left, in which case DailyTrigger is indeed A trigger. But what type of trigger is it? It is a trigger to have the Analysis execute, but it is not a trigger to cause an event frame to start or stop. The Analysis will execute and then examine the Start Trigger expressions. If the Start Trigger is false, no event frame is generated by the new DailyTrigger.

     

    Triggers to start or stop and event frame have their own set of expressions as is evident in your image. You may omit the End Trigger as it will be implied when the StartTrigger changes from True to False. That is to say that the default End Trigger is the simple negation of the Start Trigger.

     

    However, you have defined an End Trigger and I want to stress that it is NOT identical to the simple negation of the StartTrigger. Your end trigger is when 'Mode_Calculated' is no longer 1. The negation of the StartTrigger is EITHER when 'Mode_Calculated' is no longer 1 OR when 'IRR_alm' is no longer 1.

     

    Note also that an event frame will not be created just because 'Mode_Calculated' equals 1. 'IRR_alm' must also equal 1 for the start trigger to fire. While you have been gracious enough to include some recorded values for 'Mode_Calculated', you should also review the recorded values for 'IRR_alm' during the same time period.

     

    Hope this helps,

    Rick Davin

Children
  • 0 in reply to Rick_Davin_3.0

    Hi Rick,

    thanks for your answer, however it does not help me very much.

    I understand all you said, and I agree. But I think you're missed the focal point here.

    The issue is not caused by the StartTrigger (so I don't think is relevant to include timeseries of 'IRR_alm' here), but it is caused in the EndTrigger.

    The events generated in realtime seems to be closed because the EndTrigger was satisfied (i.e. the Mode_Calculated=0), but the Analysis was triggered by the DailyTrigger, not the Mode_Calculated, so the End Time is at midnight.

    What I do not understand is why the analysys lost the trigger of the Mode_Calculated, but when it is triggered by the DailyTrigger it sees that Mode_Calculated has changed its value.

    This is also the reason why I attach the TimeSeries of the Mode_Calculated tag and the Preview of the Analysys.

    I hope it is more clear now what I'm trying to understand.

    Thank you.