SWGuideTauHLT < CMSPublic

CMSPublic Web>SWGuide>SWGuideOnSel>SWGuideTriggerStudiesHowTo>SWGuideTauHLT (2007-10-05, SebastienGreder) (raw view)

<!-- /ActionTrackerPlugin -->
---+!! Tau HLT  
%COMPLETE3% 

%TOC{title="Contents:"}% 

---++ Goal of this page  

This page provides instructions for running the tau High Level Trigger. 

---++ Tau triggers  
The following trigger paths have been implemented: 
   * <nop>HLT1Tau: single Tau trigger
   * <nop>HLT1Tau1MET: Single Tau plus MET trigger (as the above one but with lower thresholds due to the presence of a MET selection even at L1)
   * <nop>HLT2Tau: Double Tau trigger (uses pixel tracks for isolation).
   * <nop>HLTXElectronTau: Electron+Tau trigger.
   * <nop>HLTXMuonTau: Muon+Tau trigger (uses pixel tracks for isolation).

On how to use the trigger bits to select events in the output module, please look at: [[SWGuideEDMPathsAndTriggerBits#Output_modules_using_trigger_res][EDM Paths SWGuide]] 

---++ Instructions for running the Tau HLT with CMSSW_1_3_1_HLT6  

==scramv1 project <nop>CMSSW CMSSW_1_3_1_HLT6== %BR% ==cd CMSSW_1_3_1_HLT6/src== %BR% ==eval `scramv1 runtime -csh`== %BR% ==project CMSSW== %BR% ==cvs co -r V_HLT6 HLTrigger/btau/test== %BR% ==cd HLTrigger/btau/test== %BR% 

Run the cfg file named ==hlt_tau_1_3_1_HLT6.cfg== (see it in the [[http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/HLTrigger/btau/test/?pathrev=V1_3_1_HLT6_BRANCH][code browser]]). All the tau triggers will be run. The output is written in the test.root file in the local area. 

For samples with two tau leptons in the final states (as Z-&gt;tautau and qqH-&gt;tautau) the <nop>TauJetMCFilter module can be used to select only desired tau decays and apply MC fiducial cuts: 
<verbatim>
module tauHadrFilter = TauJetMCFilter{
 InputTag GenParticles = VtxSmeared
        double EtTau = 0.0
        double EtaTauMin = 0.0
        double EtaTauMax = 2.5
        double EtaElecMax=2.5
        double EtaMuonMax=2.5
        double PtElec =0.
        double PtMuon=0.
        vstring includeList ={"tautau"}
#        vstring includeList ={"etau"}
#        vstring includeList ={"mutau"}
}
</verbatim>

---++ Instructions for running the Tau HLT with CMSSW_1_6_0  

==scramv1 project <nop>CMSSW CMSSW_1_6_0== %BR% ==cd CMSSW_1_6_0/src== %BR% ==eval `scramv1 runtime -csh`== %BR% ==project CMSSW== %BR% ==cvs co -r V00-00-02 <nop>RecoTauTag/HLTAnalyzers== %BR% ==cvs co -r V_1_6_0 HLTrigger/btau/test== %BR% ==scramv1 b== %BR% ==cd HLTrigger/btau/test== %BR% 

Run the cfg file named ==hlt_tau.cfg== (see it in the [[http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/HLTrigger/btau/test/?pathrev=V_1_6_0][code browser]]). All the tau triggers will be run. The output is written in the test.root file in the local area. 

For samples with two tau leptons in the final states (as Z-&gt;tautau and qqH-&gt;tautau) the <nop>TauJetMCFilter module can be used to select only desired tau decays and apply MC fiducial cuts: 
<verbatim>
module tauHadrFilter = TauJetMCFilter{
 InputTag GenParticles = source
        double EtTau = 0.0
        double EtaTauMin = 0.0
        double EtaTauMax = 2.5
        double EtaElecMax=2.5
        double EtaMuonMax=2.5
        double PtElec =0.
        double PtMuon=0.
        vstring includeList ={"tautau"}
#        vstring includeList ={"etau"}
#        vstring includeList ={"mutau"}
}
</verbatim>
Both cases 1 and 2 in HLTSetup  (under HLTrigger/Configuration/data/common) are currently working, corresponding to running off a normal digi file or a raw (+L1) file.

*ATTENTION*: the default is case 2 in HLTSetup - running off Raw files as will be standard procedure. Thus you need to provide a file containing Raw (e.g., look at the catalog DBS2) or create a Raw file yourself (using CMS.RelVal _Digi_DigiToRaw.cfg), and then run HLTtable.cfg or CMS.RelVal _HLTFromRaw.cfg off that file. Alternatively, edit HLTrigger/Configuration/data/common/HLTSetup.cff to switch to case 1 and run off a digi file, but this works only for a 152 (or higher) data/digi file. If the digi file is older, then run CMS.RelVal _Digi_DigiToRaw.cfg first to make a Raw file, and run the HLT in its default setting (case 2) from that Raw file. In any case, 13x or older files can't be used as they can't be read by 16x. 

---++ Instructions for analysing the Tau HLT with CMSSW_1_6_0  

In order to analyze HLT ouput, the following code is a good skeleton to start with:

<verbatim>
scramv1 project CMSSW CMSSW_1_6_0
 cd CMSSW_1_6_0/src
 eval `scramv1 runtime -csh`
project CMSSW
 cvs co -r v00-01-05 RecoTauTag/HLTAnalyzers 
scramv1 b -j 4 BUILDVERBOSE=''
cd RecoTauTag/HLTAnalyzers/test 
cmsRun RunHLTTauAnalyzer.cfg
</verbatim>

Tau-trigger paths and different collections as well as monte-carlo tau decays can be tuned from the RunHLTTauAnalyzer.cfg file.
==RecoTauTag/HLTAnalyzers/HLTTauAnalyzer.cc== is extensively commented for trigger/CMSSW beginners

#ReviewStatus 
---++!! Review Status  

| *Reviewer/Editor and Date (copy from screen)* | *Comments* |
| Main.SimoneGennai - 02 Apr 2007 | last content editor |
| Main.JennyWilliams - 10 Apr 2007 | non-twiki word tidying |

<!-- In the following line, be sure to put a blank space AFTER your name; otherwise the Summary doesn't come out right. -->

%RESPONSIBLE% Main.SimoneGennai %BR% %REVIEW% Reviewer

Attachments

Topic attachments
I	Attachment	History	Action	Size	Date	Who	Comment
ppt	TwikiTauHLT.ppt	r2 r1	manage	33.0 K	2007-03-06 - 11:54	SimoneGennai

Topic revision: r32 - 2007-10-05 - SebastienGreder

CMSPublic

User Support
Reference Manual

Main Areas

- Detector Reco Objects
- Tracks
- Ecal Reco
- Hcal Reco
- Muon System Reco
- Vertex Reco
- Physics Reco Objects
- Muons
- Electrons/Photons
- Jets, missing ET
- b Tagging
- Particle flow
- Tau-ID
- Analysis/Software Tools
- Physics Tools
- MC Truth Tools
- Visualization
- Trouble Shooting
- Code Performance
- Port to New Release
- CRAB
- Analysis Examples
- Higgs
- SUSY/BSM
- Electroweak
- Top
- Heavy Ions

Public webs

- Cern Search
- TWiki Search
- Google Search
CMSPublic All webs

Copyright &© 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback