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

Add HZZ electron ID for Run3 #43430

Merged
merged 5 commits into from
Jan 15, 2024
Merged

Conversation

apetkovi1
Copy link

@apetkovi1 apetkovi1 commented Nov 29, 2023

This PR is to add HZZ electron ID for Run 3. It has been tested with runTheMatrix (logs are in (1,2,3,4,5)). Also it has been tested with 2016 workflow since previously Run2 tests caused failure (log is in (6)) Additionally it has been tested privately to check if the sig. and bkg. efficiency correspond to the ones I got when testing during the training phase. Comparison is in (7). Essentially I ran testElectronMVARun3 and calculated sig and bkg efficiency in every region. Now, as you can see, testing with testElectronMVARun3 gave slightly better performance (higher sig and lower bkg eff) then test during the training phase. This is because I ran testElectronMVARun3 on a dataset which also partially includes the one which I used for training. This is because during the training phase I made random test/train splitting and did not save the test dataset. This is why I do not have completely unbiased testing sample when I use testElectronMVARun3. However, when we take into account the fact that part of this dataset was used for training, the results are expected. Please test this PR together with this one. ID presentation is in (8).

(1) step1_TTbar_14TeV+2023.log
(2) step2_TTbar_14TeV+2023.log
(3) step3_TTbar_14TeV+2023.log
(4) step4_TTbar_14TeV+2023.log
(5) step5_TTbar_14TeV+2023.log
(6) step5_TTbar_13.log
(7) MVAcomparison.pdf
(8) ElectronID_EGamma_v2.pdf

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43430/37964

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 29, 2023

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, @vlimant, @cmsbuild, @simonepigazzini, @jfernan2 can you please review it and eventually sign? Thanks.
@jdolen, @JyothsnaKomaragiri, @Sam-Harper, @varuns23, @seemasharmafnal, @hatakeyamak, @sameasy, @gpetruc, @Prasant1993, @sobhatta, @nhanvtran, @lgray, @AnnikaStein, @jdamgov, @Ming-Yan, @demuller, @andrzejnovak, @emilbols, @valsdav, @ram1123, @mariadalfonso, @mmarionncern, @rappoccio, @missirol, @azotz, @Senphy, @a-kapoor, @schoef, @afiqaize, @gouskos, @mbluj, @AlexDeMoor, @ahinzmann, @gkasieczka, @jainshilpi 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

@a-kapoor
Copy link
Contributor

@apetkovi1 I just closed #43369

@a-kapoor
Copy link
Contributor

enable nano

@a-kapoor
Copy link
Contributor

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

@cmsbuild
Copy link
Contributor

-1

Failed Tests: RelVals RelVals-INPUT RelVals-NANO
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f7b9c7/36162/summary.html
COMMIT: a75a3d6
CMSSW: CMSSW_14_0_X_2023-11-28-2300/el8_amd64_gcc12
Additional Tests: NANO
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/43430/36162/install.sh to create a dev area with all the needed externals and cmssw changes.

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:

You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f7b9c7/36162/git-recent-commits.json
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f7b9c7/36162/git-merge-result

RelVals

----- Begin Fatal Exception 29-Nov-2023 15:16:18 CET-----------------------
An exception of category 'ProductNotFound' occurred while
   [0] Processing  Event run: 1 lumi: 1 event: 1 stream: 0
   [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 29-Nov-2023 15:21:24 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 29-Nov-2023 15:34:33 CET-----------------------
An exception of category 'ProductNotFound' occurred while
   [0] Processing  Event run: 1 lumi: 1 event: 1 stream: 0
   [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 -------------------------------------------------
Expand to see more relval errors ...

RelVals-INPUT

  • 2500.02500.0_NANOmc106Xul16v2/step2_NANOmc106Xul16v2.log
  • 2500.0012500.001_NANOmc106Xul17v2/step2_NANOmc106Xul17v2.log
  • 2500.0022500.002_NANOmc106Xul18v2/step2_NANOmc106Xul18v2.log

RelVals-NANO

  • 2500.02500.0_NANOmc106Xul16v2/step2_NANOmc106Xul16v2.log
  • 2500.0012500.001_NANOmc106Xul17v2/step2_NANOmc106Xul17v2.log
  • 2500.0022500.002_NANOmc106Xul18v2/step2_NANOmc106Xul18v2.log
Expand to see more relval errors ...

@apetkovi1
Copy link
Author

apetkovi1 commented Nov 29, 2023

Hi @a-kapoor, @Prasant1993 I am not sure why this fails - locally I was able to run runTheMatrix. Locally I do not have these logs (the ones where we can see error here).

@a-kapoor
Copy link
Contributor

Hi @a-kapoor, @Prasant1993 I am not sure why this fails - locally I was able to run runTheMatrix. Locally I do not have these logs (the ones where we can see error here).

Hi @apetkovi1 Can you check if you are able to run https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f7b9c7/36162/runTheMatrix-results/25202.0_TTbar_13/cmdLog

@apetkovi1
Copy link
Author

apetkovi1 commented Nov 29, 2023

Hi @a-kapoor I have updated runTheMatrix output dir with outpouts from these new tests here. When using your commands I recreate some of these errors (check step1,2,3,4,5_TTbar_13.log). Any idea what could cause them ?

EDIT: I resolved error in step5_TTbar_13.log by removing this line https://github.com/apetkovi1/cmssw/blob/a75a3d6f1a4b8be6a2945792e9e688297ea304f3/PhysicsTools/NanoAOD/python/electrons_cff.py#L188. Also, one thing that bugs me is that before I added this line there was not a single line of code in electrons_cff.py that corresponds to HZZ working point. However, I remember that in previous nanoAOD, HZZ working point was stored.

EDIT: However, now i ran runTheMatrix while removing that line from electrons_cff.py. It seems that it is necessarry, since now wpHZZ has not been added to nano. In conclusion, this line is causing an issue https://github.com/apetkovi1/cmssw/blob/a75a3d6f1a4b8be6a2945792e9e688297ea304f3/PhysicsTools/NanoAOD/python/electrons_cff.py#L188, but if I remove it, wpHZZ is not included in nano after I do runTheMatrix. Still unclear for me how to resolve this.

@Prasant1993
Copy link
Contributor

Prasant1993 commented Nov 29, 2023

Hi @apetkovi1,

I am just trying to understand here a bit more.

About this HZZ ID in the past in Run2 UL16, Ul17 and UL18, I see you have only one variable (float) defined in the NanoAOD here :

https://github.com/apetkovi1/cmssw/blob/master/PhysicsTools/NanoAOD/python/electrons_cff.py#L244.

(run2_egamma_2016).toModify(
slimmedElectronsWithUserData.userFloats,
mvaHZZIso = "electronMVAValueMapProducer:ElectronMVAEstimatorRun2Summer16ULIdIsoValues"
)
(run2_egamma_2017).toModify(
slimmedElectronsWithUserData.userFloats,
mvaHZZIso = "electronMVAValueMapProducer:ElectronMVAEstimatorRun2Summer17ULIdIsoValues"
)
(run2_egamma_2018).toModify(
slimmedElectronsWithUserData.userFloats,
mvaHZZIso = "electronMVAValueMapProducer:ElectronMVAEstimatorRun2Summer18ULIdIsoValues"
)

But for Run3 case, you have 2 variables here. One is float and the other is int.

  1. mvaHZZIso = cms.InputTag("electronMVAValueMapProducer:ElectronMVAEstimatorRun2Winter22HZZV1Values")
  2. mvaIso_WPHZZ = cms.InputTag("egmGsfElectronIDs:mvaEleID-Winter22-HZZ-V1")

Do you really need these two in Run3 ?

The above workflow is a Run2 workflow. So it doesn't find the second int variable for Run2.
May be you can add the following :
"mvaIso_WPHZZ = None" here for Run2 : https://github.com/apetkovi1/cmssw/blob/Run3_HZZelectronID_V1p3/PhysicsTools/NanoAOD/python/electrons_cff.py#L222

Try to test again.

@apetkovi1
Copy link
Author

apetkovi1 commented Nov 30, 2023

Hi @Prasant1993 @a-kapoor, I added what you said but the message stays the same (not sure what could cause this since wpHZZ is sucesfully added to nano when running runTheMatrix, proably some conflict with Run2 since wpHZZ was not added to nano back then). Now, if I would remove WPHZZ part from electrons_cff, working point would be added to miniAOD but not to nanoAOD ? (I still have HZZ working point defined in RecoEgamma/ElectronIdentification/python/FWLite.py)

@Prasant1993
Copy link
Contributor

Hi @Prasant1993 @a-kapoor, I added what you said but the message stays the same (not sure what could cause this since wpHZZ is sucesfully added to nano when running runTheMatrix, proably some conflict with Run2 since wpHZZ was not added to nano back then). Now, if I would remove WPHZZ part from electrons_cff, working point would be added to miniAOD but not to nanoAOD ? (I still have HZZ working point defined in RecoEgamma/ElectronIdentification/python/FWLite.py)

@apetkovi1, can you paste the error that you have got after did the necessary change for Run2 : "mvaIso_WPHZZ = None" ?

@apetkovi1
Copy link
Author

apetkovi1 commented Nov 30, 2023

This is my command:

cmsDriver.py step5 -s NANO -n 10 --mc --eventcontent NANOEDMAODSIM --datatier NANOAODSIM --conditions auto:run2_mc --era Run2_2016 --filein file:step3_inMINIAODSIM.root --nThreads 2 --customise Validation/Performance/TimeMemoryJobReport.customiseWithTimeMemoryJobReport --fileout file:step5.root --suffix "-j JobReport5.xml " > step5_TTbar_13.log 2>&1

Click to read the log

NANO,ENDJOB
entry file:step3_inMINIAODSIM.root
Step: NANO Spec:
in prepare_nano nanoSequenceMC
Step: ENDJOB Spec:
customising the process with customiseWithTimeMemoryJobReport from Validation/Performance/TimeMemoryJobReport
customising the process with nanoAOD_customizeCommon from PhysicsTools/NanoAOD/nano_cff
Starting cmsRun -j JobReport5.xml step5_NANO.py
%MSG-i ThreadStreamSetup: (NoModuleName) 30-Nov-2023 13:56:41 CET pre-events
setting # threads 2
setting # streams 2
%MSG
30-Nov-2023 13:56:48 CET Initiating request to open file file:step3_inMINIAODSIM.root
30-Nov-2023 13:56:50 CET Successfully opened file file:step3_inMINIAODSIM.root
: Booking "electronMVATTH" of type "BDT" from /cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02813/slc7_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-28-2300/external/slc7_amd64_gcc12/data/PhysicsTools/NanoAOD/data/el_BDTG_2016.weights.xml.
: Reading weight file: /cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02813/slc7_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-28-2300/external/slc7_amd64_gcc12/data/PhysicsTools/NanoAOD/data/el_BDTG_2016.weights.xml

DataSetInfo : [Default] : Added class "Signal" DataSetInfo : [Default] : Added class "Background" : Booked classifier "BDTG" of type: "BDT" : Booking "electronMVATTH" of type "BDT" from /cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02813/slc7_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-28-2300/external/slc7_amd64_gcc12/data/PhysicsTools/NanoAOD/data/el_BDTG_2016.weights.xml. : Reading weight file: /cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02813/slc7_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-28-2300/external/slc7_amd64_gcc12/data/PhysicsTools/NanoAOD/data/el_BDTG_2016.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-ib.cern.ch/sw/x86_64/nweek-02813/slc7_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-28-2300/external/slc7_amd64_gcc12/data/PhysicsTools/NanoAOD/data/mu_BDTG_lowpt.weights.xml. : Reading weight file: /cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02813/slc7_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-28-2300/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 "muonMVALowPt" of type "BDT" from /cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02813/slc7_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-28-2300/external/slc7_amd64_gcc12/data/PhysicsTools/NanoAOD/data/mu_BDTG_lowpt.weights.xml. : Reading weight file: /cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02813/slc7_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-28-2300/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-ib.cern.ch/sw/x86_64/nweek-02813/slc7_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-28-2300/external/slc7_amd64_gcc12/data/PhysicsTools/NanoAOD/data/mu_BDTG_2016.weights.xml. : Reading weight file: /cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02813/slc7_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-28-2300/external/slc7_amd64_gcc12/data/PhysicsTools/NanoAOD/data/mu_BDTG_2016.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-ib.cern.ch/sw/x86_64/nweek-02813/slc7_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-28-2300/external/slc7_amd64_gcc12/data/PhysicsTools/NanoAOD/data/mu_BDTG_2016.weights.xml. : Reading weight file: /cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02813/slc7_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2023-11-28-2300/external/slc7_amd64_gcc12/data/PhysicsTools/NanoAOD/data/mu_BDTG_2016.weights.xml DataSetInfo : [Default] : Added class "Signal" DataSetInfo : [Default] : Added class "Background" : Booked classifier "BDTG" of type: "BDT" %MSG-w LogicError: GenWeightsTableProducer:genWeightsTable@beginRun 30-Nov-2023 13:57:04 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: HTXSRivetProducer:rivetProducerHTXS@beginRun 30-Nov-2023 13:57:04 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 30-Nov-2023 13:57:04 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
Begin processing the 1st record. Run 1, Event 1, LumiSection 1 on stream 1 at 30-Nov-2023 13:57:04.847 CET
Begin processing the 2nd record. Run 1, Event 2, LumiSection 1 on stream 0 at 30-Nov-2023 13:57:04.848 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 30-Nov-2023 13:57:06 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
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 30-Nov-2023 13:57:25.886 CET
Begin processing the 4th record. Run 1, Event 4, LumiSection 1 on stream 1 at 30-Nov-2023 13:57:25.895 CET
Rivet.Analysis.HiggsTemplateCrossSections: WARN Unkown Higgs production mechanism. Cannot classify event. Classification for all events will most likely fail.
: Rebuilding Dataset Default
: Rebuilding Dataset Default
: Rebuilding Dataset Default
----- Begin Fatal Exception 30-Nov-2023 13:57:26 CET-----------------------
An exception of category 'UnknownUserInt' occurred while
[0] Processing Event run: 1 lumi: 1 event: 3 stream: 0
[1] Running path 'NANOEDMAODSIMoutput_step'
[2] Prefetching for module PoolOutputModule/'NANOEDMAODSIMoutput'
[3] Calling method for module SimpleCandidateFlatTableProducer/'electronTable'
Exception Message:
Requested UserInt mvaIso_WPHZZ is not available! Possible UserInts are:
ElectronMVAEstimatorRun2Fall17IsoV1Categories ElectronMVAEstimatorRun2Fall17IsoV2Categories ElectronMVAEstimatorRun2Fall17NoIsoV1Categories ElectronMVAEstimatorRun2Fall17NoIsoV2Categories ElectronMVAEstimatorRun2RunIIIWinter22IsoV1Categories ElectronMVAEstimatorRun2RunIIIWinter22NoIsoV1Categories ElectronMVAEstimatorRun2Spring16GeneralPurposeV1Categories ElectronMVAEstimatorRun2Spring16HZZV1Categories ElectronMVAEstimatorRun2Summer18ULIdIsoCategories ElectronMVAEstimatorRun2Winter22HZZV1Categories VIDNestedWPBitmapHEEP VIDNestedWPBitmap_Fall17V2 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 cutBasedID_Fall17V2_loose cutBasedID_Fall17V2_medium cutBasedID_Fall17V2_tight cutBasedID_Fall17V2_veto cutBasedID_HEEP heepElectronID-HEEPV70 heepElectronID-HEEPV71 mvaIso_Fall17V2_WP80 mvaIso_Fall17V2_WP90 mvaIso_Fall17V2_WPL mvaNoIso_Fall17V2_WP80 mvaNoIso_Fall17V2_WP90 mvaNoIso_Fall17V2_WPL seedGain
----- End Fatal Exception -------------------------------------------------
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 ======================================================
30-Nov-2023 13:57:27 CET Closed file file:step3_inMINIAODSIM.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

This is era 2016 and it seems it is trying to find wpHZZ among Run 2 working points even tough I added mvaIso_WPHZZ = None

@cmsbuild
Copy link
Contributor

-1

Failed Tests: UnitTests RelVals RelVals-INPUT RelVals-NANO
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f7b9c7/36773/summary.html
COMMIT: 9eeb80d
CMSSW: CMSSW_14_0_X_2024-01-09-2300/el8_amd64_gcc12
Additional Tests: NANO
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/43430/36773/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 10-Jan-2024 11:24:08 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/Winter22HZZV1/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/week1/cms-sw/cmssw/43430/36773/CMSSW_14_0_X_2024-01-09-2300/poison:/cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/43430/36773/CMSSW_14_0_X_2024-01-09-2300/src:/cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/43430/36773/CMSSW_14_0_X_2024-01-09-2300/external/el8_amd64_gcc12/data:/cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02819/el8_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2024-01-09-2300/poison:/cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02819/el8_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2024-01-09-2300/src:/cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02819/el8_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2024-01-09-2300/external/el8_amd64_gcc12/data
Current directory is: /data/cmsbld/jenkins/workspace/ib-run-pr-relvals/matrix-results/136.7611_RunJetHT2016EreMINIAOD
----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 10-Jan-2024 11:24:08 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/Winter22HZZV1/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/week1/cms-sw/cmssw/43430/36773/CMSSW_14_0_X_2024-01-09-2300/poison:/cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/43430/36773/CMSSW_14_0_X_2024-01-09-2300/src:/cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/43430/36773/CMSSW_14_0_X_2024-01-09-2300/external/el8_amd64_gcc12/data:/cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02819/el8_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2024-01-09-2300/poison:/cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02819/el8_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2024-01-09-2300/src:/cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02819/el8_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2024-01-09-2300/external/el8_amd64_gcc12/data
Current directory is: /data/cmsbld/jenkins/workspace/ib-run-pr-relvals/matrix-results/136.8311_RunJetHT2017FreMINIAOD
----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 10-Jan-2024 11:24:10 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/Winter22HZZV1/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/week1/cms-sw/cmssw/43430/36773/CMSSW_14_0_X_2024-01-09-2300/poison:/cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/43430/36773/CMSSW_14_0_X_2024-01-09-2300/src:/cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/43430/36773/CMSSW_14_0_X_2024-01-09-2300/external/el8_amd64_gcc12/data:/cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02819/el8_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2024-01-09-2300/poison:/cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02819/el8_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2024-01-09-2300/src:/cvmfs/cms-ib.cern.ch/sw/x86_64/nweek-02819/el8_amd64_gcc12/cms/cmssw-patch/CMSSW_14_0_X_2024-01-09-2300/external/el8_amd64_gcc12/data
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 ...

RelVals-NANO

  • 2500.32500.3_NANOmc130X/step2_NANOmc130X.log
  • 2500.12500.1_NANOmc122Xrun3/step2_NANOmc122Xrun3.log
  • 2500.0012500.001_NANOmc106Xul17v2/step2_NANOmc106Xul17v2.log
Expand to see more relval errors ...

@apetkovi1
Copy link
Author

I see now in error log that test fails to find MVA weights, is the PR tested together with this one ?

@Prasant1993
Copy link
Contributor

Hi @vlimant Please issue the test command with the PR cms-data/RecoEgamma-ElectronIdentification#28

The weight files PR is not merged yet.

@a-kapoor
Copy link
Contributor

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

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f7b9c7/36801/summary.html
COMMIT: 9eeb80d
CMSSW: CMSSW_14_0_X_2024-01-10-2300/el8_amd64_gcc12
Additional Tests: NANO
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/43430/36801/install.sh to create a dev area with all the needed externals and cmssw changes.

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:

You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f7b9c7/36801/git-recent-commits.json
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f7b9c7/36801/git-merge-result

Comparison Summary

Summary:

  • You potentially added 17 lines to the logs
  • ROOTFileChecks: Some differences in event products or their sizes found
  • Reco comparison results: 773 differences found in the comparisons
  • DQMHistoTests: Total files compared: 48
  • DQMHistoTests: Total histograms compared: 3247277
  • DQMHistoTests: Total failures: 1213
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3246042
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 6.590999999999999 KiB( 47 files compared)
  • DQMHistoSizes: changed ( 11634.0,... ): 0.554 KiB Physics/NanoAODDQM
  • DQMHistoSizes: changed ( 13234.0,... ): 0.363 KiB Physics/NanoAODDQM
  • Checked 200 log files, 161 edm output root files, 48 DQM output files
  • TriggerResults: no differences found

NANO Comparison Summary

Summary:

  • You potentially removed 2 lines from the logs
  • ROOTFileChecks: Some differences in event products or their sizes found
  • Reco comparison results: 8 differences found in the comparisons
  • DQMHistoTests: Total files compared: 15
  • DQMHistoTests: Total histograms compared: 16405
  • DQMHistoTests: Total failures: 0
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 16405
  • DQMHistoTests: Total skipped: 0
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 6.4190000000000005 KiB( 14 files compared)
  • DQMHistoSizes: changed ( 2500.001,... ): 0.554 KiB Physics/NanoAODDQM
  • DQMHistoSizes: changed ( 2500.011,... ): 0.363 KiB Physics/NanoAODDQM
  • Checked 38 log files, 18 edm output root files, 15 DQM output files

Nano size comparison Summary:

Sample kb/ev ref kb/ev diff kb/ev ev/s/thd ref ev/s/thd diff rate mem/thd ref mem/thd
2500.0 2.542 2.542 0.000 ( +0.0% ) 5.26 5.16 +1.9% 2.196 2.164
2500.001 2.688 2.688 0.000 ( +0.0% ) 4.72 4.73 -0.1% 2.631 2.565
2500.002 2.625 2.625 0.000 ( +0.0% ) 4.89 4.90 -0.1% 2.610 2.574
2500.01 1.312 1.312 0.000 ( +0.0% ) 9.62 9.67 -0.6% 2.348 2.276
2500.011 1.729 1.729 0.000 ( +0.0% ) 5.23 5.30 -1.3% 2.475 2.445
2500.012 1.575 1.575 0.000 ( +0.0% ) 7.36 7.47 -1.5% 2.382 2.347
2500.1 2.191 2.190 0.001 ( +0.0% ) 5.32 5.36 -0.7% 2.112 2.075
2500.2 2.304 2.304 0.000 ( +0.0% ) 6.04 6.10 -1.0% 2.025 1.992
2500.21 1.180 1.180 0.000 ( +0.0% ) 4.34 4.36 -0.6% 2.305 2.289
2500.211 1.543 1.542 0.001 ( +0.0% ) 3.72 3.82 -2.4% 2.283 2.371
2500.3 2.059 2.059 0.000 ( +0.0% ) 12.58 12.91 -2.5% 2.013 1.976
2500.31 1.255 1.255 0.000 ( +0.0% ) 19.95 20.42 -2.3% 2.404 2.355
2500.311 1.642 1.642 0.001 ( +0.0% ) 12.90 13.43 -3.9% 2.492 2.436
2500.312 7.025 7.025 0.000 ( +0.0% ) 1.33 1.36 -2.6% 1.744 1.712
2500.313 1.471 1.471 0.000 ( +0.0% ) 5.74 7.01 -18.1% 1.077 1.043
2500.4 2.059 2.059 0.000 ( +0.0% ) 12.61 12.90 -2.2% 2.019 1.982
2500.5 19.575 19.575 0.000 ( +0.0% ) 1.07 1.24 -13.1% 1.143 1.165

@a-kapoor
Copy link
Contributor

Hi @vlimant
So a new ID has been
So the older values in Run3 Nanos were using :

mvaHZZIso = cms.InputTag("electronMVAValueMapProducer:ElectronMVAEstimatorRun2Summer18ULIdIsoValues"),

Which has now changed to

mvaHZZIso = cms.InputTag("electronMVAValueMapProducer:ElectronMVAEstimatorRun2Winter22HZZV1Values"),

This is now the default.

The differences in this https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisonsNANO/CMSSW_14_0_X_2024-01-10-2300+f7b9c7/60552/validateJR.html make sense since the new ID are not extremely different, but just a "Run 3" fine-tuned version. The "Run 2" version was used for Run 3 as well till Nanov13 since the new trained ID was not available at that point.

It makes sense here that the new ID for ttbar tells us there is more background:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisonsNANO/CMSSW_14_0_X_2023-12-06-1100+f7b9c7/60182/validateJR/2500.21_NANOdata124Xrun3/all_NANO_step2/c_Electron_mvaHZZIso.png
because most of ttbar is background anyway. The new ID does what it should do.

Even for Mini, It makes sense that the size of userfloat and userints change by "1":
https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_14_0_X_2024-01-10-2300+f7b9c7/60553/validateJR/25.0_TTbar/all_mini_RECO_step3_inMINIAODSIM/c_patElectrons_slimmedElectrons__RECO_obj_userInts_AT_size.png
https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_14_0_X_2024-01-10-2300+f7b9c7/60553/validateJR/25.0_TTbar/all_mini_RECO_step3_inMINIAODSIM/c_patElectrons_slimmedElectrons__RECO_obj_userFloats_AT_size.png
, which is what causes the differences in reco.

Overall, the changes are expected.

Tests are all passed, and it would be awesome if this could go ahead. Let me know.

Tagging @RSalvatico @apetkovi1 @Prasant1993

@vlimant
Copy link
Contributor

vlimant commented Jan 15, 2024

got it

@vlimant
Copy link
Contributor

vlimant commented Jan 15, 2024

+1

@jfernan2
Copy link
Contributor

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @antoniovilela, @rappoccio (and backports should be raised in the release meeting by the corresponding L2)

@rappoccio
Copy link
Contributor

+1

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.

8 participants