RunControl status update Nicolas Lurkin School of Physics and Astronomy, University of Birmingham NA62 TDAQ Meeting – CERN, 14/10/2015

TEL62 PCFarm Monitoring/Alert Other Big Screen Configuration Files Outline Nicolas Lurkin – TDAQ Meeting2

Configuration report is now provided at start of run.  Quick feedback in case of misconfiguration TEL62 Nicolas Lurkin – TDAQ Meeting3

Implemented BoardReload command directly from FSM.  Easier to use, sometimes abused of by shifters as general solution to everything Implemented BoardStatus command. Can be requested regularly to the board to understand if running correctly. -FSM is updated with WARNING state. If BoardStatus gives error, go in warning and propagate to detector level. TEL62 Nicolas Lurkin – TDAQ Meeting4 -Problem: Tested requesting every 3 burst (during inter-burst) but instability seen on tdspy  Crash, board get stuck, error flag is set after first request

Implemented L1 trigger configuration PCFarm is going to provide a list of received sources ID from which missing ones can be inferred.  Understand more easily which board is faulty (Use together with TEL62 BoardStatus) PCFarm Nicolas Lurkin – TDAQ Meeting5

Timing information provided by the farm (L0/L1 building time, L1/L2 processing time). Plots are generated with ROOT and displayed on RunControl. PCFarm Nicolas Lurkin – TDAQ Meeting6

Automatic restart has been improved: more tuneable, log available, done out of burst. Merger disk space monitoring: automatically exclude merger when more than 98% full Detection of hardware issue (memory full, system crash, …).  Automatically tries to power cycle node up to 3 times. PCFarm Nicolas Lurkin – TDAQ Meeting7

In case of failure of a beam line magnet, the electronics can be damaged.  K12 Magnets currents are read by the RunControl and integrated in the alert system. In case of problem the shifter is requested to close the TAX Monitoring/Alert Nicolas Lurkin – TDAQ Meeting8

Monitoring/Alert 9

Finalised integration of STRAW SRBs (commands, XML) Finalised integration of GTK readout (commands, XML) New L0TP parameters added (offset_det, reference detector, slowest detector, …) Global configuration of MEPFactor and Jumbo frames.  Modified in the PCFarm options and automatically applied to all readout configuration. No need for specific recipes anymore. Raspberry pi:  Stability improved (also on the pi side thanks to Matt)  Default threshold values are applied at start of run Information gathered from DIP (Experimental scalers, target intensity) are forwarded on DIM to the PCFarm and integrated in the data stream. Modifying configuration of a device is only allowed in a state before the configuration takes effect (e.g. Start run configuration can be modified until INITIALIZED state) Other Nicolas Lurkin – TDAQ Meeting10

Big Screen Nicolas Lurkin – TDAQ Meeting11 L0TP numbers (Received primitives, trigger masks, downscaling) Experimental scalers Target intensity

We had many problems with XML files: Wrong file loaded Use of outdated XML as basis when modifying XML Most of these problems arises from not enough organisation from people modifying XMLs: All XMLs at the same place, no naming convention (_old, _old_new, …), no history of modifications Configuration files Nicolas Lurkin – TDAQ Meeting12

Several attempts to find workaround: 1.Create single directory TDAQ_CONFIGURATION_OFFICIAL where files should be put before loading in DB. Revisioned directory  At some point, only DB was used. Became out of sync. 2.Create directory DBSync where files are copied every time they are loaded in DB.  Wrong file stored somewhere else used instead. 3.Prevent any long-term storage by cleaning shared directory regularly. When base file is needed, request RunControl to provide it (available for limited time to prevent outdating).  Where we stand so far Please try to be more organised when handling XML files. That might save a lot of troubles and data taking time. Configuration files Nicolas Lurkin – TDAQ Meeting13

Latest detectors included (Straw, GTK). LKr/L0 is the only one missing now. Improvement on TEL62 diagnostic PCFarm L1 configurable Monitoring of critical values and notifications to shifters. General operation by shifter is getting smoother and easier. Some known operations are automatised. XML configuration modification for TEL62 is now the main source of troubles (especially for CHOD) Conclusion Nicolas Lurkin – TDAQ Meeting14