1. ATLAS PESA Meeting 20/11/02 1 To do: di-muon & full-scan triggers 1) Di-muon trigger at L=2x10 ^33, introducing full scan at lower luminosity To do: Update di-muon trigger rates based on full simulation of signal and background (in conjunction with muon trigger group) – what can we do for TDR? Move LVL2 and EF algorithms to new selection framework – in progress Update LVL2 full-scan studies using DC1 data – first with IDscan + B(  or D s (  Re-do EF studies using DC1 data – done as part of offline work? Measure time-saving for RoI-based reconstruction in EF – use seeded xKalman Update resource estimates based on test-bed measurements using new selection framework and including conversion from byte-stream – extrapolate from e-gamma slice for TDR? Measure trigger rates and trigger selection efficiencies for J/  (  ) and B - >  triggers using fully simulated events and appropriate LVL2 and EF algorithms – post TDR Devise strategy for selecting rare decay channels, B - >  X, at EF – status?

2. ATLAS PESA Meeting 20/11/02 2 RoI guided B-trigger 2) RoI guided B-trigger, possibly with addition of full-scan at lower luminosity Current Status: Preliminary studies using fast simulation Rough c.p.u. resource estimates (ATL-COM-DAQ-2002-013) In RoI guided scheme, the main factors driving resource requirements are: muon trigger rate & muon algorithm time Jet RoI multiplicity, Jet RoI Size, time for ID reconstruction in Jet RoI (LVL1 & EF) => Important to confirm RoI multiplicities with full simulation => Need full simulation to determine trigger efficiency for signal channels

3. ATLAS PESA Meeting 20/11/02 3 RoI guided B-trigger To do: Measure multiplicities for low E T LVL1 Jet RoI using full simulation (in conjunction with LVL1 group) - essential for TDR Measure multiplicities for low E T LVL1 e/gamma RoI using full simulation(in conjunction with LVL1 group) - essential for TDR Measure efficiencies for low p T e + e - from J/  in conjunction with e/gamma trigger group) – start using fake RoI? or can we already use the LVL1 RoI? Measure trigger rates and efficiencies for B(  ) and B(D s  (KK)  ) signal channels– start using fake RoI? or can we already use the LVL1 RoI? Measure EF execution times for RoI-based reconstruction (see previous page) Update resource estimates – algorithm execution times from running algorithms offline, overheads from e-gamma slice on Test-bed