Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  11 Mar 2019, Francesco Renga, Forum, Run length 
    Reply  12 Mar 2019, Stefan Ritt, Forum, Run length 
    Reply  12 Mar 2019, Pierre Gorel, Forum, Run length 
    Reply  13 Mar 2019, Konstantin Olchanski, Forum, Run length 
Message ID: 1487     Entry time: 12 Mar 2019     In reply to: 1484
Author: Pierre Gorel 
Topic: Forum 
Subject: Run length 
> 
> .... some ODB settings ....
>      TRANSITION START
>      WAIT events 100
>      TRANSITION STOP
> I have two questions: 
> 
> - for the long run, I want to write on disk only a maximum number of events. I think I can suppress 
> the event polling in the frontend, with an ODB query of the number of collected events. I'm 
> wondering if there is a smarter way to do that. It is also ok if the run is stopped after a maximum 
> number of events, but the subsequent short run should still start exactly after 1h from the previous 
> short run. 

I don't know about a way to give you an exact number of events (maybe /Logger/Run duration). 

I personally use 
    WAIT ODBValue,"/Equipment/DTM/Statistics/Events sent",>,100

Where DTM is the frontend of my trigger. Because of the lag in the run stop, the run will always exceed by few
seconds*rates.

Hope it helps
ELOG V3.1.4-2e1708b5