The FDET DQM System Ian C. Brock FDET Review 13/6/2002

13/06/2002FDET DQM2 Outline Aims and Concept Data sources The DQM job (Automatic) histogram checking ZMON Checkdqm Utilities Documentation The Future

13/06/2002FDET DQM3 The Aims and Concept Use histograms to check detector performance Make a history of selected variables Collect information needed for calibration Log bad runs or data taking periods for future physics analysis Integrate FTD and STT jobs offline FTD and STT DQM are separate online Automatic checking as much as possible Use same code online and offline CVS as central code repository

13/06/2002FDET DQM4 Sources of Data Online –Server/Client system Data split before event builder Data from only one detector available –Server on zaxp07 –Client/Consumer on zulu9 (or any other Linux machine) Offline –RAW data tapes Every 10 th written to disk Analysis job started automatically –Data from all components available

13/06/2002FDET DQM5 The DQM Job Standard EAZE job –Separate zuinit, zuanal, zuterm for offline (FTD + STT), online FTD and online STT Special code to read in online data and set up necessary ADAMO tables. Online and offline code otherwise common Offline job can read in and update histograms and UZ counters Online job keeps histograms in shared memory + RZ file Online source code in /data/fdet_onl/… on zulu9

13/06/2002FDET DQM6 The DQM Job – zuinit Read in UZ counters? Initialise HBOOK Book/read in histograms Initialise STT DQM Initialise tfrecon Initialise FRTD DQM Initialise strecon Setup STT control bits Which components? Initialise UZ

13/06/2002FDET DQM7 The DQM Job - zuanal Check GAFTYP Call TFEVIN Call TFPHS1 Call STEVIN Call STPHS1 Get trigger bits Call TFPHS2 Call STPHS2 Call TFFDQM Call STDQM_ANAL OK? Measure CPU consumption UZ + histograms Also fill HV histograms and Ntuple

13/06/2002FDET DQM8 The DQM Job - zuterm Call stterm Call tfterm Write FRTD histograms FRTD residuals & resolution Write HV histograms Bad channels DQM summary + T0 Segment efficiency Space  drift time Write STT histograms Call STDQM_ANAL Online: Histograms + UZ counters written every ~500 events to file(s)

13/06/2002FDET DQM9 Other Features Online –Fill HV Ntuples –Store histograms in shared memory –Should include plots vs. time –… Offline –Determine single wire efficiencies –Look for miscablings –…

13/06/2002FDET DQM10 Automatic Histogram Checking Online –System designed for unix –Adapted by HPJ for VMS –Needs to be implemented on zulu9 (Linux) –Checks for STT have to be defined Offline (in progress) –Convert histograms to root format –Add checks to histogram class –More manpower would help

13/06/2002FDET DQM11 Looking at Histograms Online –Online DQM keeps histograms in shared memory –Can (in theory) be accessed by VMS presenter (needs to be set up) Zulu9 –Histograms written to disk every 500 events –mon_hist command

13/06/2002FDET DQM12 ZMON Histograms are filled when ZEPHYR is run (standard ZEUS reconstruction) Only place where ALL data is checked Checking integrated into ZMON Size and number of histograms limited STT still has to be implemented

13/06/2002FDET DQM13 Checkdqm Standard tool for checking DQM histograms and more TRD replaced by STT Standard checkdqm in ~fdetdqm/tcl/pro/checkdqm + fdetdqm CVS repository Use ~fdetdqm/tcl/old/checkdqm for ZEUS I data Some basic documtation available FDETDQM documentation FDETDQM documentation Balloon help also built in Has links to info needed to find out why DQM did not work

13/06/2002FDET DQM14 Checkdqm – standard procedure Update the run logs See which runs have been analysed Check the history Check the histograms for the run Update the run logs Similar procedure for ZMON histograms –Usually check history and all histograms for every 10 th run or so

13/06/2002FDET DQM15 Other Utilities Online (zaxp07/zulu9) evs [ftd|stt] –shows whether events are available, –which clients are running, –data volume transferred –error counts … –Uses ~15-20% zaxp07 CPU mon_client ftd|stt mon_conusmer ftd|stt mon_logfiles mon_processes Offline Checkrun(x) - run DQM job for a run ep_check.pl –See if all (and only all) EP runs analysed Dqmrunlog –Summary of which automatic DQM jobs ran makedqmps makezemps makehistory

13/06/2002FDET DQM16 Mn_fit Scripts In ~fdetdqm/mnf and CVS repository exec dqm_setup.ftd.2002 to set things up ftd_check runno to run standard checks ftd_help to see what commands are defined ZMON histograms work in same way exec zem_setup.ftd.2000 etc.

13/06/2002FDET DQM17 History Ntuples and Plots In ~ fdetdqm/history and CVS repository.defs files specify which histograms and values are checked –Single bin, area, RMS, … Also specifies valid ranges (not ideal) Mn_Fit macros to display Ntuples Exec history_setup_ftd_200 2 Ranges to plot specified here

13/06/2002FDET DQM18 Logging and Documentation Logbook and run logs –Summarise status of each run TFTAKE/TRTAKE/STTAKE –List of bad runs –Made semiautomatically from run logs –Started at end of checkdqm Online –Client/server README –Online primer Checkdqm –Balloon help –Learning by doing DQM –Web pages

13/06/2002FDET DQM19 The Future Refine standard STT plots Refine online FTD checks Update VMS presenter menus Replace checkdqm with root based system Automated checking should replace most of checkdqm functionality