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
keeping MET sumPtUnclustered (backport of #28370) #29276
Conversation
A new Pull Request was created by @danbarto (Daniel) for CMSSW_10_2_X. It involves the following packages: DataFormats/PatCandidates @perrotta, @cmsbuild, @santocch, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
@cmsbuild please test |
The tests are being triggered in jenkins. |
thank you really much @danbarto for providing this backport |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@@ -250,6 +254,8 @@ namespace pat { | |||
|
|||
// MET significance | |||
double metSig_; | |||
// MET metSumPtUnclustered for MET Significance | |||
double metSumPtUnclustered_; |
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.
Why to change the name of this private class member wrt the one in the master?
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.
Sorry, my mistake. I'll fix that.
<class name="pat::MET" ClassVersion="15"> | ||
<version ClassVersion="15" checksum="428901429"/> | ||
<class name="pat::MET" ClassVersion="16"> | ||
<version ClassVersion="16" checksum="2969659150"/> |
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.
@Dr15Jones @slava77 (also for my own understanding): is it correct that the same ClassVersion
(here "16") can get two different checksum
's in different releases (here 10_2 vs 11_1)?
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.
Once a checksum has been assigned a version number it should not be changed. The only exception is when it is deemed that version was never used for any useful jobs.
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.
- changes of existing versions in a release are not allowed
- same versions in different releases with different checksums are not allowed
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.
Thank you @Dr15Jones and @slava77
I assume then that, once metSumPtUnclustered_
is renamed as sumPtUnclustered_
. as in the master, the very same structure in terms of class members and methods will be there for this backport and the master. Therefore the same version "16" and checksum as the master can be also backported.
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.
if for whatever reason we have to increment a version number here, we should make sure to add it to the master as well
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.
if for whatever reason we have to increment a version number here, we should make sure to add it to the master as well
Once class members and methods are sinchronized as suggested above, the same class version can be considered for both releases.
The only difference in the code itself between the master and the 10_2 backport will come from the application of the clang format updates in the master, and not yet in 10_2.
That is not enough to trigger a version number change. (And even if so, then probably both
DataFormats/PatCandidates/interface/MET.h
DataFormats/PatCandidates/src/MET.cc
can be directly copied from the version in the master, and at that point they will be absolutely identical in the two CMSSW releases).
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.
After fixing the inconsistencies in MET.h/MET.cc the version is now consistent with the master. I'll update the PR soon.
@@ -44,7 +44,8 @@ namespace metsig { | |||
JME::JetResolution & resPtObj, | |||
JME::JetResolution & resPhiObj, | |||
JME::JetResolutionScaleFactor & resSFObj, | |||
bool isRealData); | |||
bool isRealData, | |||
double& sumPtUnclustered); |
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.
fix indentation
@@ -54,7 +54,8 @@ metsig::METSignificance::getCovariance(const edm::View<reco::Jet>& jets, | |||
JME::JetResolution& resPtObj, | |||
JME::JetResolution& resPhiObj, | |||
JME::JetResolutionScaleFactor& resSFObj, | |||
bool isRealData) { | |||
bool isRealData, | |||
double& sumPtUnclustered) { |
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.
fix indentation
@cmsbuild please test |
Comparison is ready Comparison Summary:
|
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1
|
merge |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_10_2_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_11_1_X is complete. This pull request will be automatically merged. |
PR description:
The sum of the unclustered energy is one of the inputs to MET significance, but is currently not stored in miniAOD, making recomputation of the significance and the MET covariance matrix difficult. With this PR, the calculated sum of the pTs of the unclustered particles is stored, and can be accessed with metSumPtUnclustered(), similar to metSignificance().
PR validation:
All tests have been run, and were passed.
if this PR is a backport please specify the original PR and why you need to backport that PR:
backport of #28370, needed for nanoAODv7