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

Workflow 511.1: herwig7+ MG5+Openloops pptoee at NLO QCD #24813

Merged
merged 1 commit into from
Oct 9, 2018

Conversation

Andrej-CMS
Copy link
Contributor

New workflow for testing Openloops with Herwig7

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 5, 2018

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 5, 2018

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 5, 2018

A new Pull Request was created by @Andrej-CMS for master.

It involves the following packages:

Configuration/Generator
Configuration/PyReleaseValidation

@cmsbuild, @efeyazgan, @zhenhu, @perrozzi, @prebello, @kpedro88, @pgunnell, @alberto-sanchez, @qliphy can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @felicepantaleo, @makortel 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

@alberto-sanchez
Copy link
Member

please test workflow 511.1

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 5, 2018

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/30904/console Started: 2018/10/05 18:31

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 5, 2018

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 5, 2018

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 5, 2018

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

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

  • /build/cmsbld/jenkins/workspace/compare-root-files-short-matrix/results/JR-comparison/PR-24813/511.1_PPtoee-M60-120_13TeV_madgraph_openloops_herwig7+PPtoee-M60-120_13TeV_madgraph_openloops_herwig7+HARVESTGEN

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 32
  • DQMHistoTests: Total histograms compared: 3162979
  • DQMHistoTests: Total failures: 1
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3162781
  • DQMHistoTests: Total skipped: 197
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 31 files compared)
  • Checked 134 log files, 14 edm output root files, 32 DQM output files

@zhenhu
Copy link
Contributor

zhenhu commented Oct 5, 2018

+1

@alberto-sanchez
Copy link
Member

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 8, 2018

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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)

@fabiocos
Copy link
Contributor

fabiocos commented Oct 9, 2018

+1

@cmsbuild cmsbuild merged commit be33f4f into cms-sw:master Oct 9, 2018
@fabiocos
Copy link
Contributor

@alberto-sanchez @smuzaffar I notice that this test quite often goes in TimeOut because the LHE calculation is quite heavy (I guess). Although it could be useful to have defined fragments, do you think it is fundamental to probe regularly this code at every IB?

@cmsbuild cmsbuild modified the milestones: CMSSW_10_3_X, CMSSW_10_4_X Oct 11, 2018
@alberto-sanchez
Copy link
Member

Not really. I think we really would to have it when the involved libraries or relevant code is updated.
Like in this case openloops was modified. We will have a discussion about this and other possible FW in the following GEN meetings.

@fabiocos
Copy link
Contributor

@alberto-sanchez yes please, unless @smuzaffar has some bright idea I do not think it makes sense to have a test that most of the times fails with a TimeOut problem. This looks more suitable for standalone checks

@smuzaffar
Copy link
Contributor

@fabiocos , we have a way to customize the timeout per release per workflow. So if no objections I can see timeout for workflow 511.1 to be 3 hours?

@davidlange6
Copy link
Contributor

davidlange6 commented Oct 16, 2018 via email

@smuzaffar
Copy link
Contributor

almost all the time is taken by the initialization (before first event) in step1. If we can improve this time then we are fine. Rest of the job just took less than a minute for 10 events.

[a]
Started: Tue Oct 16 08:08:34 2018
Finished: Tue Oct 16 09:57:24 2018

[b] Step1 log
%MSG-i ThreadStreamSetup: (NoModuleName) 16-Oct-2018 08:08:59 CEST pre-events
...
....
Begin processing the 1st record. Run 1, Event 1, LumiSection 1 on stream 2 at 16-Oct-2018 09:56:55.891 CEST

@fabiocos
Copy link
Contributor

@smuzaffar @davidlange6 it is the openloops calculation at the beginning that takes all the time. If people wants to test it, I do not know whether there is something simpler that might be tried, @Andrej-CMS could you please comment? Otherwise a 3 hours timeout would do the job for what i could see in my check

@davidlange6
Copy link
Contributor

davidlange6 commented Oct 16, 2018 via email

@Andrej-CMS
Copy link
Contributor Author

@fabiocos

the time is taken by the integration of phase space by mg5+openloops. The card has pp->ee +1j. I'm not aware of any easier/faster process at NLO QCD.

@davidlange6
Copy link
Contributor

davidlange6 commented Oct 18, 2018 via email

@davidlange6
Copy link
Contributor

davidlange6 commented Oct 18, 2018 via email

@davidlange6
Copy link
Contributor

davidlange6 commented Nov 3, 2018 via email

@prebello
Copy link
Contributor

prebello commented Nov 3, 2018

@efeyazgan @qliphy
could you please help to clarify @davidlange6 's question?

@qliphy
Copy link
Contributor

qliphy commented Nov 3, 2018

@davidlange6 @prebello I am not sure I understand the question. But if you want to check the DQM plots, you may do as following:

CMSSW_10_3_0
runTheMatrix -l 511.1
and after finishing the run, do
cmsRun step3_HARVESTING.py
then you can find all the plots inside the DQM*root file.

@davidlange6
Copy link
Contributor

davidlange6 commented Nov 3, 2018 via email

@qliphy
Copy link
Contributor

qliphy commented Nov 3, 2018

@davidlange6 Yes, from above procedure, I find plots like these ones:

ptlep1
dilepmass

@smuzaffar smuzaffar modified the milestones: CMSSW_10_4_X, CMSSW_10_3_X Nov 26, 2018
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

10 participants