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

[10_6_X] Fix a discrepancy in Puppi weights when running on MiniAOD w/ useExistingWeights=False #28169

Merged
merged 1 commit into from
Nov 5, 2019

Conversation

hqucms
Copy link
Contributor

@hqucms hqucms commented Oct 14, 2019

PR description:

Backport of #28033.
This is a minimal fix without the code simplification in #28033.

The discrepancy happens only when remaking puppi from miniAOD in analysis setup or other non-standard workflows, with useExistingWeights=False, and is fixed in this PR.

Standard miniAOD or nanoAOD productions are not affected.

@cmsbuild cmsbuild added this to the CMSSW_10_6_X milestone Oct 14, 2019
@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 14, 2019

A new Pull Request was created by @hqucms (Huilin Qu) for CMSSW_10_6_X.

It involves the following packages:

CommonTools/PileupAlgos

@perrotta, @cmsbuild, @santocch, @slava77 can you please review it and eventually sign? Thanks.
@rappoccio, @ahinzmann, @riga, @jdolen, @gkasieczka, @clelange this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

@perrotta
Copy link
Contributor

backport of #28033

@perrotta
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 14, 2019

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/2926/console Started: 2019/10/14 18:44

@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-61b88c/2926/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 4 differences found in the comparisons
  • DQMHistoTests: Total files compared: 33
  • DQMHistoTests: Total histograms compared: 3212305
  • DQMHistoTests: Total failures: 3
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3211968
  • DQMHistoTests: Total skipped: 334
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 32 files compared)
  • Checked 137 log files, 14 edm output root files, 33 DQM output files

@slava77
Copy link
Contributor

slava77 commented Oct 16, 2019

@hqucms
related to #28033 (comment)
to simplify signoff of this backport,
please provide an overlay of the plots for the 3 tests done in that comment with and without this PR.
Thank you.

@slava77
Copy link
Contributor

slava77 commented Oct 16, 2019

+1

for #28169 acf7bb8

@fabiocos my comments in the ORP were based on the #28033 ; after some more careful look in this PR, I see that it should be OK for integration

@hqucms please edit the PR description to clarify that the standard miniAOD or nanoAOD production are not affected

@fabiocos
Copy link
Contributor

@slava77 thanks for the clarification, as I have noted in the spreadsheet this is not a real complete backport

@hqucms
Copy link
Contributor Author

hqucms commented Oct 16, 2019

@slava77 I have updated the PR description accordingly. Let me know if you still need the plots mentioned in #28169 (comment).

@slava77
Copy link
Contributor

slava77 commented Oct 16, 2019

@slava77 I have updated the PR description accordingly. Let me know if you still need the plots mentioned in #28169 (comment).

I think that the plots would still be helpful mostly to clarify the level of previous disagreement and the newly updated agreement between running from AOD and that from miniAOD.
The plots attached in #28033 (comment) are in separate files with dissimilar size format that makes incremental comparison rather hard.
Perhaps it's even better to update the info in the master PR as well.

@santocch
Copy link

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_10_6_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_11_0_X is complete. This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)

@fabiocos
Copy link
Contributor

fabiocos commented Nov 5, 2019

+1

1 similar comment
@fabiocos
Copy link
Contributor

fabiocos commented Nov 5, 2019

+1

@fabiocos
Copy link
Contributor

fabiocos commented Nov 5, 2019

@smuzaffar the bot looks stuck on this PR...

@cmsbuild cmsbuild merged commit bd99ef3 into cms-sw:CMSSW_10_6_X Nov 5, 2019
@smuzaffar
Copy link
Contributor

it was due to github issue https://www.githubstatus.com/incidents/42hkbtl63nmn

@fabiocos
Copy link
Contributor

fabiocos commented Nov 6, 2019

@smuzaffar ok, thanks for the clarification

@hqucms hqucms deleted the patch-1 branch November 15, 2019 19:56
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