1. Event Filter and Trigger Menu L=10 31 cm -2 s -1 Sergio Grancagnolo on behalf of the Muon Trigger software group

2. Outline News on EF algorithm implementation (for rel. 13.x.x) HLT Data Quality assessment EF performance studies –resolution/efficiency –EF rates –status of the studies of muons from  decay Muon trigger rates and trigger menu for LHC startup

3. Two different running modes:Seeded Reconstruction performed only in the geometrical regions provided by the RoIs of previous levels. Full scan Full reconstruction, ~equivalent to the offline working mode LVL2 (muFast) Moore Algs LVL1 MuIdStandAloneAlgs TrigMoore Seeding Algs MuIdCombinedAlgs Hypo Alg TrigMoore – a reminder Seeding Algorithms assume the seed is from LVL2 or a LVL1 ROI Full functionality in barrel and end- caps 3 istances of TrigMoore called by the steering, for reconstruction in the MS, extrapolation to the IP and combination with ID tracks TrigMoore attaches to the TE a "TrigMooreFeature" for each ROI, accessed by TrigMooreHypo for p T test TrigMoore records in SG the TrigMooreFeature per each ROI and all reconstructed tracks in the event in a single container for conversion in Trk:Track format and subsequent output in ESD and AOD LVL2 (muComb) LVL2 ID Offline ID

4. MuonEF in Rel 13.0.10 Migration to new HLT Steering (DONE) –Both FEX and Hypothesis algorithms Migration to Configurables (DONE) –TrigMoore configurables py classes available in 3 flavours (MuonSpectrometer, Extrapolated and Combined Tracks) –New style EF muon sequences (including ID) added in TrigHypothesis/TrigMuonHypo Migration to new EDM (DONE) –TrigMoore uses the standard reconstruction input object (PrepRawData). –The Moore offline algorithm organization has been adopted also by TrigMoore Use of EF version of ID for combined MS-ID tracks (DONE) –MuidCombined adapted to get as input EF-ID tracks. –Replacement of the previous implementation in wich EF ID and offline ID (New Tracking or iPatRec) was used.

5. MuonEF in Rel 13.0.10 Implementation of REGTESTs for Monitoring and Validation (DONE) Monitoring Histo in Hypo Algo (DONE) Definition of jobOptions to include Muon EF in ATN test (DONE) Bug Fix- Fix for duplicated python modules in genConf (DONE- to be collected right after 13.0.10) Bug Fix- Problem in Persistification (appeared in 13.0.X nightly) Fixed in 13.0.10

6. Muon HLT Data Quality

7. Preliminary considerations on DQ monitoring and assessment for the muon slice presented at TDAQ Data Quality Wshop in Zeuthen (February 28-March 1 2007), focusing on LVL2 and EF, in online/offline e.g. for EF online monitoring: hit #/track per tecnology; geometrical track parameters; pt spectrum; track quality (  2 ); Muon Slice Data Quality (I) residual distributions; matching with ID; combined tracks/moore tracks; ratio of positive/negative tracks; matched hits/total hits in the seed region; Monitoring activities are going to be organized for LVL1/2/3 in the appropriate environments, to use general tools and DQ Monitoring framework, to move the first steps towards muon trigger slice DQ Nothing exists for the moment for Muon Slice DQA but what implemented for monitoring during 2004 test beam (for LVL2) and the test of the trigger slices on the pre-series machines at Point 1 in december 2006 (for EF) can be a starting point for Data Quality Monitoring

8. e.g. TrigMoore histos from the last technical run Trigger/TrigAlgorithms/TrigMoore/src/TrigMooreHisto.cxx (here obtained running the jobOptions prepared for the on-line with a bytestream file containing 50 top events as input: muons are selected by the LVL2 and the EF muon algorithms) Muon Slice Data Quality (II) completed in release 13 for TrigMoore Hypothesis algos

9. EF Performance studies

10. Sample and releases Single mu sample centrally simulated on lcg-dq grid (CSC production) –mixed charge; –p T from 2 to 200 GeV/c –total statistics …… Reconstruction with a dedicated sw chain in 12.0.6 –Muon Trigger slice only LVL1 emulation, (100% of the statistics processed with standard LVL1 configuration, part of the low pt points re-processed with low thresholds) LVL2: mufast, IDscan, muComb EF(seeded by LVL2): trigmoore + EF ID algo Hypothesis algorithms disabled –Private AA NTuple production using grid tools (GANGA) on Napoli Tier2 storage elements (mostly by Napoli group) –Used for both LVL1 (Napoli, Tokyo) and EF (Lecce, Napoli) studies –Main goal: CSC note efficiency, resolution, single muon trigger rates

11. Sample and releases Single  p T (GeV) 22.533.544.5567 10 6 events 1.21.41.31.20.780.50.670.550.21  tot ~8 x 10 6 events in the range 2-7 GeV Note that only few single muon events, with pT=3÷5 GeV, pass the LVL1/LVL2 mu6 threshold and no one is reconstructed by the EF. Even a 10 7 sample of low p T events is not allowing to estimate the EF efficiency with great precision below the 6 GeV threshold.

12. Efficiency and resolution curves (standard LVL1 configuration) barrel EF MuId Combined efficiency curves w.r.t. LVL2 (muComb) p T (GeV) 6 GeV 8 GeV 20 GeV40 GeV p T (GeV) barrel EF resolutions MuidStandAlone TrigMoore MuidCombined

13. EF MuId Combined Resolutions Endcap Overlap Very FwdAll

14. Other EF Muon Trigger rates 6 GeV 10 33 cm -2 s -1 Barrel (Hz) Endcap (Hz) beauty641845 charm327426 top0.050.07 W2.94.0  /K 19181462 TOTAL28892737 8 GeV 10 33 cm -2 s -1 Barrel (Hz) Endcap (Hz) beauty172291 charm77134 top0.060.05 W2.83.9  /K 281313 TOTAL533742 20 GeV 10 34 cm -2 s -1 Barrel (Hz) Endcap (Hz) beauty73118 charm2846 top0.270.32 W22.332.6  /K 5048 TOTAL173244 40 GeV 10 34 cm -2 s -1 Barrel (Hz) Endcap (Hz) beauty2.54.5 charm0.871.6 top0.07 W3.97.1  /K 0.20.3 TOTAL7.513.6

15. EF Efficiency curves (for low pt regime) EF (MuId CB) efficiency w.r.t. LVL2 (muComb) 35 35 p T (GeV) p T threshold at 4 GeV corresponds to a totally open LVL1 window – EF effective threshold is 3 GeV/c p T threshold at 5 GeV has a cut lowered by 2 times the resolution corresponding at 5 GeV (as for higher thresholds) “4 GeV” 5 GeV barrel

16. Low p T thresholds single muon rates “4 GeV” 10 31 cm -2 s -1 Barrel (Hz) Endcap (Hz)  /K 13380 beauty1921 charm1112 top6∙10 -4 8∙10 -4 W0.030.04 TOTAL163113 5 GeV 10 31 cm -2 s -1 Barrel (Hz) Endcap (Hz)  /K 4430 beauty1113 charm67 top5∙10 -4 7∙10 -4 W0.030.04 TOTAL6149 Luminosity: L = 10 31 cm -2 s -1

17. Trigger Menus Proposal for L=10 31 cm -2 s -1 L1 trig. item RateLVL2RateEFRate MU4~1 kHz μCombTrigMoore TrigDiMuonDiMuon PS/PT1 HzPT1 Hz MU6227 Hz μComb80.8 HzTrigMoore56.3 Hz InDet onlyPS/PT μFast only99.7 HzPS/PT 1 HzPT1 Hz MU10112 Hz μCombTrigMoore~10 Hz PS/PT1 HzPT1 Hz

18. Trigger Menus Proposal for L=10 31 cm -2 s -1 L1 trig. item RateLVL2RateEFRate MU1519 Hz μCombTrigMoore~2 Hz InDet onlyPT μFast onlyPT PS/PT1 HzPT1 Hz MU2014 HzPT14 HzPT14 Hz MU408 HzPT8 HzPT8 Hz 2MU4~9 Hz???PT 2MU64 HzPT4 HzPT4 Hz 2MU10~1 HzPT~1 HzPT~1 Hz 2MU20< 1 HzPT< 1 HzPT< 1 Hz 2MU40< 1 HzPT< 1 HzPT< 1 Hz Express streams

19. Trigger efficiency from Z → μ + μ - Double Object (DO) method 1-2 % statistical uncertainty with few pb -1 data Differential (η,φ) trigger efficiency determination CSC AOD analysis is going to be finalized Double Object with orthogonal Signature (DOS) method Backgrounds from BBμμX, Wμv, Zττ Different reconstruction modes

20. Muons from  /K

21. Strategy extract from minimum bias and dijets of various energy a global p T vs  distribution for pions and kaons, re-weighting to a common value of the integrated luminosity Use the particle-generator to generate single pions according to the previous distribution simulate the decay of pions with G4 saving only events were the pion decay before the muon spectrometer study a procedure to identify and reject this kind of muons

22. Event Sample File NameEvents Cross Section (mb) minimum bias csc11.005001.pythia_minbias.evgen.EVNT.v11004202._xxxxx 12420092E00 J1 csc11.005010.J1_pythia_jetjet.evgen.EVNT.v11004201._xxxxx 2422871.376E00 J2 csc11.005011.J2_pythia_jetjet.evgen.EVNT.v11004201._xxxxx 2575089.327E-02 J3 csc11.005012.J3_pythia_jetjet.evgen.EVNT.v11004201._xxxxx 302995.884E-03 J4 csc11.005013.J4_pythia_jetjet.evgen.EVNT.v11000401._xxxxx 404003.084E-04 J5 csc11.005014.J5_pythia_jetjet.evgen.EVNT.v11000401._xxxxx 50501.247E-05 J6 csc11.005015.J6_pythia_jetjet.evgen.EVNT.v11000401._xxxxx 500003.604E-07 J7 csc11.005016.J7_pythia_jetjet.evgen.EVNT.v11004201._xxxxx 50505.707E-09 J8 csc11.005017.J8_pythia_jetjet.evgen.EVNT.v11004201._xxxxx 101002.444E-11 Particle selection requiring:  PDG code |  |<2.7 pT>500MeV generation at the interaction point (0.,0.,0.) and filling a two-dimensional histogram of p T vs , one entry for each pion.

23. pT vs  distributions Minimum bias Dijets J8 Some existing correlation between p T and  requires a generation according to the 2-D distribution The solution that I adopted is to slice the 2-D histograms in p T bins and simulate using the 1-D projections in p T and  A tool was developed to force all the generated pions to decay: the PionDecayer Supposing an efficiency  =10 -4 between 2.5 GeV and 7.5 GeV, and a granularity of 500 MeV, to extimate an error of  10%  10 6 events needed in each bin If only ~1% of the pions decays in the volume before the calorimeter at least 10 9 events should be generated The red curve, mu6 eff. at EF, is estimated with 10 p T points (2GeV/c – 8 GeV/c) with 10 6 – 0.5·10 6 single muon each but events passing LVL2 are 30 at 3 GeV/c, 500 at 4 GeV/c, 3600 at 5 GeV/c, 350k at 6 GeV/c Single muon efficiency

24. Produced sample no available tools to randomly extract from a 2D distribution –solution: slice the 2D distribution in pt bins (of ~same content) and generate according to the 1D distributions of pT and Eta From PANDA, centrally simulated files: Task name Task IDReq JobsDone JobsTotal events Prio GridStatus Timestamp misal1_mc12.007180.singlePion_pTSlice_20_of_30.digit.v12000502 7822 500 500 25000 100 osg done Apr 18 10:04 misal1_mc12.007162.singlePion_pTSlice_2_of_30.digit.v12000502 6296 1600 1600 80000 100 osg done Mar 1 12:34 misal1_mc12.007163.singlePion_pTSlice_3_of_30.digit.v12000502 6295 1400 1400 70000 100 osg done Mar 1 12:33 ……… misal1_mc12.007189.singlePion_pTSlice_29_of_30.digit.v12000502 6270 100 100 5000 100 osg done Mar 1 11:46 misal1_mc12.007190.singlePion_pTSlice_30_of_30.digit.v12000502 6269 100 100 5000 100 osg done Mar 1 11:45 TOTAL: 25.800 files 1.065.000 events ~1.7Tb Since, for a given pion direction, the decay is forced into a definite path length L, the single event probability is

25. Following steps… Since full statistics has become available all efforts have been directed to apply the muon slice and the standard ntuple analysis to the single  sample –with some addition specific to the    case keep track of the muon mother and its decay vertex keep track of the links between a combined reconstructed muon and its ID and MS seeds, etc...) Fixes made by Alan and migration of methods from MuidMatch to MuidTrack first attempt: –copy from osg grid to castor, submit jobs to lxplus queues for running the specific reconstruction + analysis code  turned out to be unaffordable mostly due to castor access too slow and unstable use of grid infrastructures absolutely necessary ! –the solution: use lcg-dq after replicating the files to Napoli tier-2 affordable but still very time consuming; copy from castor to NA tier-2 took 4/5 days only for higher pT slices (20-30) –reconstruction jobs submitted on a small part of these replicas A long process for the study of a critical issue: now all necessary input ready to perform the analysis and get some results

26. Problems Many problems encountered to complete the analysis chain: –Last simulation job finished ~ half april –Copy output to castor from US grid ~1 week –Many attempts to run the muon trigger slice Run athena jobs directly on castor  failed Copy from castor to local nfs  local disk failed Replicate from castor to european grid  ongoing Running muon trigger slice  ongoing Run analysis macro  ongoing

27. Conclusions Many important steps since last T&P week Performances under control Data quality and trigger menus under study Still waiting to finish the study on muons from single pion sample, but many technical problems –grid tools are already very important Stay tuned for new results on this topic