1 / 19

The FDET DQM System

The FDET DQM System. Ian C. Brock FDET Review 13/6/2002. Outline. Aims and Concept Data sources The DQM job (Automatic) histogram checking ZMON Checkdqm Utilities Documentation The Future. Use histograms to check detector performance Make a history of selected variables

udell
Download Presentation

The FDET DQM System

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. The FDET DQM System Ian C. Brock FDET Review 13/6/2002

  2. Outline • Aims and Concept • Data sources • The DQM job • (Automatic) histogram checking • ZMON • Checkdqm • Utilities • Documentation • The Future FDET DQM

  3. 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 The Aims and Concept FDET DQM

  4. 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 10th written to disk Analysis job started automatically Data from all components available Sources of Data FDET DQM

  5. 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 The DQM Job FDET DQM

  6. The DQM Job – zuinit Which components? Initialise tfrecon Initialise UZ Initialise FRTD DQM Initialise HBOOK Setup STT control bits Book/read inhistograms Initialise strecon Read inUZ counters? Initialise STT DQM FDET DQM

  7. The DQM Job - zuanal Check GAFTYP Call TFEVIN Call STEVIN OK? OK? Get trigger bits Call TFPHS1 Call STPHS1 OK? OK? Also fill HV histograms and Ntuple Call TFPHS2 Call STPHS2 Measure CPUconsumptionUZ + histograms Call TFFDQM Call STDQM_ANAL FDET DQM

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

  9. Online Fill HV Ntuples Store histograms in shared memory Should include plots vs. time … Offline Determine single wire efficiencies Look for miscablings … Other Features FDET DQM

  10. 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 Automatic Histogram Checking FDET DQM

  11. 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 Looking at Histograms FDET DQM

  12. 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 ZMON FDET DQM

  13. 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 Balloon help also built in Has links to info needed to find out why DQM did not work Checkdqm FDET DQM

  14. 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 10th run or so Checkdqm – standard procedure FDET DQM

  15. 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 Other Utilities FDET DQM

  16. 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. Mn_fit Scripts FDET DQM

  17. 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_2002 Ranges to plot specified here History Ntuples and Plots FDET DQM

  18. 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 Logging and Documentation FDET DQM

  19. 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 The Future FDET DQM

More Related