How-to: HI Trigger Table Setup in CMSSW
Complete:
Goal of this page
This page explains how to obtain the configuration file necessary to run the Heavy Ions High-Level Trigger (HLT) menu offline on RAW data. For a general description of the CMS HLT please see the HLT page in the CMSSW SW guide
here.
Instructions
Starting from CMSSW_3_X_X the HI HLT Trigger menu is stored and developed in the configuration data base
ConfDB.
To browse the available HLT menus for a given CMSSW release in ConfDB use the
HLT config browser
. In the config browser for each major CMSSW release you will find the pp configurations for various luminosity and conditions (8E29, 1E31, GRun) and the HI configuration HIon. The available HLT configurations are stored with a version number; please use the highest version number for your studies.
For closed CMSSW releases the final HLT table can be obtained by checking out the HLTrigger/Configuration package and executing the cmsDriver.sh shell script in the test directory. This will produce all necessary configuration files to run the Release Validation of the HLT and also all standalone configurations needed to run the HLT.
A specific configuration can also be extracted directly from ConfDB by using the
edmConfigFromDB tool.
For example:
edmConfigFromDB --configName /dev/CMSSW_3_1_0/pre11/HIon_V13/V1 --format Python > MyHIon.py
The appropriate configName can be identified by consulting the
HLT config browser
.
To execute the HI HLT on a given raw data file just edit the Source fileNames in your MyHIon.py config file and run it with
cmsRun MyHIon.py
Another tool called
hltGetConfiguration
also exists with functionality shown in
the following example
:
hltGetConfiguration --process TEST --unprescale --full --offline --mc /users/cer/HI_ActivityPaths/V3 > HIHLT_mc.py
The various flags that can be used are described
in this python code
. One useful setting is
--cff
, which creates a cff for inclusion in e.g. cmsDriver, rather than a full cfg.
Additional instructions for specific versions
Setup for CMSSW_3_1_2
CMSSW_3_1_2 needs a patch for the HI Tracking region used in the vertexing.
Check out and build the RecoHI/HiTracking package, with the tag V01-00-04
cvs co -r V01-00-04 RecoHI/HiTracking/
scramv1 b
Setup for CMSSW_2_1_0
(Now obsolete)
Check out the HI Vertexing
cvs co -r V00-00-03 RecoHI/HiTracking
Check out the Muon L3 code
cvs co -r V00-02-00 RecoHIMuon/HiMuSeed
cvs co -r V00-02-00 RecoHIMuon/HiMuTracking
cvs co RecoHIMuon/HiMuPropagator (head version)
Compile everything
scramv1 b
The HLT Table needs raw data to run on.
15k Pb Pb min bias rawdata can be found in dcache at MIT:
/pnfs/cmsaf.mit.edu/hibat/cms/users/cer/digi2raw_210pre9/MinBiasPbPb/
To generate raw data yourself from your favorite gen-sim file please use the default release-validation digi2raw configuration. To get it check out HLTrigger/Configuration:
cvs co -r CMSSW_2_1_X HLTrigger/Configuration
and use:
HLTrigger/Configuration/test/RelVal_Digi_Digi2Raw_cfg.py
To get a running HI_HLT configuration you need to get the standard pp reconstruction sequences we use from the configuration data base and add the heavy ion specific modules and paths to it. Here is a script to do that:
getHIHLT.csh
The script should give a running configuration for all HLT supported CMSSW_2_1_X versions.
To run the script copy python fragment containing the HI specifics to the same directory:
HLT_HI_fragment.py.txt (remove the .txt extension added by twiki)
The script is set up to get a HLT Table for CMSSW_2_1_0. To get a configuration for another CMSSW_2_1_X release, edit the config name option to edmconfigfromdb:
edmConfigFromDB --configName /dev/CMSSW_2_1_0/HLT
The output of the script is a python config file containing all modules and paths to run the HI HLT. Just point the
PoolSource files Names to your copy of the rawdata and run the HLT Config:
cmsRun HI_HLT_Table.py
Review status
Responsible:
ChristofRoland