New zero suppression in simulation: current status David Adams BNL November 25, 2015 DUNE 35-ton simulation, reconstruction and analysis

Introduction I have been working on zero suppression (ZS) Have simulation of the ZS planned for 35-ton running o See description of this and current simulation default at Working on new DetSim module that can use the new ZS sim o Will allow user to plug in different services for ZS – And for multi-channel ZS and compression o Also developing modules to reproduce current behavior For more info, see my talk at last meeting of this goup: o Dunezs package Has three ZS services: legacy, 35t sim, no ZS One compression service: sets ADC to zero for suppressed channels Detsim module that uses above ZS and compression through service interfaces D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, 20152

Legacy ZS I created a service to do “legacy” ZS I.e. to reproduce the ZS in the current version of dunetpc o That used for past (and upcoming) MCC Keep +/-TickRange ticks around any tick with |ADC| > AdcThreshold I reported slight discrepancies between new and old code last week I added option to not suppress a range < MinTickGap o This fixed some of the disscrepancy But there are still differences o In a few cases I keep a tick that is suppressed by the old code o Often/always following double peak and range of constant ADC o Jonathon thinks this is likely a defect in the old code o Discrepancy is in 15/29M ( %) of bins o Difference is in either ZS or compression code No plan to resolve remaining discrepancy D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, 20153

Unsuppressed D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, 20154

New suppression D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, service_provider: ZeroSuppress35tLegacyService AdcThreshold: 10.0 TickRange: 10 MinTickGap: 2 SuppressStickyBits: true New code keeps this tick

Old suppression D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, Old code suppresses this tick

New noise model Last week I showed the then-current noise model Significant correlations between neighboring ticks o I.e. low frequency (compared to 2MHz) noise RMS was 3.2 ADC counts Shortly after the meeting a new default was defined Higher frequency RMS = 2.5 ADC counts Parameters are in the next slide I believe this is what we intend to use for the upcoming MCC o May also produce a 35t sample with twice the amplitude o I.e. RMS=5, close to present observation in 35t I used this to tune zero suppression and produce results shown here D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, 20157

DetSim producer parameters daq: { CollectionCalibPed: 500 CollectionCalibPedRMS: 0.01 CollectionPed: 500 CollectionPedRMS: 0.01 CompressionType: "ZeroSuppression" DriftEModuleLabel: "largeant" FractHorizGapUCollect: 0.1 FractHorizGapUMiss: 0.8 FractHorizGapVCollect: 0.1 FractHorizGapVMiss: 0.8 FractHorizGapZMiss: 0.8 FractUUCollect: 0.5 FractUUMiss: 0.2 FractUVCollect: 0.1 FractUVMiss: 0.2 FractVUCollect: 0.5 FractVUMiss: 0.2 FractVVCollect: 0.1 FractVVMiss: 0.2 FractVertGapUCollect: 0.1 FractVertGapUMiss: 0.8 FractVertGapVCollect: 0.1 FractVertGapVMiss: 0.8 FractVertGapZMiss: 0.8 FractZUMiss: 0.2 FractZVMiss: 0.2 InductionCalibPed: 1800 InductionCalibPedRMS: 0.01 InductionPed: 1800 InductionPedRMS: 0.01 LowCutoffU: 7.5 LowCutoffV: 7.5 LowCutoffZ: 7.5 NearestNeighbor: 25 NeighboringChannels: 3 NoiseArrayPoints: 1000 NoiseFactU: 0.05 NoiseFactV: 0.05 NoiseFactZ: 0.05 NoiseModel: 1 NoiseWidthU: 2000 NoiseWidthV: 2000 NoiseWidthZ: 2000 PedestalOn: "false" SaveEmptyChannel: "true" SimCombs: "false" SimStuckBits: "false" StuckBitsOverflowProbHistoName: "pCorrFracOverflowVsInputLsbCell" StuckBitsProbabilitiesFname: "ADCStuckCodeProbabilities35t/output_produceDcScanSummar yPlots_ _coldTest_0p1to1p4_step0p0010.root" StuckBitsUnderflowProbHistoName: "pCorrFracUnderflowVsInputLsbCell" ZeroThreshold: 5 module_type: "SimWireDUNE” } D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, ZS parameters taken from service

New noise Histograms show noise Top is noise histogram from DetSim module Bottom is part of ADC spectrum from one wire Comment Signal is evident on wire Noise has more higher frequency than earlier D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, 20159

New zero suppression The new zero suppression is sim of that planned for online Description is at n_and_zero_suppression#35-ton-ZS-algorithm n_and_zero_suppression#35-ton-ZS-algorithm Has many parameters o Chosen values are listed below Main features Thresholds applied on RS (running sum) rather than individual chans o RS is over NS channels – Channels with ADC <= TS are included with value zero – Stuck bit channels are not included in sum or channel count – Threshold applied on RS = sum/(# included channels) |RS| > TL defines the start of a block to be retained Preceding NL channels are kept Ticks after start are retained through end of dead region plus NT ticks o Dead region is ND ticks with |RS| <= TD D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25,

Zero suppression parameters The table below gives the parameter values used here D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, NameValueMeaning NS5# of ticks in RS TS3Threshold for RS TL7Threshold to flag start of signal NL15# ticks retained before start of signal ND5# ticks to define dead region TD3-5Threshold for dead region NT3# ticks retained after dead region

Choosing the signal threshold (TL) I looked at one MC sample Single muons with p = 4 GeV (MIP) One APA plane shown here Results Following plots show the raw signals, RS and |RS| Suppress everything except around |RS| > TL TL = 7 keeps all signals and no BG D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25,

Raw signal w/o ZS D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25,

Running sum D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, RS

|Running sum| D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, RS

Defining dead region Dead region is specified by ND and TD Tick is dead if ND preceding channels have |RS| <= TD Following pages show plots of dead ticks o In practice, live (not dead) channels are plotted as black – White regions are dead o Live fraction away from the signal is shown with each plot o Results shown varying TD from 3 to 5 Results Region around signal is always live Retained dead region and tail look dead: mix of small negative and positive signals Live fraction is small in all cases D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25,

Raw signal w/o ZS D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25,

Live regions: ND = 3 D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, %

Live regions: ND = 3.5 D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, %

Live regions: ND = 4 D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, %

Live regions: ND = 5 D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, %

Zero suppression Following page shows application of 35t ZS I.e. the new simulation of the online algorithm Parameters are those listed earlier (and on the plot) Result The ZS is very effective: retains all signal and suppresses all BG About 40 ticks are retained in each channel Assuming 1 muon/4000 ticks (see my Nov 4 plots), this means we keep 1% of ticks. Caveats o Actual noise may be much worse o And vertical muons may deposit more energy o And induction planes have wider signals But we might be able to meet goal of 5% retention (X20 suppression) D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25,

Raw signal w/o ZS D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25,

Raw signal after zero suppression D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, NS: 5 NL: 15 ND: 5 NT: 3 TS: 3 TL: 7 TD: 5

Raw signal after zero suppression (zoomed) D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25, NS: 5 NL: 15 ND: 5 NT: 3 TS: 3 TL: 7 TD: 5

Leading edge boundary Dead zone appears effective Trailing boundary of signals is quiet: nice mix of positive and negative small signals Leading edge not quite as nice Some regions where the boundary is all positive o Radiation in direction of APA or just noise? o May want to have more signals on the leading side Should we also use dead zone to also define leading boundary? o JJ is looking at this D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25,

Summary/conclusions I continue to develop ZS (and compression) code Changes at present in dunezs Plan to move some/all to dunetpc Interfaces for ZS and compression and SimWire module for these Implementations of legacy and 35t ZS Implementation of replacement and Huffman (TBA) compression All are implemented as art services Legacy ZS compared with old version Small discrepancy remains New noise parameterization has been introduced By Jonathon Propose to use that and 2X that for low and high level noise 35t ZS Simulation code in place Results of first study reported o Single beam-directed mu at center of TPC, low noise o ZS is very effective (no BG, high signal efficiency) o Parameter set proposed Idea for improving algorithm: add dead zone on leading side D. Adams, BNL ZS simulation status DUNE 35t sim/reco November 25,