1 / 7

New Run Control’s beast:

New Run Control’s beast:. Virtual DAQ Expert. Whom to blame for: Sergey Belikov. Goals:. Current : to annoy Achim Franz. Run 7 : to reduce the number of night calls ALARA, to increase the DAQ efficiency. Future : auto-fix most problems of the data collection. How does it work:.

fineen
Télécharger la présentation

New Run Control’s beast:

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. New Run Control’s beast: Virtual DAQ Expert Whom to blame for: Sergey Belikov DAQ Fest

  2. Goals: Current: to annoy Achim Franz. Run 7 : to reduce the number of night calls ALARA, to increase the DAQ efficiency. Future : auto-fix most problems of the data collection DAQ Fest

  3. How does it work: • VDE periodically checks status of a running Run Control by analyzing states of the most of its components: triggers, EBC, ATPs, SEBs, DCMs, GTMs. • If rate of all live triggers has become zero, or data flow has been broken, VDE tries to find out the source(s) of the problem and tells DO what to do to fix it. (In the nearest(?) future VDE will be able to fix it automatically by itself(?)) DAQ Fest

  4. Block diagram (very simplified) of the VDE operation G-links OK? No Tell DO what to do Yes No No No Triggers OK? No GTMs OK? Yes SEBs OK? Yes ATPs OK? Yes Yes No Data Flow OK? No Tell DO what to do EBCs OK? Yes Yes Sleep $VDE_PERIOD seconds No DCMs OK? Yes No GL1 RC OK? 631-689 -1991 Yes DAQ Fest

  5. What all those “OK”s mean • G-link OK are all DCMs’ G-links locked? • Trigger OK is at least one Live Trigger rolling ? • Data Flow OK • No EvB Mode: are DCMs’ event counters incremented?  • EvB Mode: EBC: run started and EBC is running? && are “received”, “assigned” and “completed” counters incremented  && at least 10% of all ATPs are running and DD Run Started? • GTM OK GTM is running and VME Busy is low • SEB OK Running && Buffer not Full && Nevents < Max • ATP OK Running && Run Started && Processing events. • EBC OK Running && Run Started • DCM OK G-link OK && no FPGA errors && no compressor errors && no other errors && Busy is low. DAQ Fest

  6. Current status • VDE is able to recognize most of the problem, and even more…Not obvious (to me) problems: • Even in the GL1 Run Control the EBC sometimes receives events, but does not assigns them in more then 10 seconds period. Why? • Starting from Run 5(4?) the DCM event counters are not incremented during the Stand Alone data taking, until you hit the Stop button. Changed threads race condition? • It would be great if all DAQ experts could improve “WHAT TO DO” part of the VDE. Collective experience? DAQ Fest

  7. Pink future… • By using Run 7 experience, make the “WHAT TO DO” advices correct in > 90% cases. • Add “Auto Fix” button to a VDE message for the cases where we are on 100% sure what has to be done to fix this condition. • Sound accompaniment? DAQ Fest

More Related