Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run3 HZZ electron ID #43369

Closed
wants to merge 3 commits into from
Closed

Conversation

apetkovi1
Copy link

This PR is to add Run3 HZZ electron ID. I have tested the changes privately with 1. Please, test it with this PR 2, since it hasn't been merged yet (weights are available at 3)

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43369/37839

  • This PR adds an extra 44KB to repository

  • There are other open Pull requests which might conflict with changes you have proposed:

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @apetkovi1 (Andro Petkovic) for master.

It involves the following packages:

  • PhysicsTools/NanoAOD (xpog)
  • PhysicsTools/PatAlgos (xpog, reconstruction)
  • RecoEgamma/EgammaTools (reconstruction)
  • RecoEgamma/ElectronIdentification (reconstruction)

@mandrenguyen, @cmsbuild, @vlimant, @jfernan2, @simonepigazzini can you please review it and eventually sign? Thanks.
@ram1123, @azotz, @seemasharmafnal, @nhanvtran, @valsdav, @mmarionncern, @schoef, @gpetruc, @Prasant1993, @a-kapoor, @andrzejnovak, @JyothsnaKomaragiri, @gouskos, @lgray, @jdamgov, @missirol, @Ming-Yan, @AlexDeMoor, @emilbols, @jainshilpi, @hatakeyamak, @afiqaize, @mbluj, @AnnikaStein, @sobhatta, @Senphy, @rappoccio, @sameasy, @ahinzmann, @Sam-Harper, @jdolen, @varuns23, @gkasieczka, @demuller, @mariadalfonso this is something you requested to watch as well.
@sextonkennedy, @antoniovilela, @rappoccio you are the release manager for this.

cms-bot commands are listed here

@jfernan2
Copy link
Contributor

please test with cms-data/RecoEgamma-ElectronIdentification#28

@cmsbuild
Copy link
Contributor

-1

Failed Tests: UnitTests RelVals RelVals-INPUT
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c21094/36033/summary.html
COMMIT: 8a8b9f7
CMSSW: CMSSW_14_0_X_2023-11-22-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/43369/36033/install.sh to create a dev area with all the needed externals and cmssw changes.

Unit Tests

I found 1 errors in the following unit tests:

---> test runtestRecoEgammaElectronIdentification had ERRORS

RelVals

----- Begin Fatal Exception 23-Nov-2023 17:34:22 CET-----------------------
An exception of category 'FileInPathError' occurred while
   [0] Constructing the EventProcessor
   [1] Constructing module: class=ElectronMVAValueMapProducer label='electronMVAValueMapProducer'
Exception Message:
edm::FileInPath unable to find file RecoEgamma/ElectronIdentification/data/MVAWeightFiles/Winter_22_ID_ISO/EB1_5.weights.xml.gz anywhere in the search path.
The search path is defined by: CMSSW_SEARCH_PATH
${CMSSW_SEARCH_PATH} is: /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/43369/36033/CMSSW_14_0_X_2023-11-22-2300/poison:/cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/43369/36033/CMSSW_14_0_X_2023-11-22-2300/src:/cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/43369/36033/CMSSW_14_0_X_2023-11-22-2300/external/el8_amd64_gcc12/data:/cvmfs/cms-ib.cern.ch/sw/x86_64/week0/el8_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-22-2300/poison:/cvmfs/cms-ib.cern.ch/sw/x86_64/week0/el8_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-22-2300/src
Current directory is: /data/cmsbld/jenkins/workspace/ib-run-pr-relvals/matrix-results/136.8311_RunJetHT2017FreMINIAOD
----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 23-Nov-2023 17:34:22 CET-----------------------
An exception of category 'FileInPathError' occurred while
   [0] Constructing the EventProcessor
   [1] Constructing module: class=ElectronMVAValueMapProducer label='electronMVAValueMapProducer'
Exception Message:
edm::FileInPath unable to find file RecoEgamma/ElectronIdentification/data/MVAWeightFiles/Winter_22_ID_ISO/EB1_5.weights.xml.gz anywhere in the search path.
The search path is defined by: CMSSW_SEARCH_PATH
${CMSSW_SEARCH_PATH} is: /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/43369/36033/CMSSW_14_0_X_2023-11-22-2300/poison:/cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/43369/36033/CMSSW_14_0_X_2023-11-22-2300/src:/cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/43369/36033/CMSSW_14_0_X_2023-11-22-2300/external/el8_amd64_gcc12/data:/cvmfs/cms-ib.cern.ch/sw/x86_64/week0/el8_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-22-2300/poison:/cvmfs/cms-ib.cern.ch/sw/x86_64/week0/el8_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-22-2300/src
Current directory is: /data/cmsbld/jenkins/workspace/ib-run-pr-relvals/matrix-results/136.7611_RunJetHT2016EreMINIAOD
----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 23-Nov-2023 17:34:25 CET-----------------------
An exception of category 'FileInPathError' occurred while
   [0] Constructing the EventProcessor
   [1] Constructing module: class=ElectronMVAValueMapProducer label='electronMVAValueMapProducer'
Exception Message:
edm::FileInPath unable to find file RecoEgamma/ElectronIdentification/data/MVAWeightFiles/Winter_22_ID_ISO/EB1_5.weights.xml.gz anywhere in the search path.
The search path is defined by: CMSSW_SEARCH_PATH
${CMSSW_SEARCH_PATH} is: /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/43369/36033/CMSSW_14_0_X_2023-11-22-2300/poison:/cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/43369/36033/CMSSW_14_0_X_2023-11-22-2300/src:/cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/43369/36033/CMSSW_14_0_X_2023-11-22-2300/external/el8_amd64_gcc12/data:/cvmfs/cms-ib.cern.ch/sw/x86_64/week0/el8_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-22-2300/poison:/cvmfs/cms-ib.cern.ch/sw/x86_64/week0/el8_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-22-2300/src
Current directory is: /data/cmsbld/jenkins/workspace/ib-run-pr-relvals/matrix-results/136.88811_RunJetHT2018DreMINIAODUL
----- End Fatal Exception -------------------------------------------------
Expand to see more relval errors ...

RelVals-INPUT

  • 4.64.6_MinimumBias2010A/step2_MinimumBias2010A.log
  • 136.72411136.72411_RunJetHT2016B_reminiaodUL/step2_RunJetHT2016B_reminiaodUL.log
  • 136.72412136.72412_RunJetHT2016B_reminiaodUL/step2_RunJetHT2016B_reminiaodUL.log
Expand to see more relval errors ...

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43369/37858

  • This PR adds an extra 40KB to repository

  • There are other open Pull requests which might conflict with changes you have proposed:

@cmsbuild
Copy link
Contributor

Pull request #43369 was updated. @vlimant, @jfernan2, @cmsbuild, @mandrenguyen, @simonepigazzini can you please check and sign again.

@a-kapoor
Copy link
Contributor

@apetkovi1 Did you do private tests with runTheMatrix? If you can share those, that would be nice. Moreover, did you validate this ID once it has appeared in Mini and nano? It would be useful to see that, for example, the signal efficiency is indeed what you think it is.

@apetkovi1
Copy link
Author

Hi @a-kapoor, no I just ran testElectronMVARun3 to see if it appears in nano and calculated manually sig eff as a check. I am not aware there is another test runTheMatrix. Can you please share this script. Also, if there is a script that validates if ID appears in nano and Mini outside of testElectronMVARun3, can you also share it ?

@a-kapoor
Copy link
Contributor

Hi @apetkovi1,
Sure!
Once compiled and env set with cmsenv, you can run:
runTheMatrix.py -l 12434.0
This will run a standard ttbar workflow with the series of cmsDriver commands.
With default settings you will get a ttbar mini and nano with 10 events.

If you have the results of the manual check, please share those too. (You can update the description of the PR)

@apetkovi1
Copy link
Author

apetkovi1 commented Nov 23, 2023

@a-kapoor I ran runTheMatrix test and it fails:

in: /grid_mnt/vol_home/llr/cms/apetkovic/CMSSW_13_3_0/src going to execute cd 12434.0_TTbar_14TeV+2023

cmsDriver.py TTbar_14TeV_TuneCP5_cfi -s GEN,SIM -n 10 --conditions auto:phase1_2023_realistic --beamspot Realistic25ns13p6TeVEarly2023Collision --datatier GEN-SIM --eventcontent FEVTDEBUG --geometry DB:Extended --era Run3_2023 --relval 9000,100 --fileout file:step1.root > step1_TTbar_14TeV+2023.log 2>&1

in: /grid_mnt/vol_home/llr/cms/apetkovic/CMSSW_13_3_0/src going to execute cd 12434.0_TTbar_14TeV+2023

cmsDriver.py step2 -s DIGI:pdigi_valid,L1,DIGI2RAW,HLT:@relval2023 --conditions auto:phase1_2023_realistic --datatier GEN-SIM-DIGI-RAW -n 10 --eventcontent FEVTDEBUGHLT --geometry DB:Extended --era Run3_2023 --filein file:step1.root --fileout file:step2.root > step2_TTbar_14TeV+2023.log 2>&1

in: /grid_mnt/vol_home/llr/cms/apetkovic/CMSSW_13_3_0/src going to execute cd 12434.0_TTbar_14TeV+2023

cmsDriver.py step3 -s RAW2DIGI,L1Reco,RECO,RECOSIM,PAT,NANO,VALIDATION:@standardValidation+@miniAODValidation,DQM:@standardDQM+@ExtraHLT+@miniAODDQM+@nanoAODDQM --conditions auto:phase1_2023_realistic --datatier GEN-SIM-RECO,MINIAODSIM,NANOAODSIM,DQMIO -n 10 --eventcontent RECOSIM,MINIAODSIM,NANOEDMAODSIM,DQM --geometry DB:Extended --era Run3_2023 --filein file:step2.root --fileout file:step3.root > step3_TTbar_14TeV+2023.log 2>&1

ERROR executing cd 12434.0_TTbar_14TeV+2023; cmsDriver.py step3 -s RAW2DIGI,L1Reco,RECO,RECOSIM,PAT,NANO,VALIDATION:@standardValidation+@miniAODValidation,DQM:@standardDQM+@ExtraHLT+@miniAODDQM+@nanoAODDQM --conditions auto:phase1_2023_realistic --datatier GEN-SIM-RECO,MINIAODSIM,NANOAODSIM,DQMIO -n 10 --eventcontent RECOSIM,MINIAODSIM,NANOEDMAODSIM,DQM --geometry DB:Extended --era Run3_2023 --filein file:step2.root --fileout file:step3.root > step3_TTbar_14TeV+2023.log 2>&1; ret= 16640
12434.0_TTbar_14TeV+2023 Step0-PASSED Step1-PASSED Step2-FAILED Step3-NOTRUN Step4-NOTRUN - time date Thu Nov 23 20:13:49 2023-date Thu Nov 23 20:00:17 2023; exit: 0 0 16640 0 0
1 1 0 0 0 tests passed, 0 0 1 0 0 failed

Will have to solve this

@cmsbuild
Copy link
Contributor

-1

Failed Tests: RelVals RelVals-INPUT
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c21094/36042/summary.html
COMMIT: 910a4ba
CMSSW: CMSSW_14_0_X_2023-11-23-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/43369/36042/install.sh to create a dev area with all the needed externals and cmssw changes.

RelVals

----- Begin Fatal Exception 23-Nov-2023 20:21:59 CET-----------------------
An exception of category 'ProductNotFound' occurred while
   [0] Processing  Event run: 1 lumi: 1 event: 2 stream: 1
   [1] Running path 'NANOEDMAODSIMoutput_step'
   [2] Prefetching for module PoolOutputModule/'NANOEDMAODSIMoutput'
   [3] Prefetching for module CandMCMatchTableProducer/'boostedTauMCTable'
   [4] Prefetching for module PATObjectCrossLinker/'linkedObjects'
   [5] Prefetching for module PATElectronRefSelector/'finalElectrons'
   [6] Calling method for module PATElectronUserDataEmbedder/'slimmedElectronsWithUserData'
Exception Message:
Principal::getByToken: Found zero products matching all criteria
Looking for type: edm::ValueMap<bool>
Looking for module label: egmGsfElectronIDs
Looking for productInstanceName: mvaEleID-Winter22-HZZ-V1

   Additional Info:
      [a] If you wish to continue processing events after a ProductNotFound exception,
add "TryToContinue = cms.untracked.vstring('ProductNotFound')" to the "options" PSet in the configuration.

----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 23-Nov-2023 20:27:32 CET-----------------------
An exception of category 'ProductNotFound' occurred while
   [0] Processing  Event run: 1 lumi: 1 event: 1 stream: 1
   [1] Running path 'NANOEDMAODSIMoutput_step'
   [2] Prefetching for module PoolOutputModule/'NANOEDMAODSIMoutput'
   [3] Prefetching for module CandMCMatchTableProducer/'boostedTauMCTable'
   [4] Prefetching for module PATObjectCrossLinker/'linkedObjects'
   [5] Prefetching for module PATElectronRefSelector/'finalElectrons'
   [6] Calling method for module PATElectronUserDataEmbedder/'slimmedElectronsWithUserData'
Exception Message:
Principal::getByToken: Found zero products matching all criteria
Looking for type: edm::ValueMap<bool>
Looking for module label: egmGsfElectronIDs
Looking for productInstanceName: mvaEleID-Winter22-HZZ-V1

   Additional Info:
      [a] If you wish to continue processing events after a ProductNotFound exception,
add "TryToContinue = cms.untracked.vstring('ProductNotFound')" to the "options" PSet in the configuration.

----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 23-Nov-2023 20:31:27 CET-----------------------
An exception of category 'Configuration' occurred while
   [0] Processing  Event run: 369978 lumi: 219 event: 198765919 stream: 0
   [1] Running path 'dqmoffline_2_step'
   [2] Prefetching for module NanoAODDQM/'nanoDQM'
   [3] Prefetching for module SimpleCandidateFlatTableProducer/'boostedTauTable'
   [4] Prefetching for module PATObjectCrossLinker/'linkedObjects'
   [5] Prefetching for module PATElectronRefSelector/'finalElectrons'
   [6] Prefetching for module PATElectronUserDataEmbedder/'slimmedElectronsWithUserData'
   [7] Calling method for module EleVIDNestedWPBitmapProducer/'bitmapVIDForEle'
Exception Message:
Trying to compress VID bitmaps for cutflows of different size 
----- End Fatal Exception -------------------------------------------------
Expand to see more relval errors ...

RelVals-INPUT

  • 140.202140.202_RunJetMET2022D_reMINI/step2_RunJetMET2022D_reMINI.log
  • 13234.013234.0_TTbar_14TeV+2021FS/step2_TTbar_14TeV+2021FS.log
  • 14034.014034.0_TTbar_14TeV+2023FS/step2_TTbar_14TeV+2023FS.log
Expand to see more relval errors ...

@a-kapoor
Copy link
Contributor

@a-kapoor I ran runTheMatrix test and it fails:

in: /grid_mnt/vol_home/llr/cms/apetkovic/CMSSW_13_3_0/src going to execute cd 12434.0_TTbar_14TeV+2023

cmsDriver.py TTbar_14TeV_TuneCP5_cfi -s GEN,SIM -n 10 --conditions auto:phase1_2023_realistic --beamspot Realistic25ns13p6TeVEarly2023Collision --datatier GEN-SIM --eventcontent FEVTDEBUG --geometry DB:Extended --era Run3_2023 --relval 9000,100 --fileout file:step1.root > step1_TTbar_14TeV+2023.log 2>&1

in: /grid_mnt/vol_home/llr/cms/apetkovic/CMSSW_13_3_0/src going to execute cd 12434.0_TTbar_14TeV+2023

cmsDriver.py step2 -s DIGI:pdigi_valid,L1,DIGI2RAW,HLT:@relval2023 --conditions auto:phase1_2023_realistic --datatier GEN-SIM-DIGI-RAW -n 10 --eventcontent FEVTDEBUGHLT --geometry DB:Extended --era Run3_2023 --filein file:step1.root --fileout file:step2.root > step2_TTbar_14TeV+2023.log 2>&1

in: /grid_mnt/vol_home/llr/cms/apetkovic/CMSSW_13_3_0/src going to execute cd 12434.0_TTbar_14TeV+2023

cmsDriver.py step3 -s RAW2DIGI,L1Reco,RECO,RECOSIM,PAT,NANO,VALIDATION:@standardValidation+@miniAODValidation,DQM:@standardDQM+@ExtraHLT+@miniAODDQM+@nanoAODDQM --conditions auto:phase1_2023_realistic --datatier GEN-SIM-RECO,MINIAODSIM,NANOAODSIM,DQMIO -n 10 --eventcontent RECOSIM,MINIAODSIM,NANOEDMAODSIM,DQM --geometry DB:Extended --era Run3_2023 --filein file:step2.root --fileout file:step3.root > step3_TTbar_14TeV+2023.log 2>&1

ERROR executing cd 12434.0_TTbar_14TeV+2023; cmsDriver.py step3 -s RAW2DIGI,L1Reco,RECO,RECOSIM,PAT,NANO,VALIDATION:@standardValidation+@miniAODValidation,DQM:@standardDQM+@ExtraHLT+@miniAODDQM+@nanoAODDQM --conditions auto:phase1_2023_realistic --datatier GEN-SIM-RECO,MINIAODSIM,NANOAODSIM,DQMIO -n 10 --eventcontent RECOSIM,MINIAODSIM,NANOEDMAODSIM,DQM --geometry DB:Extended --era Run3_2023 --filein file:step2.root --fileout file:step3.root > step3_TTbar_14TeV+2023.log 2>&1; ret= 16640 12434.0_TTbar_14TeV+2023 Step0-PASSED Step1-PASSED Step2-FAILED Step3-NOTRUN Step4-NOTRUN - time date Thu Nov 23 20:13:49 2023-date Thu Nov 23 20:00:17 2023; exit: 0 0 16640 0 0 1 1 0 0 0 tests passed, 0 0 1 0 0 failed

Will have to solve this

Hey. You need to look at the log files like these "step3_TTbar_14TeV+2023.log". This might shed some light on the errors.
I suggest you don't update the PR until local tests have passed.

@apetkovi1
Copy link
Author

apetkovi1 commented Nov 24, 2023

Hi @a-kapoor, after changing few things, I am now able to runTheMatrix.py -l 12434.0 locally. However, I do not see any nanoAOD file as an output (I was expecting to see nanoAOD file with tree-like structure where one of the branches would correspond to newly added HZZ ID). Or am I missing something, and runTheMatrix should not produce something like that at all. After running the command these are output files:
cmdLog
step2_DIGI_L1_DIGI2RAW_HLT.py
step4_TTbar_14TeV+2023.log
DQM_V0001_R000000001__Global__CMSSW_X_Y_Z__RECO.root
step2.root
step5_ALCA.py
EcalESAlign.root
step2_TTbar_14TeV+2023.log
step5_TTbar_14TeV+2023.log
HcalCalHBHEMuonProducerFilter.root
step3_inDQM.root
TkAlDiMuonAndVertex.root
MuAlOverlaps.root
step3_inMINIAODSIM.root
TkAlJpsiMuMu.root
SiPixelCalSingleMuonLoose.root
step3_inNANOEDMAODSIM.root
TkAlMinBias.root
SiPixelCalSingleMuonTight.root step3_RAW2DIGI_L1Reco_RECO_RECOSIM_PAT_NANO_VALIDATION_DQM.py
TkAlMuonIsolated.root
SiStripCalMinBias.root
step3.root
TkAlUpsilonMuMu.root
step1.root
step3_TTbar_14TeV+2023.log
TkAlZMuMu.root
step1_TTbar_14TeV+2023.log
step4_HARVESTING.py
TTbar_14TeV_TuneCP5_cfi_GEN_SIM.py

@Prasant1993
Copy link
Contributor

Prasant1993 commented Nov 24, 2023

Hi @apetkovi1, this time it seems the test is successful. You have all the output files
Can you have a look into this Nano file : step3_inNANOEDMAODSIM.root
If you look at this log file: step3_TTbar_14TeV+2023.log, you can see whether your new ID is added to pat electrons or not

Hint: The log file will contain something like below for an example:
--- egmGsfElectronIDs:mvaEleID-RunIIIWinter22-iso-V1-wp80 added to patElectrons
--- egmGsfElectronIDs:mvaEleID-RunIIIWinter22-iso-V1-wp90 added to patElectrons
--- egmGsfElectronIDs:mvaEleID-RunIIIWinter22-noIso-V1-wp80 added to patElectrons
--- egmGsfElectronIDs:mvaEleID-RunIIIWinter22-noIso-V1-wp90 added to patElectrons

@apetkovi1
Copy link
Author

apetkovi1 commented Nov 24, 2023

Hi @Prasant1993 - unfortunately when I check step3_TTbar_14TeV+2023.log it seems that it fails to add this ID. It is strange why it did not crash. Do you perhaps now what could cause these logic errors in log:
`RAW2DIGI,L1Reco,RECO,RECOSIM,PAT,NANO,VALIDATION:@standardValidation+@miniAODValidation,DQM:@standardDQM+@ExtraHLT+@miniAODDQM+@nanoAODDQM
We have determined that this is simulation (if not, rerun cmsDriver.py with --data)
with DB:
entry file:step2.root
Step: RAW2DIGI Spec:
Step: L1Reco Spec:
Step: RECO Spec:
Step: RECOSIM Spec:
Step: PAT Spec:
Step: NANO Spec:
in prepare_nano nanoSequenceMC
Step: VALIDATION Spec: ['@standardValidation', '@miniAODValidation']
@standardValidation+@miniAODValidation in preparing validation
Step: DQM Spec: ['@standardDQM', '@ExtraHLT', '@miniAODDQM', '@nanoAODDQM']
customising the process with nanoAOD_customizeCommon from PhysicsTools/NanoAOD/nano_cff
customising the process with setCrossingFrameOn from SimGeneral/MixingModule/fullMixCustomize_cff
customising the process with miniAOD_customizeAllMC from PhysicsTools/PatAlgos/slimming/miniAOD_tools
Starting cmsRun step3_RAW2DIGI_L1Reco_RECO_RECOSIM_PAT_NANO_VALIDATION_DQM.py
24-Nov-2023 20:57:39 CET Initiating request to open file file:step2.root
24-Nov-2023 20:57:42 CET Successfully opened file file:step2.root
2023-11-24 20:57:57.743875: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: SSE4.1 SSE4.2 AVX AVX2 AVX512F FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-11-24 20:57:57.759497: I tensorflow/compiler/mlir/mlir_graph_optimization_pass.cc:353] MLIR V1 optimization pass is not enabled
%MSG-w IdInformation: VersionedGsfElectronIdProducer:egmGsfElectronIDs@ctor 24-Nov-2023 20:57:59 CET pre-events
Instantiated ID: mvaEleID-Winter22-HZZ-V1
with MD5 hash:
This ID is not POG approved and likely under development!!!
Please make sure to report your progress with this ID at the next relevant POG meeting.

%MSG
%MSG-w LogicError: GenWeightsTableProducer:genWeightsTable@beginRun 24-Nov-2023 20:58:15 CET Run: 1
::getByLabel: An attempt was made to read a Run product before endRun() was called.
The product is of type 'LHERunInfoProduct'.
The specified ModuleLabel was 'externalLHEProducer'.
The specified productInstanceName was ''.

%MSG
%MSG-w LogicError: GenWeightsTableProducer:genWeightsTable@beginRun 24-Nov-2023 20:58:15 CET Run: 1
::getByLabel: An attempt was made to read a Run product before endRun() was called.
The product is of type 'LHERunInfoProduct'.
The specified ModuleLabel was 'source'.
The specified productInstanceName was ''.

%MSG
%MSG-w LogicError: HTXSRivetProducer:rivetProducerHTXS@beginRun 24-Nov-2023 20:58:15 CET Run: 1
::getByLabel: An attempt was made to read a Run product before endRun() was called.
The product is of type 'LHERunInfoProduct'.
The specified ModuleLabel was 'externalLHEProducer'.
The specified productInstanceName was ''.

%MSG
%MSG-w LogicError: LheWeightValidation:lheWeightValidation@beginRun 24-Nov-2023 20:58:16 CET Run: 1
::getByLabel: An attempt was made to read a Run product before endRun() was called.
The product is of type 'LHERunInfoProduct'.
The specified ModuleLabel was 'externalLHEProducer'.
The specified productInstanceName was ''.

%MSG
Begin processing the 1st record. Run 1, Event 1, LumiSection 1 on stream 0 at 24-Nov-2023 20:58:29.239 CET
#--------------------------------------------------------------------------

FastJet release 3.4.1

M. Cacciari, G.P. Salam and G. Soyez

A software package for jet finding and analysis at colliders

http://fastjet.fr

Please cite EPJC72(2012)1896 [arXiv:1111.6097] if you use this package

for scientific work and optionally PLB641(2006)57 [hep-ph/0512210].

FastJet is provided without warranty under the GNU GPL v2 or higher.

It uses T. Chan's closest pair algorithm, S. Fortune's Voronoi code

and 3rd party plugin jet algorithms. See COPYING file for details.

#--------------------------------------------------------------------------
%MSG-w LHETablesProducer: GenWeightsTableProducer:genWeightsTable 24-Nov-2023 20:58:30 CET Run: 1 Event: 1
No LHEEventProduct, so there will be no LHE Tables

%MSG
Rivet.AnalysisHandler: INFO Using named weights

======== HiggsTemplateCrossSections Initialization =========

Rivet.Analysis.HiggsTemplateCrossSections: WARN No HIGGSPRODMODE shell variable found. Needed when running Rivet stand-alone.

======== Higgs prod mode 0 =========
======== Sucessful Initialization =========

Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Rivet.AnalysisHandler: INFO Using named weights
Begin processing the 2nd record. Run 1, Event 2, LumiSection 1 on stream 0 at 24-Nov-2023 20:58:45.671 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Begin processing the 3rd record. Run 1, Event 3, LumiSection 1 on stream 0 at 24-Nov-2023 20:58:46.996 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Begin processing the 4th record. Run 1, Event 4, LumiSection 1 on stream 0 at 24-Nov-2023 20:58:49.329 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Begin processing the 5th record. Run 1, Event 5, LumiSection 1 on stream 0 at 24-Nov-2023 20:58:51.213 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Begin processing the 6th record. Run 1, Event 6, LumiSection 1 on stream 0 at 24-Nov-2023 20:58:53.018 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Begin processing the 7th record. Run 1, Event 7, LumiSection 1 on stream 0 at 24-Nov-2023 20:58:54.464 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Begin processing the 8th record. Run 1, Event 8, LumiSection 1 on stream 0 at 24-Nov-2023 20:58:56.052 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Begin processing the 9th record. Run 1, Event 9, LumiSection 1 on stream 0 at 24-Nov-2023 20:58:57.900 CET
%MSG-w NullTransverseMomentum: JetFlavourClustering:genJetAK8FlavourAssociation 24-Nov-2023 20:58:58 CET Run: 1 Event: 9
dropping input candidate with pt=0
%MSG
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Begin processing the 10th record. Run 1, Event 10, LumiSection 1 on stream 0 at 24-Nov-2023 20:59:00.295 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Rivet.Analysis.HiggsTemplateCrossSections: INFO ======================================================
Rivet.Analysis.HiggsTemplateCrossSections: INFO Higgs Template X-Sec Categorization Tool
Rivet.Analysis.HiggsTemplateCrossSections: INFO Status Code Summary
Rivet.Analysis.HiggsTemplateCrossSections: INFO ======================================================
Rivet.Analysis.HiggsTemplateCrossSections: INFO >>>> All 0 events successfully categorized!
Rivet.Analysis.HiggsTemplateCrossSections: INFO ======================================================
Rivet.Analysis.HiggsTemplateCrossSections: INFO ======================================================
24-Nov-2023 20:59:07 CET Closed file file:step2.root

The MCnet usage guidelines apply to Rivet: see http://www.montecarlonet.org/GUIDELINES
Please acknowledge Rivet in results made using it, and cite https://arxiv.org/abs/1912.05451
`

@Prasant1993
Copy link
Contributor

I am just curious about the msg :
%MSG-w IdInformation: VersionedGsfElectronIdProducer:egmGsfElectronIDs@ctor 24-Nov-2023 20:57:59 CET pre-events
Instantiated ID: mvaEleID-Winter22-HZZ-V1
with MD5 hash:
This ID is not POG approved and likely under development!!!
Please make sure to report your progress with this ID at the next relevant POG meeting.

Given the above,
Hi @apetkovi1 and @a-kapoor , the ID is EGM POG approved I suppose.

If that's the case, can you also make it true here : https://github.com/apetkovi1/cmssw/blob/Run3_HZZelectronID_V1p1/RecoEgamma/ElectronIdentification/python/Identification/mvaElectronID_Winter22_HZZ_V1_cff.py#L49

mvaEleID_Winter22_HZZ_V1.isPOGApproved = cms.untracked.bool(False)

@apetkovi1
Copy link
Author

Hi @Prasant1993 - it is not approved. I presented this ID on EGM meeting - in the meanwhile I recomputed weights so that ID uses cluster iso variables instead of particle. If I change POGapproved to true log looks like this (I still do not see in the log any info that my ID has been added. Checking step3_inNANOEDMAODSIM.root I only see branches that correspond to some tables, not even sure what does it mean):
RAW2DIGI,L1Reco,RECO,RECOSIM,PAT,NANO,VALIDATION:@standardValidation+@miniAODValidation,DQM:@standardDQM+@ExtraHLT+@miniAODDQM+@nanoAODDQM
We have determined that this is simulation (if not, rerun cmsDriver.py with --data)
with DB:
entry file:step2.root
Step: RAW2DIGI Spec:
Step: L1Reco Spec:
Step: RECO Spec:
Step: RECOSIM Spec:
Step: PAT Spec:
Step: NANO Spec:
in prepare_nano nanoSequenceMC
Step: VALIDATION Spec: ['@standardValidation', '@miniAODValidation']
@standardValidation+@miniAODValidation in preparing validation
Step: DQM Spec: ['@standardDQM', '@ExtraHLT', '@miniAODDQM', '@nanoAODDQM']
customising the process with nanoAOD_customizeCommon from PhysicsTools/NanoAOD/nano_cff
customising the process with setCrossingFrameOn from SimGeneral/MixingModule/fullMixCustomize_cff
customising the process with miniAOD_customizeAllMC from PhysicsTools/PatAlgos/slimming/miniAOD_tools
Starting cmsRun step3_RAW2DIGI_L1Reco_RECO_RECOSIM_PAT_NANO_VALIDATION_DQM.py
25-Nov-2023 13:02:25 CET Initiating request to open file file:step2.root
25-Nov-2023 13:02:29 CET Successfully opened file file:step2.root
2023-11-25 13:02:53.237724: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: SSE4.1 SSE4.2 AVX AVX2 AVX512F FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-11-25 13:02:53.257825: I tensorflow/compiler/mlir/mlir_graph_optimization_pass.cc:353] MLIR V1 optimization pass is not enabled
%MSG-w LogicError: GenWeightsTableProducer:genWeightsTable@beginRun 25-Nov-2023 13:03:26 CET Run: 1
::getByLabel: An attempt was made to read a Run product before endRun() was called.
The product is of type 'LHERunInfoProduct'.
The specified ModuleLabel was 'externalLHEProducer'.
The specified productInstanceName was ''.

%MSG
%MSG-w LogicError: GenWeightsTableProducer:genWeightsTable@beginRun 25-Nov-2023 13:03:26 CET Run: 1
::getByLabel: An attempt was made to read a Run product before endRun() was called.
The product is of type 'LHERunInfoProduct'.
The specified ModuleLabel was 'source'.
The specified productInstanceName was ''.

%MSG
%MSG-w LogicError: HTXSRivetProducer:rivetProducerHTXS@beginRun 25-Nov-2023 13:03:26 CET Run: 1
::getByLabel: An attempt was made to read a Run product before endRun() was called.
The product is of type 'LHERunInfoProduct'.
The specified ModuleLabel was 'externalLHEProducer'.
The specified productInstanceName was ''.

%MSG
%MSG-w LogicError: LheWeightValidation:lheWeightValidation@beginRun 25-Nov-2023 13:03:27 CET Run: 1
::getByLabel: An attempt was made to read a Run product before endRun() was called.
The product is of type 'LHERunInfoProduct'.
The specified ModuleLabel was 'externalLHEProducer'.
The specified productInstanceName was ''.

%MSG
Begin processing the 1st record. Run 1, Event 1, LumiSection 1 on stream 0 at 25-Nov-2023 13:03:43.003 CET
#--------------------------------------------------------------------------

FastJet release 3.4.1

M. Cacciari, G.P. Salam and G. Soyez

A software package for jet finding and analysis at colliders

http://fastjet.fr

Please cite EPJC72(2012)1896 [arXiv:1111.6097] if you use this package

for scientific work and optionally PLB641(2006)57 [hep-ph/0512210].

FastJet is provided without warranty under the GNU GPL v2 or higher.

It uses T. Chan's closest pair algorithm, S. Fortune's Voronoi code

and 3rd party plugin jet algorithms. See COPYING file for details.

#--------------------------------------------------------------------------
%MSG-w LHETablesProducer: GenWeightsTableProducer:genWeightsTable 25-Nov-2023 13:03:44 CET Run: 1 Event: 1
No LHEEventProduct, so there will be no LHE Tables

%MSG
Rivet.AnalysisHandler: INFO Using named weights

======== HiggsTemplateCrossSections Initialization =========

Rivet.Analysis.HiggsTemplateCrossSections: WARN No HIGGSPRODMODE shell variable found. Needed when running Rivet stand-alone.

======== Higgs prod mode 0 =========
======== Sucessful Initialization =========

Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Rivet.AnalysisHandler: INFO Using named weights
Begin processing the 2nd record. Run 1, Event 2, LumiSection 1 on stream 0 at 25-Nov-2023 13:04:02.225 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Begin processing the 3rd record. Run 1, Event 3, LumiSection 1 on stream 0 at 25-Nov-2023 13:04:04.050 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Begin processing the 4th record. Run 1, Event 4, LumiSection 1 on stream 0 at 25-Nov-2023 13:04:06.768 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Begin processing the 5th record. Run 1, Event 5, LumiSection 1 on stream 0 at 25-Nov-2023 13:04:09.099 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Begin processing the 6th record. Run 1, Event 6, LumiSection 1 on stream 0 at 25-Nov-2023 13:04:11.193 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Begin processing the 7th record. Run 1, Event 7, LumiSection 1 on stream 0 at 25-Nov-2023 13:04:12.782 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Begin processing the 8th record. Run 1, Event 8, LumiSection 1 on stream 0 at 25-Nov-2023 13:04:14.478 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Begin processing the 9th record. Run 1, Event 9, LumiSection 1 on stream 0 at 25-Nov-2023 13:04:16.399 CET
%MSG-w NullTransverseMomentum: JetFlavourClustering:genJetAK8FlavourAssociation 25-Nov-2023 13:04:16 CET Run: 1 Event: 9
dropping input candidate with pt=0
%MSG
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Begin processing the 10th record. Run 1, Event 10, LumiSection 1 on stream 0 at 25-Nov-2023 13:04:18.752 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Rivet.Analysis.HiggsTemplateCrossSections: INFO ======================================================
Rivet.Analysis.HiggsTemplateCrossSections: INFO Higgs Template X-Sec Categorization Tool
Rivet.Analysis.HiggsTemplateCrossSections: INFO Status Code Summary
Rivet.Analysis.HiggsTemplateCrossSections: INFO ======================================================
Rivet.Analysis.HiggsTemplateCrossSections: INFO >>>> All 0 events successfully categorized!
Rivet.Analysis.HiggsTemplateCrossSections: INFO ======================================================
Rivet.Analysis.HiggsTemplateCrossSections: INFO ======================================================
25-Nov-2023 13:04:26 CET Closed file file:step2.root

The MCnet usage guidelines apply to Rivet: see http://www.montecarlonet.org/GUIDELINES
Please acknowledge Rivet in results made using it, and cite https://arxiv.org/abs/1912.05451

@Prasant1993
Copy link
Contributor

Prasant1993 commented Nov 25, 2023

Hi @apetkovi1
Okay I see. It would be good to have green light from EGM POG before this ID is added to CMSSW.
I let @a-kapoor and @RSalvatico take care of it.

Since in the log file I don't see the msg appearing whether the ID is added or not.
To make sure, lets check the miniAOD file produced : step3_inMINIAODSIM.root
To print the electron and photon ID from MiniAOD, can you run this file here: https://swmukher.web.cern.ch/swmukher/printEgammaUserData.py

python3 printEgammaUserData.py step3_inMINIAODSIM.root

You can paste here the output of the above command.

@apetkovi1
Copy link
Author

Hi @Prasant1993 yes it has been added - output looks like this:
pho userfloats:
PhotonMVAEstimatorRun2Spring16NonTrigV1Values
PhotonMVAEstimatorRunIIFall17v1p1Values
PhotonMVAEstimatorRunIIFall17v2Values
PhotonMVAEstimatorRunIIIWinter22v1Values
pho userints:
PhotonMVAEstimatorRun2Spring16NonTrigV1Categories
PhotonMVAEstimatorRunIIFall17v1p1Categories
PhotonMVAEstimatorRunIIFall17v2Categories
PhotonMVAEstimatorRunIIIWinter22v1Categories
cutBasedPhotonID-Fall17-94X-V1-loose
cutBasedPhotonID-Fall17-94X-V1-medium
cutBasedPhotonID-Fall17-94X-V1-tight
cutBasedPhotonID-Fall17-94X-V2-loose
cutBasedPhotonID-Fall17-94X-V2-medium
cutBasedPhotonID-Fall17-94X-V2-tight
cutBasedPhotonID-RunIIIWinter22-122X-V1-loose
cutBasedPhotonID-RunIIIWinter22-122X-V1-medium
cutBasedPhotonID-RunIIIWinter22-122X-V1-tight
cutBasedPhotonID-Spring16-V2p2-loose
cutBasedPhotonID-Spring16-V2p2-medium
cutBasedPhotonID-Spring16-V2p2-tight
pho IDs:
cutBasedPhotonID-Fall17-94X-V1-loose
cutBasedPhotonID-Fall17-94X-V1-medium
cutBasedPhotonID-Fall17-94X-V1-tight
cutBasedPhotonID-Fall17-94X-V2-loose
cutBasedPhotonID-Fall17-94X-V2-medium
cutBasedPhotonID-Fall17-94X-V2-tight
cutBasedPhotonID-RunIIIWinter22-122X-V1-loose
cutBasedPhotonID-RunIIIWinter22-122X-V1-medium
cutBasedPhotonID-RunIIIWinter22-122X-V1-tight
cutBasedPhotonID-Spring16-V2p2-loose
cutBasedPhotonID-Spring16-V2p2-medium
cutBasedPhotonID-Spring16-V2p2-tight
mvaPhoID-RunIIFall17-v1p1-wp80
mvaPhoID-RunIIFall17-v1p1-wp90
mvaPhoID-RunIIFall17-v2-wp80
mvaPhoID-RunIIFall17-v2-wp90
mvaPhoID-RunIIIWinter22-v1-wp80
mvaPhoID-RunIIIWinter22-v1-wp90
mvaPhoID-Spring16-nonTrig-V1-wp80
mvaPhoID-Spring16-nonTrig-V1-wp90
ele userfloats:
ElectronMVAEstimatorRun2Fall17IsoV1Values
ElectronMVAEstimatorRun2Fall17IsoV2Values
ElectronMVAEstimatorRun2Fall17NoIsoV1Values
ElectronMVAEstimatorRun2Fall17NoIsoV2Values
ElectronMVAEstimatorRun2RunIIIWinter22IsoV1Values
ElectronMVAEstimatorRun2RunIIIWinter22NoIsoV1Values
ElectronMVAEstimatorRun2Spring16GeneralPurposeV1Values
ElectronMVAEstimatorRun2Spring16HZZV1Values
ElectronMVAEstimatorRun2Summer18ULIdIsoValues
ElectronMVAEstimatorRun2Winter22HZZV1Values
ele userints:
ElectronMVAEstimatorRun2Fall17IsoV1Categories
ElectronMVAEstimatorRun2Fall17IsoV2Categories
ElectronMVAEstimatorRun2Fall17NoIsoV1Categories
ElectronMVAEstimatorRun2Fall17NoIsoV2Categories
ElectronMVAEstimatorRun2RunIIIWinter22IsoV1Categories
ElectronMVAEstimatorRun2RunIIIWinter22NoIsoV1Categories
ElectronMVAEstimatorRun2Spring16GeneralPurposeV1Categories
ElectronMVAEstimatorRun2Spring16HZZV1Categories
ElectronMVAEstimatorRun2Summer18ULIdIsoCategories
ElectronMVAEstimatorRun2Winter22HZZV1Categories
cutBasedElectronID-Fall17-94X-V1-loose
cutBasedElectronID-Fall17-94X-V1-medium
cutBasedElectronID-Fall17-94X-V1-tight
cutBasedElectronID-Fall17-94X-V1-veto
cutBasedElectronID-Fall17-94X-V2-loose
cutBasedElectronID-Fall17-94X-V2-medium
cutBasedElectronID-Fall17-94X-V2-tight
cutBasedElectronID-Fall17-94X-V2-veto
cutBasedElectronID-RunIIIWinter22-V1-loose
cutBasedElectronID-RunIIIWinter22-V1-medium
cutBasedElectronID-RunIIIWinter22-V1-tight
cutBasedElectronID-RunIIIWinter22-V1-veto
cutBasedElectronID-Summer16-80X-V1-loose
cutBasedElectronID-Summer16-80X-V1-medium
cutBasedElectronID-Summer16-80X-V1-tight
cutBasedElectronID-Summer16-80X-V1-veto
heepElectronID-HEEPV70
heepElectronID-HEEPV71
ele IDs:
cutBasedElectronID-Fall17-94X-V1-loose
cutBasedElectronID-Fall17-94X-V1-medium
cutBasedElectronID-Fall17-94X-V1-tight
cutBasedElectronID-Fall17-94X-V1-veto
cutBasedElectronID-Fall17-94X-V2-loose
cutBasedElectronID-Fall17-94X-V2-medium
cutBasedElectronID-Fall17-94X-V2-tight
cutBasedElectronID-Fall17-94X-V2-veto
cutBasedElectronID-RunIIIWinter22-V1-loose
cutBasedElectronID-RunIIIWinter22-V1-medium
cutBasedElectronID-RunIIIWinter22-V1-tight
cutBasedElectronID-RunIIIWinter22-V1-veto
cutBasedElectronID-Summer16-80X-V1-loose
cutBasedElectronID-Summer16-80X-V1-medium
cutBasedElectronID-Summer16-80X-V1-tight
cutBasedElectronID-Summer16-80X-V1-veto
heepElectronID-HEEPV70
heepElectronID-HEEPV71
mvaEleID-Fall17-iso-V1-wp80
mvaEleID-Fall17-iso-V1-wp90
mvaEleID-Fall17-iso-V1-wpLoose
mvaEleID-Fall17-iso-V2-wp80
mvaEleID-Fall17-iso-V2-wp90
mvaEleID-Fall17-iso-V2-wpHZZ
mvaEleID-Fall17-iso-V2-wpLoose
mvaEleID-Fall17-noIso-V1-wp80
mvaEleID-Fall17-noIso-V1-wp90
mvaEleID-Fall17-noIso-V1-wpLoose
mvaEleID-Fall17-noIso-V2-wp80
mvaEleID-Fall17-noIso-V2-wp90
mvaEleID-Fall17-noIso-V2-wpLoose
mvaEleID-RunIIIWinter22-iso-V1-wp80
mvaEleID-RunIIIWinter22-iso-V1-wp90
mvaEleID-RunIIIWinter22-noIso-V1-wp80
mvaEleID-RunIIIWinter22-noIso-V1-wp90
mvaEleID-Spring16-GeneralPurpose-V1-wp80
mvaEleID-Spring16-GeneralPurpose-V1-wp90
mvaEleID-Spring16-HZZ-V1-wpLoose
mvaEleID-Summer16UL-ID-ISO-HZZ
mvaEleID-Summer17UL-ID-ISO-HZZ
mvaEleID-Summer18UL-ID-ISO-HZZ
mvaEleID-Winter22-HZZ-V1

@Prasant1993
Copy link
Contributor

Prasant1993 commented Nov 25, 2023

Hi @apetkovi1,
Okay I see. The ID is added to pat electrons in MiniAOD successfully.
Lets check whether you have this ID in NANOAOD.

You can produce a NanoAOD file from the above MiniAOD file produced using the cmsDriver.py command.
Assuming your workflow directory "12434.0_TTbar_14TeV+2023" is present in the CMSSW/src directory:

cmsDriver.py step2 -s NANO,DQM:@nanoAODDQM --process NANO --mc --eventcontent NANOAODSIM,DQM --datatier NANOAODSIM,DQMIO -n 10000 --customise "Configuration/DataProcessing/Utils.addMonitoring" --era Run3 --conditions auto:phase1_2022_realistic --filein file:12434.0_TTbar_14TeV+2023/step3_inMINIAODSIM.root

You can check the root file produced for your new ID: step2_NANO_DQM.root

You may need to add the ID in Nano DQM histograms as well here : https://github.com/cms-sw/cmssw/blob/master/PhysicsTools/NanoAOD/python/nanoDQM_cfi.py#L49

@apetkovi1
Copy link
Author

Hi @Prasant1993. I created step2_NANO_DQM.root in a way you wrote. I went to check the content
root step2_NANO_DQM.root Events->Print() and I see branches luminosityBlock, run, event and bunchCrossing. So, this ID is not stored in a branch ? How do I see it ?

@Prasant1993
Copy link
Contributor

Prasant1993 commented Nov 25, 2023

Hi @apetkovi1,
This is strange to me.

When you print the Event tree,
Events->Print()

You should be able to see the Electron branches in the tree as well as other physics objects like photon, jets etc.

For example in the Electron branch shoud look like the following:

*Br 72 :Electron_lostHits : UChar_t number of missing inner hits *
*Entries : 10 : Total Size= 777 bytes File Size = 145 *
*Baskets : 1 : Basket Size= 32000 bytes Compression= 1.00 *
............................................................................
*Br 73 :Electron_mvaIso_WP80 : Bool_t MVA Iso ID WP80, Winter22V1 *
*Entries : 10 : Total Size= 788 bytes File Size = 148 *
*Baskets : 1 : Basket Size= 32000 bytes Compression= 1.00 *
............................................................................
*Br 74 :Electron_mvaIso_WP90 : Bool_t MVA Iso ID WP90, Winter22V1 *
*Entries : 10 : Total Size= 788 bytes File Size = 148 *
*Baskets : 1 : Basket Size= 32000 bytes Compression= 1.00 *
............................................................................
*Br 75 :Electron_mvaNoIso_WP80 : Bool_t MVA noIso ID WP80, Winter22V1 *
*Entries : 10 : Total Size= 798 bytes File Size = 150 *
*Baskets : 1 : Basket Size= 32000 bytes Compression= 1.00 *
............................................................................
*Br 76 :Electron_mvaNoIso_WP90 : Bool_t MVA noIso ID WP90, Winter22V1 *
*Entries : 10 : Total Size= 798 bytes File Size = 150 *
*Baskets : 1 : Basket Size= 32000 bytes Compression= 1.00 *
............................................................................

@apetkovi1
Copy link
Author

Hi @Prasant1993 ok now I see that the command had error Product not found (Photon ID ???):

NANO,DQM:@nanoAODDQM
entry file:step3_inMINIAODSIM.root
Step: NANO Spec:
in prepare_nano nanoSequenceMC
Step: DQM Spec: ['@nanoAODDQM']
customising the process with addMonitoring from Configuration/DataProcessing/Utils
customising the process with nanoAOD_customizeCommon from PhysicsTools/NanoAOD/nano_cff
Starting cmsRun step2_NANO_DQM.py
25-Nov-2023 14:51:40 CET Initiating request to open file file:step3_inMINIAODSIM.root
25-Nov-2023 14:51:42 CET Successfully opened file file:step3_inMINIAODSIM.root
: Booking "electronMVATTH" of type "BDT" from /cvmfs/cms.cern.ch/slc7_amd64_gcc12/cms/cmssw/CMSSW_13_3_0/external/slc7_amd64_gcc12/data/PhysicsTools/NanoAOD/data/el_BDTG_2017.weights.xml.
: Reading weight file: /cvmfs/cms.cern.ch/slc7_amd64_gcc12/cms/cmssw/CMSSW_13_3_0/external/slc7_amd64_gcc12/data/PhysicsTools/NanoAOD/data/el_BDTG_2017.weights.xml

DataSetInfo : [Default] : Added class "Signal" DataSetInfo : [Default] : Added class "Background" : Booked classifier "BDTG" of type: "BDT" : Booking "muonMVALowPt" of type "BDT" from /cvmfs/cms.cern.ch/slc7_amd64_gcc12/cms/cmssw/CMSSW_13_3_0/external/slc7_amd64_gcc12/data/PhysicsTools/NanoAOD/data/mu_BDTG_lowpt.weights.xml. : Reading weight file: /cvmfs/cms.cern.ch/slc7_amd64_gcc12/cms/cmssw/CMSSW_13_3_0/external/slc7_amd64_gcc12/data/PhysicsTools/NanoAOD/data/mu_BDTG_lowpt.weights.xml DataSetInfo : [Default] : Added class "Signal" DataSetInfo : [Default] : Added class "Background" : Booked classifier "BDTG" of type: "BDT" : Booking "muonMVATTH" of type "BDT" from /cvmfs/cms.cern.ch/slc7_amd64_gcc12/cms/cmssw/CMSSW_13_3_0/external/slc7_amd64_gcc12/data/PhysicsTools/NanoAOD/data/mu_BDTG_2017.weights.xml. : Reading weight file: /cvmfs/cms.cern.ch/slc7_amd64_gcc12/cms/cmssw/CMSSW_13_3_0/external/slc7_amd64_gcc12/data/PhysicsTools/NanoAOD/data/mu_BDTG_2017.weights.xml DataSetInfo : [Default] : Added class "Signal" DataSetInfo : [Default] : Added class "Background" : Booked classifier "BDTG" of type: "BDT" %MSG-w LogicError: GenWeightsTableProducer:genWeightsTable@beginRun 25-Nov-2023 14:51:51 CET Run: 1 ::getByLabel: An attempt was made to read a Run product before endRun() was called. The product is of type 'LHERunInfoProduct'. The specified ModuleLabel was 'externalLHEProducer'. The specified productInstanceName was ''.

%MSG
%MSG-w LogicError: GenWeightsTableProducer:genWeightsTable@beginRun 25-Nov-2023 14:51:51 CET Run: 1
::getByLabel: An attempt was made to read a Run product before endRun() was called.
The product is of type 'LHERunInfoProduct'.
The specified ModuleLabel was 'source'.
The specified productInstanceName was ''.

%MSG
%MSG-w LogicError: HTXSRivetProducer:rivetProducerHTXS@beginRun 25-Nov-2023 14:51:51 CET Run: 1
::getByLabel: An attempt was made to read a Run product before endRun() was called.
The product is of type 'LHERunInfoProduct'.
The specified ModuleLabel was 'externalLHEProducer'.
The specified productInstanceName was ''.

%MSG
Begin processing the 1st record. Run 1, Event 1, LumiSection 1 on stream 0 at 25-Nov-2023 14:51:51.497 CET
#--------------------------------------------------------------------------

FastJet release 3.4.1

M. Cacciari, G.P. Salam and G. Soyez

A software package for jet finding and analysis at colliders

http://fastjet.fr

Please cite EPJC72(2012)1896 [arXiv:1111.6097] if you use this package

for scientific work and optionally PLB641(2006)57 [hep-ph/0512210].

FastJet is provided without warranty under the GNU GPL v2 or higher.

It uses T. Chan's closest pair algorithm, S. Fortune's Voronoi code

and 3rd party plugin jet algorithms. See COPYING file for details.

#--------------------------------------------------------------------------
%MSG-w LHETablesProducer: GenWeightsTableProducer:genWeightsTable 25-Nov-2023 14:51:54 CET Run: 1 Event: 1
No LHEEventProduct, so there will be no LHE Tables

%MSG
Rivet.AnalysisHandler: INFO Using named weights

======== HiggsTemplateCrossSections Initialization =========

Rivet.Analysis.HiggsTemplateCrossSections: WARN No HIGGSPRODMODE shell variable found. Needed when running Rivet stand-alone.

======== Higgs prod mode 0 =========
======== Sucessful Initialization =========

Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
Rivet.AnalysisHandler: INFO Using named weights
----- Begin Fatal Exception 25-Nov-2023 14:51:55 CET-----------------------
An exception of category 'ProductNotFound' occurred while
[0] Processing Event run: 1 lumi: 1 event: 1 stream: 0
[1] Running path 'dqmoffline_step'
[2] Prefetching for module NanoAODDQM/'nanoDQMMC'
[3] Prefetching for module CandMCMatchTableProducer/'boostedTauMCTable'
[4] Prefetching for module PATObjectCrossLinker/'linkedObjects'
[5] Prefetching for module PATPhotonRefSelector/'finalPhotons'
[6] Prefetching for module PATPhotonUserDataEmbedder/'slimmedPhotonsWithUserData'
[7] Calling method for module PhoVIDNestedWPBitmapProducer/'bitmapVIDForPho'
Exception Message:
Principal::getByToken: Found zero products matching all criteria
Looking for type: edm::ValueMapvid::CutFlowResult
Looking for module label: egmPhotonIDs
Looking for productInstanceName: cutBasedPhotonID-RunIIIWinter22-122X-V1-loose

Additional Info:
[a] If you wish to continue processing events after a ProductNotFound exception,
add "TryToContinue = cms.untracked.vstring('ProductNotFound')" to the "options" PSet in the configuration.

----- End Fatal Exception -------------------------------------------------
Rivet.Analysis.HiggsTemplateCrossSections: INFO ======================================================
Rivet.Analysis.HiggsTemplateCrossSections: INFO Higgs Template X-Sec Categorization Tool
Rivet.Analysis.HiggsTemplateCrossSections: INFO Status Code Summary
Rivet.Analysis.HiggsTemplateCrossSections: INFO ======================================================
Rivet.Analysis.HiggsTemplateCrossSections: INFO >>>> All 0 events successfully categorized!
Rivet.Analysis.HiggsTemplateCrossSections: INFO ======================================================
Rivet.Analysis.HiggsTemplateCrossSections: INFO ======================================================
25-Nov-2023 14:51:55 CET Closed file file:step3_inMINIAODSIM.root
TimeReport> Time report complete in 31.3644 seconds
Time Summary:

  • Min event: 3.69184
  • Max event: 3.69184
  • Avg event: 3.69184
  • Total loop: 10.264
  • Total init: 21.1002
  • Total job: 31.3644
  • Total EventSetup: 2.30291
  • Total non-module: 0.311602
    Event Throughput: 0.0974274 ev/s
    CPU Summary:
  • Total loop: 7.05964
  • Total init: 24.0318
  • Total extra: 0
  • Total children: 0.215381
  • Total job: 31.0916
    Processing Summary:
  • Number of Events: 1
  • Number of Global Begin Lumi Calls: 1
  • Number of Global Begin Run Calls: 1

The MCnet usage guidelines apply to Rivet: see http://www.montecarlonet.org/GUIDELINES
Please acknowledge Rivet in results made using it, and cite https://arxiv.org/abs/1912.05451

@Prasant1993
Copy link
Contributor

Hi @apetkovi1,

This PR has nothing to do with Photon. There should not be any error for accessing the existing photonIDs.

I am just curious, did you run the above cmsDriver.py command in the CMSSW/src directory to produce the NanoAOD ?

Otherwise, One more workaround can be the following:
git-cms-addpkg RecoEgamma/PhotonIdentification
scram b -j8
Run the cmsDriver.py again to produce the NANOAOD.

@apetkovi1
Copy link
Author

apetkovi1 commented Nov 25, 2023

Hi @Prasant1993 , yes I am running locally from CMSSW_13_3_0/src (I am tracking master branch, not the CMSSW_13_3_0). I added photon package but message stays the same. I am suspecting now that there is some interference between master branch and my local CMSSW_13_3_0. What I do is that I first create CMSSW area cmsrel CMSSW_13_3_0 cd CMSSW_13_3_0/src cmsenv. Then I add needed packages e.g. git-cms-addpkg RecoEgamma/ElectronIdentification. After that, since I should send PR to master branch I start developing from master branch by doing git checkout --track official-cmssw/master. Is this the right way ? I am suspecting that by doing this I am mixing packages that are from master branch (in this case RecoEgamma/ElectronIdentification) with rest of them which belong to my local CMSSW_13_3_0.

EDIT:
I re-did all of this in CMSSW_14_0_X_2023-11-25-1100 locally and now it works. Seems that problem was due to mixing of releases.

@a-kapoor can I close this PR and send it from another branch (the one created from 14_0_...) ?

@Prasant1993
Copy link
Contributor

Hi @Prasant1993 , yes I am running locally from CMSSW_13_3_0/src (I am tracking master branch, not the CMSSW_13_3_0). I added photon package but message stays the same. I am suspecting now that there is some interference between master branch and my local CMSSW_13_3_0. What I do is that I first create CMSSW area cmsrel CMSSW_13_3_0 cd CMSSW_13_3_0/src cmsenv. Then I add needed packages e.g. git-cms-addpkg RecoEgamma/ElectronIdentification. After that, since I should send PR to master branch I start developing from master branch by doing git checkout --track official-cmssw/master. Is this the right way ? I am suspecting that by doing this I am mixing packages that are from master branch (in this case RecoEgamma/ElectronIdentification) with rest of them which belong to my local CMSSW_13_3_0.

EDIT: I re-did all of this in CMSSW_14_0_X_2023-11-25-1100 locally and now it works. Seems that problem was due to mixing of releases.

@a-kapoor can I close this PR and send it from another branch (the one created from 14_0_...) ?

Hi @apetkovi1,
It's good that, you found the issue already and solved it. May be it is better to close the PR and start a fresh one targeting to cmssw/master branch provided all the necessary validation steps are completed successfully.

If you would like to give a presentation again in the EGM POG meeting for you new IDs using PF cluster isolation variables instead of particle isolations, it will be more appreciated and help us to approve the ID. I let @a-kapoor and @RSalvatico comment more on this.

@a-kapoor
Copy link
Contributor

Hi @Prasant1993 , yes I am running locally from CMSSW_13_3_0/src (I am tracking master branch, not the CMSSW_13_3_0). I added photon package but message stays the same. I am suspecting now that there is some interference between master branch and my local CMSSW_13_3_0. What I do is that I first create CMSSW area cmsrel CMSSW_13_3_0 cd CMSSW_13_3_0/src cmsenv. Then I add needed packages e.g. git-cms-addpkg RecoEgamma/ElectronIdentification. After that, since I should send PR to master branch I start developing from master branch by doing git checkout --track official-cmssw/master. Is this the right way ? I am suspecting that by doing this I am mixing packages that are from master branch (in this case RecoEgamma/ElectronIdentification) with rest of them which belong to my local CMSSW_13_3_0.

EDIT: I re-did all of this in CMSSW_14_0_X_2023-11-25-1100 locally and now it works. Seems that problem was due to mixing of releases.

@a-kapoor can I close this PR and send it from another branch (the one created from 14_0_...) ?

Hi @apetkovi1 That explains it. Yes, please create another branch and start a fresh pull request. This time, attach the results of runTheMatrix and your private validation with the description. Thanks.

@a-kapoor
Copy link
Contributor

please close

@cmsbuild cmsbuild closed this Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants