1 / 14

Summary of Trigger and Physics Datasets Activities

Summary of Trigger and Physics Datasets Activities. Massimiliano Chiorboli Universita ’ di Catania Gheorghe Lungu Rockfeller University Maurizio Pierini CERN. Luminosity plan. Darin Acosta. 8e29 and 1e31 tables. R. Rossin :

britain
Télécharger la présentation

Summary of Trigger and Physics Datasets Activities

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Summary of Trigger and Physics Datasets Activities Massimiliano Chiorboli Universita’ diCatania Gheorghe Lungu Rockfeller University Maurizio Pierini CERN

  2. Luminosity plan Darin Acosta

  3. 8e29 and 1e31 tables • R. Rossin: • http://indico.cern.ch/getFile.py/access?contribId=24&sessionId=33&resId=0&materialId=slides&confId=84487 • At startup we use the 8E29 menu as developed from MC studies (+ some commissioning paths) • This 8E29 menu will then be tuned on the first s=7TeV data. We consider it as a data-validated menu for all extrapolation purposes. • Minimal MC-dependence for rate calculations • The 1E31 will also be adjusted based on the “8E29” data • Non-linear effects due to pile-up are expected to be small • The 8E29 and 1E31 menus have been designed on the s=10TeV MC to deliver ~150Hz of total rate (~2x safety) • Predictions for the same menus at 7TeV (w/o prescales nor thresholds adjustments) are about 90Hz (~3x safety) • Data will be different from all the above. Will have to adjust prescales and maybe thresholds to get to the target rates

  4. Trigger group needs input from Physics groups to decide how to evolve the menu

  5. 1e29 proposed menu • L. Apanasevich • http://indico.cern.ch/getFile.py/access?contribId=1&sessionId=1&resId=1&materialId=slides&confId=79093

  6. New Onia Triggers • C. Lourenco, H. Wohri, Z. Gecse, W. Adam, F. Teischinger, J. Kim • http://indico.cern.ch/getFile.py/access?contribId=3&resId=1&materialId=slides&confId=87593 • Set of triggers developed by the Onia group to increase the muon acceptance to very low pt • Defining the efficiency with respect to the number of J/ψ dimuons reconstructed offline, as global-global (GG), global-tracker (GT), or tracker-tracker (TT) • The existing triggers are very efficient at selecting dimuons that can be reconstructed offline as GG pairs • New triggers studies and requested by Onia group • rate 40-60 Hz for muon triggers • we will collect >100k Jpsi by the end of June

  7. New trigger proposed by the SUSY group: MHT • J. Marrouche, A. Tapper • http://indico.cern.ch/getFile.py/access?contribId=0&sessionId=1&resId=1&materialId=slides&confId=79090 • HTmiss and ETmiss are extremely similar in their calculation; the former uses clustered jets, whilst the latter uses calorimeter energy deposits. • HTmiss proposed as a complementary trigger to ETmiss. The available configurable jet threshold will provide a handle in the face of problems and may make it a more robust trigger in the search for new physics (SUSY + Exotica)

  8. Performance and triggers requested LM0 Timing studies requested by the TSG group

  9. Calorimeter spikes • Spikes observed in the calorimeter in data • spike rate > 5 GeV is expected to be ~100Hz at 1E30, needs to be rejected at HLT (~40Hz >10 GeV) • we don’t know how it scales with lumi so need to be prepared at L1 too • currently only E/gamma trigger paths require spike rejection • thresholds on JETMet, Tau sufficiently high to avoid spikes • this depends on what happens with data. • Spikes in single crystals: • Strategy for spike rejection at L1: request >1 strip in eta • J. Jackson, http://indico.cern.ch/getFile.py/access?sessionId=3&resId=0&materialId=0&confId=88158 • Strategy for spike rejection at HLT: cut on E1/E9: • A. Ghezzi, http://indico.cern.ch/getFile.py/access?contribId=1&sessionId=1&resId=0&materialId=slides&confId=79091

  10. Pixel Hit Cut • Due to “Monster Events” in data with many pixel hits, HLT timing explodes (one event took 29 s!) • cut now of Nhits < 5000 (at RECO level) • returns empty collection for events with Nhits > 5000 • any path which uses pixel info fails if Nhits > 5000 • Triggers Affected: • all Electron triggers • L3 Muon triggers • HLT_BTagIP_Jet50U • HLT_IsoTrack*_8E29 • HLT_ZeroBiasPixel_SingleTrack • H T_HighMult40 • all cross-triggers using one or more of the above

  11. Pixel Hit Cut – check for SUSY RelVal_LM1, CMSSW_333 Number of hits well below 5000 Is this check enough? Do somebody want to check special scenarios?

More Related