1. Pixel DQM Status R.Casagrande, P.Merkel, J.Zablocki (Purdue University) D.Duggan, D.Hidas, K.Rose (Rutgers University) L.Wehrli (ETH Zuerich) A.York (University of Tennessee) 09/01/09

2. 09-01-09Pixel DQM2 Reminder of DQM Infrastructure  Online DQM: monitoring on module level, a few Hz of the data stream. Focus on FED error detection, data corruption, noisy pixels.  Offline DQM (@Tier0): monitoring on ladder/blade level, full statistics, better calib constants, reco. Focus on clusters on- and off- track. (In the future: efficiencies).  Also from Tier0 DQM: trend plotting. Tier0 DQM writes values to offline DB, which then can be retrieved and plotted vs. run number.

3. 09-01-09Pixel DQM3 In the works  Static TrackerMaps embedded in DQM root files (K.Potamianos, J.Zablocki)  Additional TrackerMap layouts, e.g. by FED, by PS (K.Rose, PM)  Coarse hit efficiency monitoring (offline) (Antwerp group)  DCS info (LV, HV) will be incorporated in data certification (t.b.c.)  Monitoring of Pixel objects in the HLT (D.Duggan)

4. 09-01-09Pixel DQM4 Pixel DQM Operations  Online: Central process handled automatically by RunControl; we provide upgrades that get implemented within hours  days Local process running on vmepcs2b18-25 (tracker machine); started via RunControl by shifter;  development test bed and backup to central process Two new monitors installed (top-right) for DQM shift purposes  Offline: Central process runs automatically at Tier0 Trend monitoring requires manual root script running right now, will be automized.  Monitoring: shifters study histograms in the Central DQM GUI (online and offline) and the Pixel Expert GUI (online); trend plots on a web page.

5. 09-01-09Pixel DQM5 Online DQM during CRAFT09  First step was to detect all the noisy pixels with the DQM and to mask them  FED errors spotted reliably Discussing restructuring for collisions with Danek (monitor everything by FED channel only, not by module anymore)  Spotted FED’s not included in global DAQ (empty DQM plots)  Spotted part of detector off (cooling interlock) with DQM  Lower digi and cluster charges in barrel seen in online first  Reference plots are now overlaid

6. 09-01-09Pixel DQM6 Offline DQM  Lower thresholds and shifted barrel pedestals spotted Lower digi and cluster charges Concluded that new gain and pedestal calibration was not applied by mistake This was spotted by central and Tracker offline shifters  Data certification worked reliably, some cuts were tuned using the higher statistics, and adjusted to newly calibrated detector  Experience with offline shifts was mainly ok Pretty smooth operation overall Some improvements implemented along the way Some ideas for things to be changed before collisions  Trend plotting automated and used routinely for the first time

7. 09-01-09Pixel DQM7 Online charge distributions Barrel digis Endcap digis Barrel clusters Endcap clusters Grey histo: reference

8. 09-01-09Pixel DQM8 Offline clusters Clusters on tracks charge Clusters on tracks size Clusters off tracks size Clusters off tracks charge

9. 09-01-09Pixel DQM9 Track multiplicities “normal” run: Pixel/All ~3-4% FPIX/BPIX ~10% recent run: Pixel/All ~1‰ FPIX/BPIX ~1000%

10. 09-01-09Pixel DQM10 Trend monitoring: digi charge http://cmstac05.cern.ch/historic_dqm/HistoryDQM/AllRuns/Plots_SiPixelHistoricInfoClient/index.html Switched to new calib constants

11. 09-01-09Pixel DQM11 Trend monitoring: cluster charge OnTrack Switched to new calib constants

12. 09-01-09Pixel DQM12 Trend monitoring: track multiplicities #clusters on tracks (FPIX/BPIX) #clusters on tracks (PIX/ALL) # strip tracks (changed trigger conditions) Pixel timing studies: Last good run: 112101 (-12ns) All runs at -6, +12, +18 ns Show very low hit finding Efficiency.

13. 09-01-09Pixel DQM13 Summary  Good experience in online DQM  Some bugs spotted and fixed and improvements implemented throughout first half of CRAFT  Some shifters gave excellent feedback  Good experience in offline DQM  Plots and instructions updated for shifters  Trend monitoring is automated now  Cuts for data certification have been re-tuned  Automatic data certification partially successful (bad runs during timing studies only spotted by hand)  Experience with shifters  Better communication between P5 and offline needed (morning meeting not always attended by P5 shift leader)  Better training of offline shift leaders needed, better definition of their tasks  Started to train other Pixel DQM on-call experts  Things to do before collisions  Will put some changes regarding shift procedures in place based on CRAFT experience  Still implementing some new features in code (e.g. rechit efficiencies, change how errors are monitored, more user friendly features)