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

Developments to provide facilitated access to new TauID information (all high level changes) #18244

Merged

Conversation

roger-wolf
Copy link
Contributor

This is a PR that had been stalled on 90X since cmssw was just in the transition to 91X. Comments from RECO formerly made here (#17624) have now been addressed and the PR migrated to 91X. I'm copying the comments of the former PR here once again to make clear hat this is about. Note that these developments are most relevant for current analyses so upon integration they will require backports down to 81X.

Dear colleagues,

this pull request comprises three developments that have been made to facilitate the access to new TauID information that is now available based on trainings made on the whole 2016 dataset.

  • configuring access to the new MVATauID training that has been made on the full 2016 dataset.
  • introducing a bypass for a variable that could be missing on miniAOD (phiAtEcalEntrace) -- when set to true by configuration this variable can be approximated from existing miniAOD information. This is in the first place in preparation for a backport to 80X, where this issue occurs. By default and for CMSSW>=8_1_X the parameter will be false.
  • adding a producer plugin (PATTauIDEmbedder) that allows to write a slimmedTau collection back into the EDM event content with updated MVAIsolation and MVA electron identification.

All these changes are "high level" with effect only on the analysis level on already existing miniAOD. They are meant for the currently ongoing analyses with the actual target to be backported down to CMSSW_8_0_X.

Neither unit/matrixTests nor DQM plots tracking physics performance should be affected by these changes.

Cheers,
Roger

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 6, 2017

A new Pull Request was created by @roger-wolf (Roger Wolf) for master.

It involves the following packages:

DataFormats/PatCandidates
RecoTauTag/Configuration
RecoTauTag/RecoTau

@perrotta, @cmsbuild, @slava77, @monttj, @davidlange6 can you please review it and eventually sign? Thanks.
@gpetruc, @gouskos, @cbernet this is something you requested to watch as well.
@Muzaffar, @davidlange6, @smuzaffar you are the release manager for this.

cms-bot commands are listed here

@slava77
Copy link
Contributor

slava77 commented Apr 6, 2017

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 6, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/18977/console Started: 2017/04/06 14:43

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 6, 2017

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 6, 2017

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 6, 2017

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

Comparison Summary:

  • No significant changes to the logs found
  • ROOTFileChecks: Some differences in event products or their sizes found
  • results differ 1232 all_OldVSNew_TTbarPUwf50202p0 JR results differ 376 all_mini_OldVSNew_TTbarPUwf50202p0 SUMMARY Reco comparison results: 1608 differences found in the comparisons
  • DQMHistoTests: Total files compared: 23
  • DQMHistoTests: Total histograms compared: 1913135
  • DQMHistoTests: Total failures: 36094
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 1876868
  • DQMHistoTests: Total skipped: 173
  • DQMHistoTests: Total Missing objects: 0
  • Checked 94 log files, 14 edm output root files, 23 DQM output files

…, requires a few knock-on adaptations in several files
@cmsbuild
Copy link
Contributor

Pull request #18244 was updated. @perrotta, @cmsbuild, @slava77, @monttj, @davidlange6 can you please check and sign again.

@@ -104,7 +112,7 @@ double PATTauDiscriminationAgainstElectronMVA6::discriminate(const TauRef& theTa
double deltaREleTau = deltaR(theElectron.p4(), theTauRef->p4());
deltaRDummy = deltaREleTau;
if( deltaREleTau < 0.3 ){
double mva_match = mva_->MVAValue(*theTauRef, theElectron, usePhiAtEcalEntranceExtrapolation_);
double mva_match = mva_->MVAValue(*theTauRef, theElectron, usePhiAtEcalEntranceExtrapolation_, bField_);
Copy link
Contributor

Choose a reason for hiding this comment

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

why not set bField in the mva::beginEvent call ?
It seems like a simpler solution with fewer changes in interfaces.

{
bool result = false;
double bField = 3.8; // hopefully Teslas are proper units (better to take it from event setup)
//double bField = 3.8; // hopefully Teslas are proper units (better to take it from event setup)
Copy link
Contributor

Choose a reason for hiding this comment

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

the comment can be now removed

@cmsbuild
Copy link
Contributor

Pull request #18244 was updated. @perrotta, @cmsbuild, @slava77, @monttj, @davidlange6 can you please check and sign again.

@slava77
Copy link
Contributor

slava77 commented Apr 25, 2017

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 25, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/19372/console Started: 2017/04/25 14:22

@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-18244/19372/summary.html

Comparison Summary:

  • You potentially added 29 lines to the logs
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 23
  • DQMHistoTests: Total histograms compared: 1780076
  • DQMHistoTests: Total failures: 14948
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 1764955
  • DQMHistoTests: Total skipped: 173
  • DQMHistoTests: Total Missing objects: 0
  • Checked 94 log files, 14 edm output root files, 23 DQM output files

@slava77
Copy link
Contributor

slava77 commented Apr 25, 2017

+1

for #18244 48fa4c5

  • changes are in line with the description: default behavior of algorithms running in reco/miniAOD is unchanged
  • jenkins tests pass and comparisons with baseline show no differences

#include "MagneticField/Engine/interface/MagneticField.h"
#include "MagneticField/Records/interface/IdealMagneticFieldRecord.h"

#include <TMath.h>
Copy link
Contributor

Choose a reason for hiding this comment

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

hi @roger-wolf - is this needed?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hi David,

I'm not sure I understand what you are referring to, therefore I'll answer to both interpretations that I'm having:

(1)
The MagneticFiled headers are needed for the track extrapolation we are doing in case that the variable "phiAtEcalEntrace" has not been pre-calculated to be saved in miniAOD (the Bfield is used in function atECalEntrance).

(2)
TMath actually is not used any more as it seem to me. If you want me to do it I could delete the line and recommit, while I'm a bit hesitant to start the whole signing and testing procedure again on this long thread.

Cheers,
Roger

Copy link
Contributor

Choose a reason for hiding this comment

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

it was about the TMath.h include - please remove in a follow up PR.

reco::Candidate const* signalCand = signalCands[o].get();
float phi = theTau.phi();
math::XYZPoint aPos;
if ( atECalEntrance(signalCand, aPos) == true ) phi = aPos.Phi();
Copy link
Contributor

Choose a reason for hiding this comment

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

Hi @roger-wolf - just to be sure I follow - this phi variable ends up meaning "phi at ecal" if the particle intersects the ecal, otherwise it is phi at the primary vertex?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hi David,

yes this is the way also the training has been done.

Cheers,
Roger

@roger-wolf
Copy link
Contributor Author

Hi all,

I think the last missing signatures are not more than formalities. @davidlange6 : would you like me to remove the header in discussion above and to recommit? Otherwise just let me know if you want/need some action from my side. Could AT also sign off in case of no further issues?

Since this is a long pending PR I'd be happy to get it off the table asap.

Cheers,
Roger

@roger-wolf
Copy link
Contributor Author

@monttj : Hi Tae Jeong, can you sign this thing off for us? I think this is the last step for us to get this PR off the table. Thanx a lot!

Cheers,
Roger

@davidlange6 davidlange6 merged commit dadb664 into cms-sw:master May 2, 2017
@roger-wolf roger-wolf deleted the CMSSW_9_1_X_tau-pog_miniAOD-tauMVAs branch November 17, 2017 10:10
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

5 participants