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

Update to fix late validation plots from PR 15562 #15669

Merged
merged 2 commits into from Sep 12, 2016

Conversation

violatingcp
Copy link
Contributor

Following concerns in #15562 we have fix based on the validation plots. This results from the fact that when CandViewMerger is used, the referening of the packedcandidates to the orignal leptons is somehow broken. PuppiPhoton relies on these references to remove the give pfcandidates assigned to a good photon weight 1. If this is broken Puppi photon will add back the missing candidates even if they are there. The solution is to either run puppi no lepton or puppiphoton, but not both. The problem with this is that puppi vs puppi no lepton will reduce the MET response by a 2-3% whereas puppiphoton vs puppi will make puppiMET robust in photon+jet events. We prfer to have puppi photon. On another note, after miniAOD is run, the puppinolepton weights attached to the packed candidates give weight 1 for the leptons, so puppiphoton can be run on the miniAOD using the precomputed puppinolepton weights allowing for the best puppiMET peformance.

…en CandViewMerger is used, the referening of the packedcandidates to the orignal leptons is somehow broken. PuppiPhoton relies on these references to remove the give pfcandidates assigned to a good photon weight 1. If this is broken Puppi photon will add back the missing candidates even if they are there. The solution is to either run puppi no lepton or puppiphoton, but not both. The problem with this is that puppi vs puppi no lepton will reduce the MET response by a 2-3% whereas puppiphoton vs puppi will make puppiMET robust in photon+jet events. We prfer to have puppi photon. On another note, after miniAOD is run, the puppinolepton weights attached to the packed candidates give weight 1 for the leptons, so puppiphoton can be run on the miniAOD using the precomputed puppinolepton weights allowing for the best puppiMET peformance.
@cmsbuild
Copy link
Contributor

A new Pull Request was created by @violatingcp (Philip Harris) for CMSSW_8_1_X.

It involves the following packages:

PhysicsTools/PatAlgos

@cmsbuild, @cvuosalo, @slava77, @montjj, @davidlange6 can you please review it and eventually sign? Thanks.
@TaiSakuma, @imarches, @ahinzmann, @acaudron, @mmarionncern, @rappoccio, @jdolen, @nhanvtran, @gpetruc, @gkasieczka, @schoef, @ferencek, @mverzett, @mariadalfonso, @pvmulder, @JyothsnaKomaragiri this is something you requested to watch as well.
@slava77, @smuzaffar you are the release manager for this.

cms-bot commands are list here #13028

@@ -21,8 +21,8 @@ def makePuppies( process ):
process.puppiMerged = cms.EDProducer("CandViewMerger",src = cms.VInputTag( 'puppiNoLep','pfLeptonsPUPPET'))
process.load('CommonTools.PileupAlgos.PhotonPuppi_cff')
process.puppiForMET = process.puppiPhoton.clone()
process.puppiForMET.puppiCandName = 'puppiMerged'

#process.puppiForMET.puppiCandName = 'puppiMerged'
Copy link
Contributor

Choose a reason for hiding this comment

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

is this commented out code needed?
Please remove or add comments inline in the code why the commented out block is relevant

@slava77
Copy link
Contributor

slava77 commented Aug 30, 2016

@violatingcp please propagate the fix to 80X, better by updating #15429

@slava77
Copy link
Contributor

slava77 commented Aug 30, 2016

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Aug 30, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/14844/console

@violatingcp
Copy link
Contributor Author

Updated the PR was not merged, so the update is easier in this case.

On Tue, Aug 30, 2016 at 10:21 PM, Slava Krutelyov notifications@github.com
wrote:

@violatingcp https://github.com/violatingcp please propagate the fix to
80X, better by updating #15429
#15429


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#15669 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AE7V4Qr2T58kH564vcDo4fuCZOlBDiTxks5qlJC8gaJpZM4Jw4JW
.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@cvuosalo
Copy link
Contributor

cvuosalo commented Sep 5, 2016

I'm not sure that this PR fixes the problems seen in #15562. I tested workflow 25200.0_ZEE_13 with 500 events against baseline CMSSW_8_1_0_pre11. The test results show that the changes in Puppi jet energy and Et are not reversed by this PR. The other changes seen in #15562 are not reversed either, as seen below.
chetfrac
phoetfrac
met
metlog

@violatingcp
Copy link
Contributor Author

Thats correct. Only the effect of the electrons on the MET will change.

On Tue, Sep 6, 2016 at 12:10 AM, Carl Vuosalo notifications@github.com
wrote:

I'm not sure that this PR fixes the problems seen in #15562
#15562. I tested workflow
25200.0_ZEE_13 with 500 events against baseline CMSSW_8_1_0_pre11. The test
results show that the changes in Puppi jet energy and Et are not reversed
by this PR. The other changes seen in #15562
#15562 are not reversed either, as
seen below.
[image: chetfrac]
https://cloud.githubusercontent.com/assets/5736159/18257536/1b438030-738b-11e6-9318-f6303312d628.png
[image: phoetfrac]
https://cloud.githubusercontent.com/assets/5736159/18257539/25657866-738b-11e6-9faf-8f4c0b7bc98d.png
[image: met]
https://cloud.githubusercontent.com/assets/5736159/18257541/2e258284-738b-11e6-8443-ef15168f0a98.png
[image: metlog]
https://cloud.githubusercontent.com/assets/5736159/18257543/3615df84-738b-11e6-853d-093f80bf60be.png


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#15669 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AE7V4VaxO6cy5AwYfqza1PUj64imhfmnks5qnJNOgaJpZM4Jw4JW
.

@cvuosalo
Copy link
Contributor

cvuosalo commented Sep 5, 2016

In addition, there is a large shuffling of Puppi MET phi values, which seems odd, as well as significant changes in electron and muon Et, as shown below.
phi
elet
muet

@cvuosalo
Copy link
Contributor

cvuosalo commented Sep 5, 2016

@monttj: Your review of this PR and #15429 would be helpful.

@cvuosalo
Copy link
Contributor

cvuosalo commented Sep 5, 2016

@violatingcp: Please elaborate. Could you please list the problems seen in testing of #15562, of those, which are intended to be addressed by this PR?

@violatingcp
Copy link
Contributor Author

I have no idea what black is and it seems the events you are comparing to
are different than in the past, so its very difficult to make any
conclusions. What I do know is :

  1. The change in this code replaces the use of Puppi No Lepton in the MET
    calculation to puppi. The reason is that Puppi No Lepton breaks the
    assignment of PuppiPhoton weights in the MET calculation by adding back
    photons which already exist since the references appear broken
  2. MET is usually 0 so comparing MET phi changes has no meaning
  3. Puppi Jet Phi should have have changed at all, but I think you mean to
    say Puppi MET phi given the plots. The other fractions are consistent with
    what I would have expected.

On Tue, Sep 6, 2016 at 12:26 AM, Carl Vuosalo notifications@github.com
wrote:

@violatingcp https://github.com/violatingcp: Please elaborate. Could
you please list the problems seen in testing of #15562
#15562, of those, which are
intended to be addressed by this PR?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#15669 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AE7V4cKWMVoAom2CA_jo1qXga23p4__Xks5qnJcygaJpZM4Jw4JW
.

@slava77
Copy link
Contributor

slava77 commented Sep 5, 2016

@violatingcp
what about the increased tail in puppiMET?
(the plots are for ZEE)
In #15562 https://cloud.githubusercontent.com/assets/5736159/18070536/1c12bee4-6e14-11e6-888a-09dc10ecf44d.png shows a large increase in MET>100 GeV.
This PR does not change the MET distribution according to https://cloud.githubusercontent.com/assets/5736159/18257541/2e258284-738b-11e6-8443-ef15168f0a98.png

@violatingcp
Copy link
Contributor Author

Why are the events different and what is black in the second plot? The code
should now be exactly the same as what Maria is doing.

On Tue, Sep 6, 2016 at 12:50 AM, Slava Krutelyov notifications@github.com
wrote:

@violatingcp https://github.com/violatingcp
what about the increased tail in puppiMET?
(the plots are for ZEE)
In #15562 #15562 https://cloud.
githubusercontent.com/assets/5736159/18070536/1c12bee4-
6e14-11e6-888a-09dc10ecf44d.png shows a large increase in MET>100 GeV.
This PR does not change the MET distribution according to https://cloud.
githubusercontent.com/assets/5736159/18257541/2e258284-
738b-11e6-8443-ef15168f0a98.png


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#15669 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AE7V4S9vrQQ4rX5_wFIzy6HDNU-JeHRZks5qnJyigaJpZM4Jw4JW
.

…nd rather do a delta R matching to the candidates. This allows for use on Reco and and Puppi NoLepton collections without directly relying on the references to fix things. This is a result of studies which show that using the collection puppiMerged or the reco Puppi candidates breaks the use of referene keys to link things making Delta R the only option. The reco code is thus updated with what should be the BEST puppi MET version. However the validated version consists of commenting out the puppiMerged line
@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 8, 2016

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

@slava77
Copy link
Contributor

slava77 commented Sep 8, 2016

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 8, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/15041/console

@slava77
Copy link
Contributor

slava77 commented Sep 8, 2016

@cvuosalo if you follow up with the review, please make sure to check the timing on events with PU (the same ZEE sample should be OK).
Using deltaR can become pretty costly if not done minimally/carefully.

violatingcp added a commit to violatingcp/cmssw that referenced this pull request Sep 8, 2016
…nd rather do a delta R matching to the candidates. This allows for use on Reco and and Puppi NoLepton collections without directly relying on the references to fix things. This is a result of studies which show that using the collection puppiMerged or the reco Puppi candidates breaks the use of referene keys to link things making Delta R the only option. The reco code is thus updated with what should be the BEST puppi MET version. However the validated version consists of commenting out the puppiMerged line. This pull request follows the equivalent 81X verision cms-sw#15669
@mariadalfonso
Copy link
Contributor

@violatingcp
With the goal of keep in synch the miniAOD -> miniAOD and AOD->miniAOD, if the DR test is pass then

  1. activate the DR in the makePuppiesFromMiniAOD that is uncomment this lines
    https://github.com/violatingcp/cmssw/blob/0b8cf5069f232e9e93e2f40e68452df1d23e7219/PhysicsTools/PatAlgos/python/slimming/puppiForMET_cff.py#L44-L45

  2. switch the full AOD-miniAOD production to makePuppiesFromMiniAOD instead of makePuppies
    https://github.com/cms-sw/cmssw/blob/CMSSW_8_1_X/PhysicsTools/PatAlgos/python/slimming/miniAOD_tools.py#L275-L276

@slava77 do you agree ?

@slava77
Copy link
Contributor

slava77 commented Sep 8, 2016

On 9/8/16 8:20 AM, mariadalfonso wrote:

@violatingcp https://github.com/violatingcp
With the goal of keep in synch the miniAOD -> miniAOD and AOD->miniAOD,
if the DR test is pass then

  1. activate the DR in the makePuppiesFromMiniAOD that is uncomment this
    lines
    https://github.com/violatingcp/cmssw/blob/0b8cf5069f232e9e93e2f40e68452df1d23e7219/PhysicsTools/PatAlgos/python/slimming/puppiForMET_cff.py#L44-L45

  2. switch the full AOD-miniAOD production to makePuppiesFromMiniAOD
    instead of makePuppies
    https://github.com/cms-sw/cmssw/blob/CMSSW_8_1_X/PhysicsTools/PatAlgos/python/slimming/miniAOD_tools.py#L275-L276

@slava77 https://github.com/slava77 do you agree ?

Sounds good.

In interest of doing less harm, in case these two steps have other issues,
please do not update the signed "Descoped" 80X PR.
By default we go on with it in 80X.

I guess you can update #15429


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#15669 (comment), or
mute the thread
https://github.com/notifications/unsubscribe-auth/AEdcbl2c5wju9uLuMcXG5kOzekswwz5Nks5qoCfSgaJpZM4Jw4JW.

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 8, 2016

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 8, 2016

@mariadalfonso
Copy link
Contributor

@slava77 @cvuosalo let us know how your validation of this extra DR.
if ok then @violatingcp will do the changes discussed in #15669 (comment) in both #15669 and #15429

#15772 (descoped) will not be modified

@violatingcp
Copy link
Contributor Author

After discussion with @mariadalfonso we have decided #15669 contains all the fixes we would like. The proposal of two additional steps would require a larger re-engineering and consequently we stay with the current #15429 for the 80X release and #15669 for the 81X provided the checks come back with the expected good performance.

@slava77
Copy link
Contributor

slava77 commented Sep 9, 2016

@cvuosalo we should keep 81X in sync with all new features/bugfixes that were added to 80X.
So, this PR needs to go in pretty soon.

@cvuosalo
Copy link
Contributor

cvuosalo commented Sep 9, 2016

+1

For #15669 b92cdaa

Puppi photon fixes for #15562.

This PR is related to #15429, #15562, and #15772 .

The code changes match the corresponding changes in #15429, which is already merged. Jenkins tests against baseline CMSSW_8_1_X_2016-09-08-0900 show numerous tiny DQM plot changes, but most are not significant. The slightly larger changes are as expected, with two examples shown below. See #15429, which represents this PR plus #15562 for 80X, for more test results and plots.

From Jenkins workflow 25202.0_TTbar_13:

met
hfmetfrac

@davidlange6 davidlange6 merged commit b07e746 into cms-sw:CMSSW_8_1_X Sep 12, 2016
Sam-Harper pushed a commit to Sam-Harper/cmssw that referenced this pull request Nov 25, 2016
…nd rather do a delta R matching to the candidates. This allows for use on Reco and and Puppi NoLepton collections without directly relying on the references to fix things. This is a result of studies which show that using the collection puppiMerged or the reco Puppi candidates breaks the use of referene keys to link things making Delta R the only option. The reco code is thus updated with what should be the BEST puppi MET version. However the validated version consists of commenting out the puppiMerged line. This pull request follows the equivalent 81X verision cms-sw#15669
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