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

Workaround for NanoAOD LHE weights in newer MadGraph #31680

Merged
merged 3 commits into from
Nov 9, 2020

Conversation

kdlong
Copy link
Contributor

@kdlong kdlong commented Oct 6, 2020

PR description:

Workaround for a new header format in MadGraph >= 2.6.5. Originally by @arizzi, now updating to master.

PR validation:

Confirmed that 8 scale weights are found for MadGraph 2.6.5 sample:/ZGToLLG_01J_5f_PDFWeights_TuneCP5_13TeV-amcatnloFXFX-pythia8/RunIIAutumn18MiniAOD-102X_upgrade2018_realistic_v15-v2/MINIAODSIM

The central weight is not found, which is ok since it is always 1. Further testing is in progress.

Fix a few places where missing_weightgroup wasn't set

Debug back off

Formatting
@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2020

The code-checks are being triggered in jenkins.

@kdlong kdlong changed the title Porting Andrea's MG26X fixes Workaround for NanoAOD LHE weights in newer MadGraph Oct 6, 2020
@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2020

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31680/18813

  • This PR adds an extra 24KB to repository

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2020

A new Pull Request was created by @kdlong (Kenneth Long) for master.

It involves the following packages:

PhysicsTools/NanoAOD

@gouskos, @cmsbuild, @fgolf, @mariadalfonso, @santocch, @peruzzim can you please review it and eventually sign? Thanks.
@gpetruc this is something you requested to watch as well.
@silviodonato, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@mariadalfonso
Copy link
Contributor

please test workflow 1325.6, 1325.7, 1325.8, 136.7952, 1329.1, 136.7722, 136.8521, 10826.0, 1325.61, 1325.81

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2020

The tests are being triggered in jenkins.
Test Parameters:

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2020

+1
Tested at: 45af73d
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-7327e7/9754/summary.html
CMSSW: CMSSW_11_2_X_2020-10-05-2300
SCRAM_ARCH: slc7_amd64_gcc820

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2020

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2020

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

@slava77 comparisons for the following workflows were not done due to missing matrix map:

  • /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/data/PR-7327e7/1325.61_TTbar_13_106Xv1NanoAODINPUT+TTbar_13_106Xv1NanoAODINPUT+NANOAODMC2017_106XMiniAODv1
  • /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/data/PR-7327e7/1325.81_TTbar_13_106Xv1NanoAODINPUT+TTbar_13_106Xv1NanoAODINPUT+NANOEDMMC2017_106XMiniAODv1+HARVESTNANOAODMC2017_106XMiniAODv1

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 4 differences found in the comparisons
  • DQMHistoTests: Total files compared: 35
  • DQMHistoTests: Total histograms compared: 2542225
  • DQMHistoTests: Total failures: 7
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2542196
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 34 files compared)
  • Checked 149 log files, 22 edm output root files, 35 DQM output files

@mariadalfonso
Copy link
Contributor

mariadalfonso commented Oct 7, 2020

@kdlong
can you please add the DQM for LHEScaleweight ?

@mariadalfonso mariadalfonso mentioned this pull request Oct 7, 2020
@mariadalfonso
Copy link
Contributor

@kdlong
Any news on this fix ?

afaik, we have on the pipeline the DQM file fix and the suggestion from @dteague

@agrohsje
Copy link

agrohsje commented Oct 27, 2020

Hi @kdlong. Just a small comment. The blocks are currently scalewmg26x and scalewmg26xNew. Should we worry about more meaningful names or is it anyway unimportant once we have the restructured weights. Maybe we could at least add some info on what this is supposed to catch, or?

@silviodonato
Copy link
Contributor

@cms-sw/xpog-l2 @cms-sw/generators-l2 @cms-sw/analysis-l2 do you have any comments?

@agrohsje
Copy link

agrohsje commented Nov 2, 2020

Hi @silviodonato . My main concern is that, it becomes kind of hard to understand what each specific part is handling. It would be good to add a line for documentation to the code. Also, it is not clear to me if Dylan tested a file that has this problem or if this is just the code from Andrea. Sorry if I missed the info.

@kdlong
Copy link
Contributor Author

kdlong commented Nov 2, 2020

@agrohsje the code is unquestionably a disaster and a nightmare to maintain. As you know it requires a major rewrite, which is a bit outside the scope. I agree that the names are silly, POWHEG even seems to fall into the mg26XNew format, but I didn't want to deal with trying to improve on this.

It might be a good idea to do a little bit more testing if people are available and if there is any time before the v8 production starts. In particular I wonder if MadGraph Reweighting is still properly parsed in 2.6.5.

@agrohsje
Copy link

agrohsje commented Nov 2, 2020

Hi @kdlong . I fully agree the code is a nightmare to maintain but maybe we could still add a line with this is the problem, see e.g. this file. Moreover, as you say, it would be useful to test that it works well with a recent LO/NLO (madspin+ME reweighting) sample from 2.6.1 and 2.6.5. and there are no other outstanding issues.

@mariadalfonso
Copy link
Contributor

Hi @kdlong . I fully agree the code is a nightmare to maintain but maybe we could still add a line with this is the problem, see e.g. this file. Moreover, as you say, it would be useful to test that it works well with a recent LO/NLO (madspin+ME reweighting) sample from 2.6.1 and 2.6.5. and there are no other outstanding issues.

@kdlong can you confirm that you are taking care of this request?

Regarding the request to add comments in the code to specify with part of the code handle which exceptions, I suggest to do on a separate note, together with the request to remove the std::cout #31939 (comment)

@agrohsje
Copy link

agrohsje commented Nov 9, 2020

I discussed a little more with @kdlong on Friday. The landscape is very rich. It is hard to make sure all problems are covered with the PR. I will approve for now, but for v9 we should definitely prepare a wider validation campaign. We need to collect samples with problems from MC contacts. We don't have such a list on GEN side or so.

@agrohsje
Copy link

agrohsje commented Nov 9, 2020

+1

@mariadalfonso
Copy link
Contributor

+xpog

testing shows no difference as expected for the MC that are not interested by this fix

@silviodonato
Copy link
Contributor

merge

@santocch
Copy link

+1

@cmsbuild
Copy link
Contributor

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 be automatically merged.

cmsbuild added a commit that referenced this pull request Nov 13, 2020
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.

6 participants