DQM Status DQM Status Status as used (or not used) during 04/2016 - PowerPoint PPT Presentation

DQM Status DQM Status Status as used (or not used) during 04/2016 test beam GUI CSS Gui prepared for 40 ladders (precompiled) Available from belle2 software repository but rolled-out only scaled down version for used sensors to avoid confusion Precompiled version for testbeam in desy testbeam repository Gui scheme prepared for SVD, but afaik not further used. basf2 Prepared histograms which (mostly) already existed in basf2; reduced binning for some hist. Due to software crashes (pxd clusterizer), basf2 analysis chain on exp reco stopped after raw level, thus only raw hitmaps and charge hists were filled discussion about what we want to see on-line postponed B. Spruck, Uni Mainz, 3.3.2016, p. 1

DQM – Example OPIs DQM – Example OPIs Click on box opens corresponding sensor OPI (done with precompiled OPIs) B. Spruck, Uni Mainz, 3.3.2016, p. 2

DQM – Tech Details DQM – Tech Details Histograms from within basf2 (Express Reco) How and where to show histograms → Belle 2 common Automatic analysis and report back to operator? → Belle 2 common Where: CSS How: CSS widget and daq/basf2 modules/programs. Main code by Itoh-san and Konno-san What is doing technically: Take histograms from basf2 and serve them by Ethernet to CSS clients. (Analysing histograms is a different but related story) Thus → if we want to monitor something, we have to unpack it and store it in basf2, make histograms within basf2 Unpack data → data objects → plot data DQM code written (be)for DESY TB 2014: f.e. PXDDQMModule, PXDRawDQMModule, PXDROIDQMModule B. Spruck, Uni Mainz, 3.3.2016, p. 3

Schematic Schematic CSS Express Reco, basf2 Histo server request/read write display CSS Task 1 Histo 1 widget export Hist display Histo 2 CSS merge Hist Task 2 widget display Histo n CSS fit Hist Task 3 widget display widget nsm Fit results B. Spruck, Uni Mainz, 3.3.2016, p. 4

Issues Issues Performance unclear for large histograms (esp 2d) many histograms many clients All histograms share a single fixed update interval One way communication no way to dynamically switch histograms on/off No possibility to show lines, fits, comparison graphs Changes require basf2 recompile and exp reco restart Expert needed during TB → no updates Improvement needed: → DAQ group B. Spruck, Uni Mainz, 3.3.2016, p. 5

Backups Backups … from old presentation … B. Spruck, Uni Mainz, 3.3.2016, p. 6

Remarks Remarks We have to see how this fits to the other systems Considered histograms: pxd/hPXDAverageSeedByStartRow1 Prepare for TB, but keep full system in mind pxd/hPXDAverageSeedByStartRow2 pxd/hPXDClusterCharge1 pxd/hPXDClusterCharge2 More histos can be added on-demand, but before TB pxd/hPXDClusters1 pxd/hPXDClusters2 is preferred pxd/hPXDDigitCharge1 pxd/hPXDDigitCharge2 pxd/hPXDFired1 There are some issues with the histograms pxd/hPXDFired2 pxd/hPXDHitmapU1 pxd/hPXDHitmapU2 number, size (esp. for 2d) pxd/hPXDHitmapV1 pxd/hPXDHitmapV2 pxd/hPXDSeed1 pxd/hPXDSeed2 axis pxd/hPXDSeedCountsByStartRow1 pxd/hPXDSeedCountsByStartRow2 pxd/hPXDSeedCountsByU1 But nothing serious → Working! pxd/hPXDSeedCountsByU2 pxd/hPXDSeedCountsByV1 pxd/hPXDSeedCountsByV2 pxd/hPXDSize1 pxd/hPXDSize2 pxd/hPXDSizeU1 pxd/hPXDSizeU2 Remark: pxd/hPXDSizeV1 pxd/hPXDSizeV2 pxdraw/hrawPxdChargeMap_$(ID) Automatic analysis of histograms (e.g. fitting) can be pxdraw/hrawPxdCount pxdraw/hrawPxdHitMapAll done within the framework. But the results have to be pxdraw/hrawPxdHitMap_$(ID) pxdraw/hrawPxdHitsCharge_$(ID) transported as PVs (NSM→ EPICS interface) pxdraw/hrawPxdHitsCommonMode_$(ID) pxdraw/hrawPxdPackets pxdraw/hrawPxdPacketSize Showing the fit within CSS is not supported! pxdrawroi/hrawROIcount pxdrawroi/hrawROIDC_DHHID pxdrawroi/hrawROItype B. Spruck, Uni Mainz, 3.3.2016, p. 7

DQM DQM Data Quality Monitoring NOT status/health of ASICs, links, etc → EPICS NOT online O(seconds) but close to O(minutes) DQM runs on Express Reco and Offline. NOT on the event builder and not on the HLT (PXD data enters afterwards) Raw DQM (pixel based, (hardware) cluster based) data rates, mean event size, fired pixels, plain distributions Cluster DQM (after clusterizer) Overlap with tracking and ROI calculating DQM (efficiency of ROI selection etc) B. Spruck, Uni Mainz, 3.3.2016, p. 8

More ... More ... Problems with large histograms… need rebinning → no way to see a single hot pixel … but thats not the goal (?) B. Spruck, Uni Mainz, 3.3.2016, p. 9