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
Adaptation to enable the use of a new MVAIsolation training #21022
Adaptation to enable the use of a new MVAIsolation training #21022
Conversation
The code-checks are being triggered in jenkins. |
+code-checks |
A new Pull Request was created by @roger-wolf (Roger Wolf) for master. It involves the following packages: PhysicsTools/PatAlgos @perrotta, @cmsbuild, @monttj, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
-1 Tested at: 00e4b6b The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: You can see the results of the tests here: I found follow errors while testing this PR Failed tests: UnitTests AddOn
I found errors in the following unit tests: ---> test runtestPhysicsToolsPatAlgos had ERRORS
I found errors in the following addon tests: cmsRun /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_4_X_2017-10-25-2300/src/PhysicsTools/PatAlgos/test/IntegrationTest_cfg.py : FAILED - time: date Thu Oct 26 08:29:57 2017-date Thu Oct 26 08:29:18 2017 s - exit: 17920 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Errors are related: @roger-wolf please fix |
The error is related to a work-flow where MiniAOD is produced from existing AOD, i.e. AOD with is not rerun, which does not contain a new VVLoose WP of MVAIso (added on request of SUSY and EXO). It was checked that it works with the full production chain. How it can be fixed to satisfy for unit tests? |
94X is now closed for new features. |
On Sun, Oct 29, 2017 at 9:21 PM, perrotta ***@***.***> wrote:
@mbluj <https://github.com/mbluj> @roger-wolf
<https://github.com/roger-wolf> : latest updates seem to correspond to
what was asked for.
Yes, thanks.
But there are still errors in the unit tests which were supposed to have
been cured with them: please check if anything was forgotten.
Yes, indeed the (temporary) customize to a few tests were overlooked. It
has just been fixed and hopefully this time all tests will be successful.
|
please test |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready There are some workflows for which there are errors in the baseline: Comparison Summary:
|
+1
|
@mbluj @roger-wolf : this is submitted to the master, which now corresponds to CMSSW_10_0_X. |
merge |
(but we need to finalize 80x and 94x AOD support) |
This appears to have broken the TopQuarkAnalysis unit tests. E.g. |
Unit tests are broken in
|
@@ -315,6 +316,11 @@ void PATTauProducer::produce(edm::Event & iEvent, const edm::EventSetup & iSetup | |||
edm::Handle<reco::PFTauDiscriminator> pfTauIdDiscr; | |||
iEvent.getByToken(pfTauIDTokens_[i], pfTauIdDiscr); | |||
|
|||
if(skipMissingTauID_ && !pfTauIdDiscr.isValid()){ | |||
edm::LogWarning("DataSource") << "Tau discriminator '" << tauIDSrcs_[i].first |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be made a LogInfo?
The warning shows up for every tau and just pollutes the logs.
A more informative option that will still be printed is to accumulate the number of dropped IDs and print only the first time it happens.
Dear Slava and Andrea,
this is a PR that enables the use of a new training adapted to the increase of the pT cut required for PFPhotons used for input variables for the tauID MVA, isolation sums and tau reconstruction in general, as included in our last PR (#20900).
All changes are only on the python configuration level. The anticipated changes in performance have been studied and documented here (*). The new training is based on the Summer17 MC samples and will be referred to as 2017v1.
We hope for an integration still into 94X to have the new training included in the upcoming new MC production campaign. Standard tests show no differences beyond those that we expect to see. For more details and confirmation I refer to @mbluj, @steggema and @isobelojalvo
Cheers,
Roger
(*)
https://indico.cern.ch/event/675184/contributions/2766837/attachments/1546406/2427371/mbluj_TauId_GammaPtGt1GeV_24Oct2017.pdf
https://indico.cern.ch/event/675184/contributions/2767859/attachments/1547023/2428479/mbluj_TauId_80XLegacyMiniAOD_24Oct2017.pdf