Muon HLT Tree Utility

Complete: 2

Introduction

The Muon HLT Tree Utiltiy was developed for in-depth, on-the-fly analyses of the Muon HLT performance. The tree utility contains information from the event, the L1 and HLT muons, and the simulated muons and their associations to the HLT muons, which allows the tree utility to be used for studies of rates, trigger and algorithm efficiencies, and studies of the distributions at each trigger level.

In its current implementation, the tree utility is an EDAnalyzer that produces ntuples containing 2 trees:

  • MuTrigData: contains the event, trigger, and HLT Muon information described briefly above and in more detail in the attached documenation.
  • MuTrigMC: contains, in addition to the contents of MuTrigData, important sim muon quantities, including their associations to the HLT Muons

The tree utiltiy has been implemented since the 2.0.X CMSSW releases.

Documentation

Installation Instructions

2.2 Release Cycle

cvs co -r V00-00-00 -d Workspace/MuonHLTTreeUtility UserCode/JRVlimant/cmssw/WorkSpace/MuonHLTTreeUtility
cvs co -r V00-00-00 -d RecoMuon/MuonXRay UserCode/JRVlimant/cmssw/RecoMuon/MuonXRay
scramv1 build

Add these line at the end of the main configuration file. For the muon tree utility, there are two paths

  • MHTU_Path: which produce all necessary objects necessary for the tree.
  • MHTU_EndPath: which run the timing module and the tree maker itself.

process.load('Workspace.MuonHLTTreeUtility.muonHLTTreeUtility_cff')
process.schedule = cms.Schedule (process.MHTU_Path)
process.schedule.append(process.MHTU_EndPath )

3.X Release Cycle

cvs co -r V00-04-00 -d Workspace/MuonHLTTreeUtility UserCode/JRVlimant/cmssw/WorkSpace/MuonHLTTreeUtility
cvs co -r V00-01-00 -d RecoMuon/MuonXRay UserCode/JRVlimant/cmssw/RecoMuon/MuonXRay
rm RecoMuon/MuonXRay/python/dqm_cff.py
scramv1 build

In the configuration file of a process which already load the HLT configuration, add

from Workspace.MuonHLTTreeUtility.muonHLTTreeUtility_cff import insertMHTU
insertMHTU(process)
This creates the muon open HLT path to the path MHTU_Path, which is added just before the first endpath. The end path MHTU_EndPath is appended to the schedule, to come after all end paths.

OR

cmsDriver.py MHTU -s L1,HLT:8E29 --processName MHTU --conditions FrontierConditions_CMS.GlobalTag,STARTUP31X_V7::All --filein HLTDEBUG-file.root --no_output --customise Workspace/MuonHLTTreeUtility/python/muonHLTTreeUtility_customise.py --no_exec
and edit the produced configuration file for the input file and number of events to run over.

Using the Tree Utility on Real Data

The tree utility can also be run over real data, provided that the RAW data is included in the event content. Starting with the tagged version V00-03-00, the configuration includes the file muonHLTTreeUtilityForData_cff.py file. As with the 3.X release cycle, the tags to check out are:

cvs co -r V00-04-00 -d Workspace/MuonHLTTreeUtility UserCode/JRVlimant/cmssw/WorkSpace/MuonHLTTreeUtility
cvs co -r V00-01-00 -d RecoMuon/MuonXRay UserCode/JRVlimant/cmssw/RecoMuon/MuonXRay
scramv1 build

The most straightforward method for generating a configuration file that will re-run the HLT over the data is to execute the following:

cmsDriver.py step2 -s HLT:GRun --relval 25000,100 --datatier RECO --eventcontent RECO --conditions GR09_H_V7OFF::All --scenario pp --magField AutoFromDBCurrent --filein file:dummy.root --no_exec

For the 3.3.X release cycle, the HLT_GRun_cff.py sample looks for the FEDRawDataCollections labeled "fedRawDataCollector;" which may be from "source" in the data. A simple fix is to check out the menu and replace all "fedRawDataCollector" instances with "source." From the auto-generated .py file, edit the ProcessName (to avoid naming conflicts with other processes), and add the appropriate globalTag and input files, and the number of events to run over. Finally, at the end of the file auto-generated file, add

def customise(process):
    from Workspace.MuonHLTTreeUtility.muonHLTTreeUtilityForData_cff import insertMHTU
    insertMHTU(process)
    return (process)

process = customise(process)

Using the RECO Tree Utility on Real Data

The tree utility can also be run over real data, provided that the RAW data is included in the event content. Starting with the tagged version V00-04-00, the configuration includes the file muonRecoTreeUtilityForData_cff.py file. As with the 3.X release cycle, the tags to check out are:

cvs co -r V00-04-00 -d Workspace/MuonRecoTreeUtility UserCode/AEverett/MuonRecoTreeUtility
cvs co -r V00-01-00 -d RecoMuon/MuonXRay UserCode/JRVlimant/cmssw/RecoMuon/MuonXRay
scramv1 build

The most straightforward method for generating a configuration file that will re-run RECO over the data is to execute the following:

cmsDriver.py promptCollisionReco -s RAW2DIGI,L1Reco,RECO,DQM,ALCA:SiStripCalZeroBias --datatier RECO --eventcontent RECO --conditions CRAFT09_R_V4::All --scenario pp --no_exec --data --magField AutoFromDBCurrent -n 100

Finally, at the end of the file auto-generated file, add

def customise(process):
    from Workspace.MuonRecoTreeUtility.muonRecoTreeUtilityForData_cff import insertMRTU
    insertMRTU(process)
    return (process)

process = customise(process)

Note: you can also add this to the end of the auto-generated configuration file generated for the MuonHLTTreeUtility above.

Muon HLT Tree Utility SandBox

Creator's notes: The tree utility is still under development, and much remains to be done. In addition to the quantities currently stored, some of the other things to be added include the following items on this wish list

  • DONE L3 track information for testing the matching of L2 muons to tracks
  • DONE Execution time
  • Filter cuts used at each level
  • DONE Absolute size of errors for the L2 error matrix
  • DONE SimToReco association

For using the tree with data, the following should be implemented:

  • Taking the trigger menu from the run automatically
  • Automating MHTU cmsDriver step with "data" option

Other useful discussions for the development of this utility include file size, code status (cleanup),

Review status

Reviewer/Editor and Date (copy from screen) Comments
-- TomDanielson - 21 Oct 2008 created page

Responsible: Tom Danielson
Last reviewed by:

Topic attachments
I Attachment History Action Size Date Who Comment
PDFpdf HLTMuonTree.pdf r1 manage 62.1 K 2008-10-22 - 00:23 TomDanielson Documentation of variables stored in trees
Edit | Attach | Watch | Print version | History: r16 < r15 < r14 < r13 < r12 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r16 - 2010-03-02 - ThomasDanielson
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback