Basics & software setup
Instructions to run nTuplizers
General information
How to get the latest HLT configuration
Where to find the Run 3 reconstruction customization functions
# setting up the latest release
export SCRAM_ARCH=slc7_amd64_gcc900
cmsrel CMSSW_12_2_0_pre2
cd CMSSW_12_2_0_pre2/src
cmsenv
export CMSSW_GIT_REFERENCE=/cvmfs/cms.cern.ch/cmssw.git.daily
git cms-init
git cms-addpkg RecoBTag/Combined
git cms-merge-topic silviodonato:customizeHLTforRun3_v2
# clone our version of JMET tools
git clone https://github.com/SWuchterl/JMETriggerAnalysis.git -o SWuchterl -b run3
# make folder for external data (PFHadron calibrations and JEC)
mkdir -p ${CMSSW_BASE}/src/JMETriggerAnalysis/NTuplizers/data
# PFHC: preliminary HLT-PFHC for Run-3
cp /afs/cern.ch/work/m/missirol/public/run3/PFHC/PFHC_Run3Winter20_HLT_v01.db ${CMSSW_BASE}/src/JMETriggerAnalysis/NTuplizers/data/PFHC_Run3Winter20_HLT_v01.db
# JESC: preliminary HLT-JESCs for Run-3 (PF/PUPPI/CALO)
cp /afs/cern.ch/work/m/missirol/public/run3/JESC/Run3Winter20_V2_MC/Run3Winter20_V2_MC.db ${CMSSW_BASE}/src/JMETriggerAnalysis/NTuplizers/data/JESC_Run3Winter20_V2_MC.db
# clone this repository
git clone -b Run3_ForJIRA --recursive https://github.com/SWuchterl/RecoBTag-PerformanceMeasurements.git RecoBTag/PerformanceMeasurements
# use the newest temporary DeepJet retraining
mkdir -p RecoBTag/Combined/data/DeepFlavour_HLT_12X
cp RecoBTag/PerformanceMeasurements/test/modelFiles/DeepJetnoNorm_04.onnx RecoBTag/Combined/data/DeepFlavour_HLT_12X/model.onnx
# fix muon data input files
cd HLTrigger/Configuration/python/Run3
./downloadCustomizationFunctions.sh
cd $CMSSW_BASE/src/RecoMuon/TrackerSeedGenerator/data
git clone -b dev https://github.com/wonpoint4/RecoMuon-TrackerSeedGenerator.git TempNewMuonData
mv TempNewMuonData/* .
mv TempNewMuonData/OIseeding/* OIseeding
rm -rf TempNewMuonData/
cd $CMSSW_BASE/src/
scram b -j12
The Offline ntuplizer can be run and configured through RecoBTag/PerformanceMeasurements/test/runBTagAnalyzer_cfg.py, to run it with the latest defaults
cmsRun runBTagAnalyzer_cfg.py defaults=Run3 runOnData=(True or False, depending on your needs) maxEvents=10The Offline ntuplizer can be run and configured through RecoBTag/PerformanceMeasurements/test/runBTagAnalyzer_cfg.py, to run it with the latest defaults
cmsRun runHLTBTagAnalyzer_cfg.py defaults=Run3 runOnData=(True or False, depending on your needs) maxEvents=10The content of the output nTuple is by default empty and has to be configured according to your needs. The store*Variables options have been removed.
The new variable configuration can be customized in the file RecoBTag/PerformanceMeasurements/python/varGroups_cfi.py.
New variables need also to be added (apart from adding them in the code) in RecoBTag/PerformanceMeasurements/python/variables_cfi.py
Recent versions are also stored already in here For MC:
hltGetConfiguration /dev/CMSSW_12_2_0/GRun \
--full \
--offline \
--unprescale \
--mc \
--process HLT2 \
--globaltag auto:phase1_2021_realistic \
--max-events 10 --eras Run3 \
> tmp.pyedmConfigDump tmp.py > HLT_dev_CMSSW_12_2_0_GRun_configDump_MC.pyFor data:
hltGetConfiguration /dev/CMSSW_12_2_0/GRun \
--full \
--offline \
--unprescale \
--data \
--process HLT2 \
--globaltag auto:run3_hlt \
--max-events 10 --eras Run2_2018 \
--customise HLTrigger/Configuration/customizeHLTforCMSSW.customiseFor2018Input \
> tmp_data.pyedmConfigDump tmp_data.py > HLT_dev_CMSSW_12_2_0_GRun_configDump_Data.pyFor data+timing:
hltGetConfiguration /dev/CMSSW_12_2_0/GRun \
--full \
--offline \
--unprescale \
--data \
--process HLT2 \
--globaltag auto:run3_hlt \
--max-events 10 \
--customise HLTrigger/Configuration/customizeHLTforCMSSW.customiseFor2018Input \
--timing --eras Run2_2018 \
> tmp_data_timing.pyedmConfigDump tmp_data_timing.py > HLT_dev_CMSSW_12_2_0_GRun_configDump_Data_timing.py-
Run3TRK: For the tracking POG single iteration tracking seeded by Patatrack pixeltracks (Triplets+Quadruplets): here An example on how to apply it on top of the GRun menu is here and here
-
DeepJet: For the application of DeepJet to all pF btagging paths: here An example on how to apply it on top of the GRun menu is here
-
noCalo+ROI: For the ROI TRK+PF approach and removal of calo btagging: here An example on how to apply it on top of the GRun menu is here
-
noCalo+global: For the central/global TRK+PF and removal of calo btagging: here An example on how to apply it on top of the GRun menu is here
-
newROICalo+ROI: For the ROI TRK+PF approach and addition of new ROI calo btagging: here An example on how to apply it on top of the GRun menu is here
-
newROICalo+global: For the central/global TRK+PF and addition of new ROI calo btagging: here An example on how to apply it on top of the GRun menu is here
-
newGlobalCalo+global: For the central/global TRK+PF and addition of new central/global TRK calo btagging: here An example on how to apply it on top of the GRun menu is here