Triggers, streams and skims for DTs

Triggers, streams and skims for DTs

S. Goy López (CIEMAT)

Based on work by many!

MBW 28/09/2010 S. Goy Lopez 2

Trigger We have just deployed 4E31 menu and entered the Run2010B era. Change to

38X. Example run 146710 (Sun-Mon night)

Lumi ~3.0E31 (integrated ~140 nb-1 in ~1h30) L1 rate ~46 kHz CMSSW_3_8_1_HLT13 Run2010/v7.1/HLT/V1

Some rates HLT_Activity_DT ~4Hz HLT_Activity_DT_Tuned ~3 Hz HLT_L1MuOpen ~2Hz HLT_L1MuOpen_DT ~2Hz HLT_Mu5 ~1Hz HLT_Mu11 ~8Hz HLT_DoubleMu3 ~3.5Hz

Go to Express Stream.


Streams

Used for calibration/ performance studies

New: Keep L1A with only trigger info. Useful for trigger studies

http://cms-project-confdb-hltdev.web.cern.ch/cms-project-confdb-hltdev/browser/


Express Stream Express stream

~ 10 Hz of muons, mainly at high pt

Small reconstruction delay

Being used for calibration and performance studies.

Basis for offline DQM quality assignment


Commissioning PD DT Activity

paths are the major contributors

DT muon skim is run on this PD.


Trigger evolution 6E31 Trigger menu for 6E31 might be last of this year (…)

For latests plans see yesterday’s TSG-Coordination meeting http://indico.cern.ch/conferenceDisplay.py?confId=79201

For L1 see I. Mikulec’s presentation (and next slide)

For HLT all info in theese twikis:https://twiki.cern.ch/twiki/bin/viewauth/CMS/TriggerMenuDevelopmenthttps://twiki.cern.ch/twiki/bin/view/CMS/TMDLumi6E31v4(5) Express Stream:

Mu15 ~5 Hz, DoubleMu3 (?) ~6Hz

Commissioning PD HLT_Activity_DT ~ 3 Hz HLT_Activity_DT_Tuned ~5 Hz


Trigger evolution L1 6E31


Recent changes to HLT_Activity_DT Including RPC. Approved at TSG on 29/07/2010 Proposed modification: want to collect a more

generic muon barrel activity sample Proposed implementation: Find at least 5 layers with

hits in one DT chamber AND (a DT primitive in the same chamber OR an RPC trigger (with loose match in eta, phi, BX range [-1:+1]) DT_Digis AND (DT primitive OR RPC trigger) where "RPC trigger" is any RPC barrel candidate found in

the GMT readout record.


Recent changes in DT-Skim Muon DT skim runs on Commissioning PD Centrally produced at T1 and shipped to CAF Output RAW_RECO format Two components:

Trigger: Requires L1_MuOpen OR HLT_Activity_DT bit Same filter as HLT_Activity configured in a looser way (only layer hit

requirements, no request on DT primitives or RPC trigger) Needed to be updated in 38X to account for modifications on

Activity_DT filter for RPC inclusion. Trigger part includes now OR HLT_Activity_DT_Tuned as well Filter requires >4 DT chamber layers hit

Note: This is basically selecting back the HLT_Activity_DT_(Tuned) triggers that go into that PD.

Skimming efficiency ~33%... for a run taken in August (efficiency depends on exact composition of Commissioning PD)


Other DT workflows DT Ntuples & extra skim. Saves only relevant info from DT

DPG skim (commissioning)(https://twiki.cern.ch/twiki/bin/view/CMS/DtNtuples )

Produced as soon as a new run appears in the muon DPG skim Select events with at least a reconstructed DT segment OR a

reconstructed muon (any kind of muon anywhere) Select collision events with a good offline vertex

A golden skim in preparation. Selecting a sample of muons from Z decays. Output RAW-RECO

DT AlCaReco Run on Express and Muon dataset on T0 and migrated to CAF. Saves only relevant info, can be run on whole statistics. Selects good muon from collisions (in 39, to be backported)


Some other interesting workflows More skims produced from MinimumBias dataset: See

http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/DPGAnalysis/Skims/python/MinBiasPDSkim_cfg.py?view=markup

Muon POG skim. Output RECO At least one reco muon

Val Skim. Output RAW-RECO Selects at least one muon satisfying isGlobalMuon && isTrackerMuon &&

pt > 3 TPG skims: Performance skims for Trigger Group. Output RAW(https://twiki.cern.ch/twiki/bin/view/CMS/TpgSkim)

GlobalPromptTight (is a global muon, global track chi2/ndof < 10, at least one valid muon hit)

At least 10 valid tracker hits . More than one pixel layer hit Tracker track |d0| < 2 cm, chi2/ndof < 5, |dZ| < 30 cm


Back Up


Some trigger rates Example run 146710


Useful information Run Registry: list of runs taken, from which LS the tracker was on and whether stable beams declared.

http://pccmsdqm04.cern.ch/runregistry/ https://twiki.cern.ch/twiki/bin/viewauth/CMS/DQMRunRegistry#Access (access from outside CERN)

Run Summary (Detailed run info, L1 and HLT Rates, plots rates per LS etc) https://cmsdaq0.cern.ch/cmswbm/cmsdb/servlet/RunSummary

First collisions twiki by PVT (skims, etc) https://twiki.cern.ch/twiki/bin/viewauth/CMS/FirstCollisionsAnalysis

L1 and HLT trigger settings (Ivan, Emmanuelle)http://indico.cern.ch/conferenceDisplay.py?confId=75542

L1 twiki (FAQs, how to access bits, examples of filters, L1 menus, info on L1 technical bits) https://twiki.cern.ch/twiki/bin/viewauth/CMS/SWGuideL1Trigger HLT https://twiki.cern.ch/twiki/bin/viewauth/CMS/TriggerStudies Datasets/ Streams (from terminal knowing key: edmConfigFromDB --orcoff --configName

cdaq/special/CirculatingBeam09/v5.1/HLT/V2 |hltDumpStream) https://twiki.cern.ch/twiki/bin/viewauth/CMS/DatasetsStreamsCollisions2009


Definitions: Streams, Datasets, Skims At P5, from storage manager (SM), based on trigger bits,

different streams defined and sent to T0. Can follow different reconstruction logics: Stream A (main physics stream, standard reprocessing) Express Stream (express reprocessing) AlCa, Monitoring, etc…

Within given stream Primary Datasets (PD) defined at HLT at SM, based also on HLT bits.

Secondary datasets (SD) defined at T1 from PD, based on HLT bits. Shipped to T2s.

Central skims (CS): run centrally at T1s on PD, can use also reco information. Shipped to T2s


CMS data workflow. DT plans

New AlCaReco from ES (high pt threshold) to derive/monitor new calibration constants at CAF

New AlCaReco from prompt reco (also low pt) to study/monitor calibration/ synch

Prompt feedback group use data at CAF (ES/AlCaReco/Skims)

Skim


New AlCaReco New AlCaReco workflow specific for DT needs Digis in Output in 36X Need to run on Express Stream for computation/monitoring of calibration

constants. This can be done on high pt muons. Need ~10Hz in order to obtain a proper calibration within 12h delay.

Propose to use at StartUp L1MuOpen, L1Mu. At 8E29 migrate to HLT_Mu5 if available (interest in having L3 muons) For higher luminosities go to higher muon threshold in HLT

Run also on prompt reco for monitoring and studies with higher stat, with higher latency and/or using lower pt muons.

Workflow can be used for DT calibration, synchronization and prompt feedback.


DT Activity paths in HLT HLT_Activity_DT path inserted in menu

Study/Recover DTTF inefficiencies at sector borders

Collect very low pt muons arriving only at MB1 (trigger on single station)

Find at least one trigger primitive in any of MB1, MB2, MB3 confirmed with at least one chamber with >5 layers hit.

Existing activity path will need to be prescaled at high luminosities

A tuned path can be more restrictive (cleaner) and no need to be prescaled.

Approved Proposal at last TSG: Run DT Activity selection on only in sectors 1 and 12. R Due to geometry sectors 1,12 small cosmic bg Useful for generic DTL1 trigger studies

regarding low pt and sector border inefficiencies

S.G.L. et al

Standard DTTF trigger: extrapolation and matching of segments in different stationsMinimum track quality is two stations


Muon seeds https://twiki.cern.ch/twiki/bin/viewauth/CMS/SWGuideL1GMTEmulator All L1 muon triggers have L1 muon-quality requirements, unless explicitly specified.

L1_SingleMuX 1 Muon with pT > X GeV/c , quality codes : 4 or 5 or 6 or 7 L1_DoubleMuX 2 Muons with pT > X GeV/c, quality codes: 3 or 5 or 6 or 7 L1_SingleMuOpen 1 Muon with quality 2, 3, 4, 5, 6 or 7; no pT cut L1_DoubleMuOpen 2 Muons, each with quality 2, 3, 4, 5, 6 or 7; no pT cut Triple or quadruple muon triggers require: 2, 3, 4, 5, 6, 7

Where the quality codes mean: 7 : DT/RPC or CSC/RPC Matched candidate 6 : DT or CSC unconfirmed candidate 5 : RPC unconfirmed candidate The "Very Low Quality Type" is calculated by a LUT and can depend on regional trigger quality flags and eta. 4 : Very Low Quality Type 3 3 : Very Low Quality Type 2: Unmatched CSC and (qCSC=1 and eta>1.2 OR qCSC=2 and (eta<1.5 or eta>1.8)) 2 : Very Low Quality Type 1: Unmatched RPC and ((qRPC=0 and 1.04<eta<1.24 or eta>1.48) OR qRPC=1 and

0.83<eta<1.04 or 1.14<eta<1.24 or eta>1.36) OR (qRPC=2 and 0.83<eta<0.93 )) 1 : Halo muon: CSC requires 2 segments and looks for the difference in eta

At startup all Low Qualities Types promoted to quality 4,5,6 in order to be accepted

Date post:	08-Jan-2016
Category:	Documents
Upload:	terris
View:	29 times
Download:	1 times

Triggers, streams and skims for DTs

Documents