Relval samples for Sherpa+Blackhat and Sherpa+OpenLoops

[thuer]

Added two RelVal steps for Sherpa with external loop generators
I put them to relval_generator.py, should I change them to extendgen?

I just took the next two free numbers in the generator file, is there any logic in assigning the numbers?

Has to go in after #9272 (Event production is currently broken with Sherpa)

[cmsbuild]

A new Pull Request was created by @thuer (Sebastian Thüer) for CMSSW_7_5_X.

Relval samples for Sherpa+Blackhat and Sherpa+OpenLoops

It involves the following packages:

Configuration/Generator
Configuration/PyReleaseValidation

@vciulli, @covarell, @boudoul, @franzoni, @thuer, @cmsbuild, @srimanob, @nclopezo, @bendavid can you please review it and eventually sign? Thanks.
@ghellwig, @Martin-Grunewald this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.
@nclopezo you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

[cmsbuild]

+1
Tested at: 9869735
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9274/2499/summary.html

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
9869735
You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9274/2499/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9274/2499/git-merge-result

[cmsbuild]

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

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_5_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar

[davidlange6]

are these tests actually confirmed to be working? I see

Matrix_Element_Handler::BuildProcesses(): Looking for processes ......................Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_1tL.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_1tL.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_1L.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_1L.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_1ptL.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_1ptL.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_0L.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_0L.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_l.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_l.so'.

::operator:("Initialising OpenLoops Virtual for (d,db,e-,e+): ppll_eexddx_1_")
..Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_1tL.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_1tL.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_1L.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_1L.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_1ptL.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_1ptL.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_0L.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_0L.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_l.so'.
Library_Loader::LoadLibrary(): Failed to load library 'libopenloops_ppll_l.so'.

[thuer]

This is the default output which you get when using Sherpa interfaced with OpenLoops.
When we asked the openloops authors about them we got this reply
"This is nothing to worry about. The OpenLoops libraries can have different names depending on what exactly they contain. Sherpa just tries all possibilities until it finds a suitable library. The warnings will disappear in a future Sherpa version. "

[davidlange6]

+1

ok thanks - but yuck…

On Jun 16, 2015, at 10:34 AM, Sebastian Thüer notifications@github.com wrote:

This is the default output which you get when using Sherpa interfaced with OpenLoops.
When we asked the openloops authors about them we got this reply
"This is nothing to worry about. The OpenLoops libraries can have different names depending on what exactly they contain. Sherpa just tries all possibilities until it finds a suitable library. The warnings will disappear in a future Sherpa version. "

—
Reply to this email directly or view it on GitHub.