AlCaRecoTriggerBits

Trigger Paths in CondDB

The first selection step of all AlCaReco skims is supposed to be based on HLT paths. This should be done using the module HLTHighLevel (link) with cloning its default configuration hltHighLevel_cfi.py (link).

To allow for a fast reaction of AlCaReco production on changes in the HLT menu, the selected paths must not be specified using the parameter HLTPaths, but have to be read from the conditions database by specifying the parameter eventSetupPathsKey. A common database payload for all AlCaReco skims is available via the record = cms.string('AlCaRecoTriggerBitsRcd') as a map between eventSetupPathsKey and lists of associated HLT paths. This is integrated in the global tag (since CMSW_3_1_0_pre5).

Note about internals:

• The object stored on CondDB is AlCaRecoTriggerBits (link). For technical reasons this concatenates the list of paths stored for each eventSetupPathsKey into one string where the paths are separated by a semicolon (;). Therefore a path name containing a ';' cannot be given. (But HLT paths will probably not be named in that way...). Currently no exception is thrown, but the path name will be split when reading back from CondDB.
• Since Oracle cannot store an empty string, an empty list of paths (meaning passing all events where at least one path succeeded) is internally represented by a single ';' (since CMSSW_3_5_0_pre4).

Which HLT Paths Are Used?

The cmsRun configuration file AlCaRecoTriggerBitsRcdRead_cfg.py (link) can be used to get a printout of the map in a specific global tag. Simply overwrite the CMS.GlobalTag in the python file and run it. E.g. in plain CMSSW_3_1_0_pre5 cmsRun $CMSSW_RELEASE_BASE/src/CondTools/HLT/test/AlCaRecoTriggerBitsRcdRead_cfg.py gives the following output. Note that you have to specify the run number in the config (see the comments in it) in case the payload does not have unlimited IOV.

<snip>
#
# Run number 1 has these AlCaRecoTriggerBits settings:
#
trigger list key: 'EcalCalElectron'
paths:
'HLT_Ele15_SW_L1R', 'HLT_DoubleEle10_SW_L1R', 'HLT_Ele10_LW_L1R', 'HLT_DoubleEle5_SW_L1R'
#
<snip>
#
trigger list key: 'TkAlMuonIsolated'
paths:
'HLT_L1MuOpen', 'HLT_L1Mu', 'HLT_L2Mu9', 'HLT_Mu3',
'HLT_Mu5', 'HLT_Mu9', 'HLT_Mu11', 'HLT_DoubleMu3'
<snip>

EcalCalElectron and TkAlMuonIsolated are the keys that must match the parameter eventSetupPathsKey in the HLTHighLevel configurations of the corresponding AlCaReco skims.

New Version of AlCaRecoTriggerBitsRcdRead_cfg.py

Since V00-01-01 of CondTools/HLT (in CMSSW since CMSSW_3_5_0_pre1), AlCaRecoTriggerBitsRcdRead_cfg.py (link)

• can list all IOVs of a given tag,
• can produce an output file instead of using the message logger
• and supports output directly copyable into this Wiki page.

So check out that version, compile and play around with cmsRun src/CondTools/HLT/test/AlCaRecoTriggerBitsRcdRead_cfg.py  > /dev/null to see how it works. Watch for the file triggerBits.twiki.

Updating HLT Paths Map

The cmsRun configuration file AlCaRecoTriggerBitsRcdUpdate_cfg.py (link) can be used as a template to create a new payload with a new tag. It can either be an update based on a previous map (as in the current template) or be created from scratch. Note again that in case the tag to be updated does not have one unlimited IOV, the run number that defines the payload copied to the updated object must be given to the EmptySource. For more details see the comments in AlCaRecoTriggerBitsRcdUpdate_cfg.py. Please check the content of the created sqlite file by AlCaRecoTriggerBitsRcdRead_cfg.py before requesting it to be included in a new global tag. </>

Testing new paths before updating

To test a new set of trigger paths before requesting it to go into the DB, you can simply overwrite the HLT module configuration by hand in the .py produced by cmsDriver.py, e.g. for TkAlZMuMu:

process.ALCARECOMuAlZMuMuHLT.eventSetupPathsKey = ''
process.ALCARECOMuAlZMuMuHLT.HLTPaths = ['newpath1', 'newPath2', 'newPathWithWild*Card', 'newPathEtc']

Upload Technicalities

Use the drop box mechanism to upload. You have to ssh to the online cluster that you need an account for, see ClusterUsersGuide. The drop box directory is /nfshome0/popcondev/HLTJob. This link can tell you the number of the current run (online) - for IOV extension use currentrun+1 or higher.

Adding new AlCaReco Trigger Bit tag

The following are the steps/scripts to add a new AlCaReco Trigger Bit tag, with a new key included. As an example, to add the Key TkAlJetHTHLT with triggerbits 'HLT_*Jet*' , 'HLT_*HT*' to all the payloads of the prompt, express and hlt tags:

1. Update https //github.com/cms-sw/cmssw/blob/master/CondTools/HLT/test/AlCaRecoTriggerBitsRcdUpdate_TEMPL_cfg.py with the correct Key and trigger bits to be updated;

the main part to be updated is this one: https://github.com/cms-sw/cmssw/blob/master/CondTools/HLT/test/AlCaRecoTriggerBitsRcdUpdate_TEMPL_cfg.py#L85-L90

2. Run the following script: https://github.com/cms-sw/cmssw/blob/master/CondTools/HLT/scripts/run_AlCaRecoTriggerBitsUpdateWorkflow.py

What this script does is that it looks for all the IOVs in the given tag and updates each of the payloads by calling the config file determined here:https://github.com/cms-sw/cmssw/blob/master/CondTools/HLT/scripts/run_AlCaRecoTriggerBitsUpdateWorkflow.py#L88

run_AlCaRecoTriggerBitsUpdateWorkflow.py -f frontier://PromptProd/CMS_CONDITIONS -i AlCaRecoHLTpaths8e29_5e33_v7_prompt -d AlCaRecoHLTpaths_TEST

This will give the following output sqlite file: AlCaRecoHLTpaths_TEST.db To look into this file and see all the payloads hashes for each of the IOVs: conddb --db AlCaRecoHLTpaths_TEST.db list AlCaRecoHLTpaths_TEST

3. To read the content of the payloads and write it to a text file with https://github.com/cms-sw/cmssw/blob/master/CondTools/HLT/test/AlCaRecoTriggerBitsRcdRead_TEMPL_cfg.py

cmsRun $CMSSW_BASE/src/CondTools/HLT/test/AlCaRecoTriggerBitsRcdRead_TEMPL_cfg.py inputDB=sqlite_file:AlCaRecoHLTpaths_TEST.db inputTag=AlCaRecoHLTpaths_TEST

then the text file it created can be read and made sure that the key added is in for all the IOVs: triggerBitsAlCaRecoHLTpaths_TEST.twiki

4. The next step is to do the upload to the prep DB, using the script uploadConditions.py

uploadConditions.py AlCaRecoHLTpaths_TEST.db

Let it create the metadata file and do the upload itself.Put a name for the destination tag eg: AlCaRecoHLTpaths8e29_5e33_v9_prompt

5. Then look at the payload inspector to check that all is as expected for that tag.

6. Once all is verified in prep DB, you can upload it to Prod DB.

Current trigger bits tags used for data taking

Current GTs (LatestOnlineGTs Twiki):

* HLT     : 124X_dataRun3_HLT_v4
* Express : 124X_dataRun3_Express_v5
* Prompt  : 124X_dataRun3_Prompt_v4

Current AlCaRecoTriggerBits tags:

* HLT     : 
* Express : 
* Prompt  : 

Existing tags for data taking