GNAM for MDT and RPC commissioning

Transcription

1 GNAM for MDT and RPC commissioning G. Crosetti, D. Salvatore, P.F. Zema (Cosenza) M. Della Pietra (Napoli) R. Ferrari, G. Gaudio, W. Vandelli (Pavia) 10 th Muon Week, Cetraro July 2005

2 Summary * GNAM and OHP In collaboration with Pisa GNAM group * GNAM for MDT and RPC test beam 2004 * From CTB to commissioning: MDT * From CTB to commissioning: RPC * Open issues * Conclusions 10th Muon Week, Cetraro Daniela Salvatore 2

3 GNAM GNAM is a low-level monitoring system. It separates common actions from detector specific ones. * Core: interaction with DAQ, data unpacking, histogram management, histogram related command handling * Plugins: data decoding, histogram filling to implement detector specific physics ---> people from different detectors developed their own code 10th Muon Week, Cetraro Daniela Salvatore 3

4 Monitoring chain 10th Muon Week, Cetraro Daniela Salvatore 4

5 Online Histogram Presenter OHP retrieves histos from the OH service and displays them in a nice and powerful GUI. * ROOT canvas available * manage reference histograms * possibility to use OHP as a browser, to quickly find and look at any histogram published on OHS... *... or to display selected significant histograms 10th Muon Week, Cetraro Daniela Salvatore 5

6 OHP as a browser for OHS 10th Muon Week, Cetraro Daniela Salvatore 6

7 OHP: a configured tab 10th Muon Week, Cetraro Daniela Salvatore 7

8 GNAM at MDT and RPC test beam GNAM was used during 2004 test beam to inspect detector status, find faulty states, check calibrations. * Four detector groups provided their specific codes: TileCal, Pixel, MDT and RPC MDT code by I.Boyko, D.Dedovitch, K.Nikolaev MDT plots RPC plots (M. Della Pietra) Hit maps Noise TDC Errors Beam profile Nr. of hits per event Hit profile for eta and phi Time correlation between confirm and pivot planes Time distribution for each strip 10th Muon Week, Cetraro Daniela Salvatore 8

9 GNAM at MDT and RPC test beam Hits Strip Profile ETA BML PIVOT Beam profile Time vs ijk PAD-1_CM-0 Pivot Confirm Trigger Generated trigger is on time 10th Muon Week, Cetraro Daniela Salvatore 9

10 From CTB to commissioning: MDT MDT code modified from CTB to satisfy different requests for commissioning at Pit: 1. manage a variable nr. and type of chambers instead of a pre-fixed one 2. choose how to retrieve MDTs parameters and mapping ---> new MapInterface routine (under construction) can access DB and/or a text file 3. once read, information is used in the same way independently of source ---> map format modifications only require changes in MapInterface 10th Muon Week, Cetraro Daniela Salvatore 10

11 From CTB to commissioning: MDT 4. some new histos have been implemented... Noise Frequency Occupancy...and others can be added on request 10th Muon Week, Cetraro Daniela Salvatore 11

12 From CTB to commissioning: RPC (M. Della Pietra) No major changes for the BB5 cosmic ray test stand. Some work needed for commissioning at Pit: 1. Better manage different kinds of stations. 2. Retrieve/Store the results of the test (dead or noisy strips) from/into a DB 10th Muon Week, Cetraro Daniela Salvatore 12

13 GNAM will provide * On-line histograms * MDT: TDC spectra vs mezzanine, Noise vs channel, Occupancy,... * RPC: Strip profile, Time vs channels, correlation between two layers on the same plane * Correlation histos (MDT vs RPC) * Histograms saved in a ROOT file * MDT: Text file with noise frequency per tube * RPC: Text file with dead and/or noisy channels 10th Muon Week, Cetraro Daniela Salvatore 13

14 Resources needed * DAQ: * GNAM needs ATLAS TDAQ environment * Events must have ATLAS structure * ROD level is enough: GNAM doesn t need the whole DataFlow chain Requirements already fulfilled thanks to the work done by Enrico * Computational power Computational power to be understood: depends on: number of events, trigger rate, total time, sampling efficiency 10th Muon Week, Cetraro Daniela Salvatore 14

15 Info needed: MDT Configuration * Many mapping formats up to now; trying to define a common unique one * Database: which interface? Producers are kindly asked to provide cabling schemes and geometrical information P. Fleischmann already contacted for BB5 mappings 10th Muon Week, Cetraro Daniela Salvatore 15

16 Info needed: RPC * Configuration (M. Della Pietra) * As for the MDT, some effort is needed to prepare and add the cabling scheme, both for RPC readout and LVL1 trigger. * Database: which interface? * LVL1 Trigger * Not yet defined what kind of Online Monitoring has to be done for the LVL1 Trigger. 10th Muon Week, Cetraro Daniela Salvatore 16

17 More open issues * Error handling * Any kind of automatic check to be performed? * What kind of alarms should be generated? * Time scale When would be necessary a running version? End of August? 10th Muon Week, Cetraro Daniela Salvatore 17

18 Conclusions GNAM is constantly upgrading to satisfy commissioning requests * many different chambers can be managed * Information will be retrieved from DB or files * Histograms can be added if needed but we are trying to clarifying pending open issues. Soon more documentation at 10th Muon Week, Cetraro Daniela Salvatore 18