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
updating DECAY and evt files from evtgen 2.0 #16
Conversation
A new Pull Request was created by @alberto-sanchez (Alberto Sanchez Hernandez) for branch master. @SiewYan, @smuzaffar, @mkirsano, @mrodozov, @cmsbuild, @GurpreetSinghChahal, @agrohsje, @alberto-sanchez can you please review it and eventually sign? Thanks. |
test parameters:
|
please test |
+externals |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-136259/13904/summary.html The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
You can see more details here: CMS Clang-Tidy warnings: There are 20 Clang-Tidy warnings. See https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-136259/13904/llvm-analysis/cmsclangtidy.txt for details. Comparison Summary@slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
|
+generators |
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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
@alberto-sanchez i cannot find the comment anymore so let me calrify: will you make a back-port to 10_6? if so, should 2020 files be a requirement for ul requests? |
@agrohsje, it is not planned. The DECAY and evt files can be used transparently between 2.0 and 1.6, howver the usage of 2.0 was not planned upto Run3. At least that was the consensus during my presentation in BPH last December. |
Moving files from cmssw
cms-sw/cmssw#33313