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

Restore Disabled PCA inputs for deepTau v2 (10_6_X) #28046

Merged
merged 2 commits into from Sep 23, 2019

Conversation

fabiocos
Copy link
Contributor

@fabiocos fabiocos commented Sep 21, 2019

PR description:

Restore #27882, revert #28032, add fix proposed in #28041 for the failures observed in the IB

PR validation:

See #28041 by @mbluj
Successfully tested with runTheMatrix.py -l 1325.51,1329.1,136.772,136.8521 -i all --ibeos

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 21, 2019

A new Pull Request was created by @fabiocos (Fabio Cossutti) for CMSSW_10_6_X.

It involves the following packages:

Configuration/Eras
Configuration/StandardSequences
PhysicsTools/NanoAOD
PhysicsTools/PatAlgos
RecoTauTag/RecoTau

@perrotta, @kpedro88, @peruzzim, @cmsbuild, @franzoni, @fgolf, @slava77, @santocch, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks.
@rappoccio, @gouskos, @felicepantaleo, @emilbols, @Martin-Grunewald, @ahinzmann, @peruzzim, @seemasharmafnal, @mmarionncern, @makortel, @smoortga, @acaudron, @dgulhan, @jdolen, @ferencek, @GiacomoSguazzoni, @rovere, @VinInn, @jdamgov, @nhanvtran, @gkasieczka, @schoef, @mariadalfonso, @clelange, @HeinerTholen, @riga, @JyothsnaKomaragiri, @mverzett, @gpetruc, @andrzejnovak, @pvmulder this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

@fabiocos
Copy link
Contributor Author

please test workflow 1325.51,1329.1,136.772,136.8521

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 21, 2019

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/2608/console Started: 2019/09/21 19:48

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-02795c/2608/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 44 differences found in the comparisons
  • DQMHistoTests: Total files compared: 33
  • DQMHistoTests: Total histograms compared: 3210949
  • DQMHistoTests: Total failures: 2
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3210613
  • DQMHistoTests: Total skipped: 334
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.047 KiB( 32 files compared)
  • DQMHistoSizes: changed ( 1325.7 ): 0.047 KiB Physics/NanoAODDQM
  • Checked 137 log files, 14 edm output root files, 33 DQM output files

@perrotta
Copy link
Contributor

backport of #27878

@perrotta
Copy link
Contributor

+1

  • This is the same as Disabled PCA inputs for deepTau v2 #27878, but the v2p1 is only activated by the Run2_2016 and Run2_2018 modifiers; Run2_2017, Run_3, Phase2 remain unchanged
  • Jenkins tests show differences in tau ID on miniAOD only in 2016 and 2018, as expected
  • The latest commit included was apparently effective in fixing the issue observed with workflows 1325.51,1329.1,136.772,136.8521

@santocch
Copy link

+1

@srimanob
Copy link
Contributor

@peruzzim Could you please have a look? Thanks.

@peruzzim
Copy link
Contributor

I have tested it for the default configurations without modifiers, and it looks ok

@peruzzim
Copy link
Contributor

+xpog

@fabiocos
Copy link
Contributor Author

+operations

no change in the main configuration part

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_10_6_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_11_0_X is complete. This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)

@fabiocos
Copy link
Contributor Author

+1

@cmsbuild cmsbuild merged commit 7ed7826 into cms-sw:CMSSW_10_6_X Sep 23, 2019
@fabiocos fabiocos deleted the fix27882 branch September 25, 2019 12:14
@@ -15,6 +15,14 @@
cut = cms.string("pt > 18 && tauID('decayModeFindingNewDMs') && (tauID('byLooseCombinedIsolationDeltaBetaCorr3Hits') || tauID('byVLooseIsolationMVArun2v1DBoldDMwLT2015') || tauID('byVLooseIsolationMVArun2v1DBnewDMwLT') || tauID('byVLooseIsolationMVArun2v1DBdR03oldDMwLT') || tauID('byVVLooseIsolationMVArun2v1DBoldDMwLT') || tauID('byVVLooseIsolationMVArun2v1DBoldDMwLT2017v2') || tauID('byVVLooseIsolationMVArun2v1DBnewDMwLT2017v2') || tauID('byVVLooseIsolationMVArun2v1DBdR03oldDMwLT2017v2') || tauID('byVVVLooseDeepTau2017v2VSjet'))")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mbluj are we sure this is correct? We are asking for the deepTau bit also in cases where it is not there, e.g. UL2017, and it will crash there, right? I can fix it with the nanoAOD PR, could you please confirm?

Copy link
Contributor

@mbluj mbluj Oct 1, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DeepTauID 2017v2 is contained in MiniAOD of UL2017 as it is now, i.e. w/o planned reMiniAOD, so check for tauID('byVVVLooseDeepTau2017v2VSjet') is correct.
What concerns planned UL2018/2016 and UL2017 reMiniAOD it will contain DeepTauID 2017v2p1 so this check is modified to tauID('byVVVLooseDeepTau2017v2p1VSjet') with corresponding era modifiers.
Regardless, I think that matrix tests will fail in case of inconsistent configurations of Mini and NanoAOD.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, sorry, I did not read carefully enough and I thought we were asking for 2p1

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.

None yet

7 participants