-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Electron and photon masses are set to zero #36954
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36954/28308
|
A new Pull Request was created by @rgoldouz (Reza Goldouzian) for master. It involves the following packages:
@jpata, @cmsbuild, @clacaputo, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
thanks @rgoldouz. should the previous PR be closed? If so, please close the old one. |
Hi @jpata Done. Thanks, |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-5d6736/22402/summary.html Comparison SummarySummary:
|
I'm surprised to see differences in MET corrections and uncertainties: https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_12_3_X_2022-02-13-2300+5d6736/48363/validateJR/all_mini_OldVSNew_RunDoubleEG2017Cwf136p793/all_mini_OldVSNew_RunDoubleEG2017Cwf136p793c_patMETs_slimmedMETs__reRECO_obj_0__corrections__1__dpx58.png maybe @michaelwassmer has some idea why this can happen by changing the electron mass? |
just a kind ping on this. it may be useful for JME experts to weigh in if the change is expected. |
Sorry for not answering earlier. This week I'm already busy with a lot of other things, so I try to have a look at it next week. |
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-5d6736/22733/summary.html Comparison SummarySummary:
|
what I don't understand here is why only the MET corrections differ, and not the MET itself, if the electron 4-vector changes. |
please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36954/28708
|
Pull request #36954 was updated. @jpata, @clacaputo, @slava77 can you please check and sign again. |
Uhm, @rgoldouz what you did instead was to add two more (empty) commits with the title that @qliphy suggested for this PR. And this by the way forced us to relaunch the tests. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-5d6736/22889/summary.html Comparison SummarySummary:
|
+reconstruction
|
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. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
type egamma it's rather hard to find out later on unless its tagged as egamma... so... |
Hello,
The electron and photon mass are not saved properly and nanoAOD users reported that many times. It is not related to nanoAOD. The problem is available in miniAOD too.
You can check the printout here
root [6] Events->Scan("Photon_mass:Electron_mass:Muon_mass:Tau_mass")
I checked and found that the problem is not from the EGamma code but from TLorentzVector root class. I found that the TLorentz vector is set via pxpypzE for all object candidates. It seems fine but when I tested locally for a particle with pxpypzE=(1,1,1,sqrt(3)) I did not get the mass==0. You can easily reproduce it
root -l
root [1] typedef ROOT::Math::LorentzVector<ROOT::Math::PxPyPzE4D > XYZTLorentzVectorD
root [2] XYZTLorentzVectorD newP4(1,1,1,sqrt(3));
root [3] newP4.M()
(double) -2.1073424e-08
It is because of the precision problem in TLorentz vector and it is recommended to use PxPyPzM to have correct masses for low mass objects.
https://root.cern.ch/doc/master/classROOT_1_1Math_1_1PxPyPzM4D.html
So I set the electron and photon masses by hand to 0 GeV , respectively.
Thanks,
Reza