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
upgrade to lhapdf 6.2.1 #3415
upgrade to lhapdf 6.2.1 #3415
Conversation
A new Pull Request was created by @mkirsano (Mikhail Kirsanov) for branch IB/CMSSW_9_4_X/gcc630. @cmsbuild, @smuzaffar, @mrodozov can you please review it and eventually sign? Thanks. |
@cmsbuild please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+external |
Just to clarify: the backport of this PR in particular to 92x (#3419) and 71x (#3417) and corresponding new releases are very urgent because we need the new PDF to start producing gridpacks [*]. The gridpacks production is a pre-condition for the GEN-SIM campaign, it would be good not to wait for 930 to be out. [*] We use 92x (gcc53x) for POWHEG and 71x (gcc48x) for Madgraph gridpacks, they can be then used on all the CMSSW versions |
hi Luca
It doesn't make sense to do anything in 92x for gen going forward. we'll already have to support 93x for the same reason, so we should converge to that cycle (and a back port will show up in 930 before 92x regardless...) 71x was noted at the release meeting.
… On Sep 15, 2017, at 4:33 PM, perrozzi ***@***.***> wrote:
Just to clarify: the backport of this PR in particular to 92x (#3419) and 71x (#3417) and corresponding new releases are very urgent because we need the new PDF to start producing gridpacks [*]. The gridpacks production is a pre-condition for the GEN-SIM campaign, it would be good not to wait for 930 to be out.
[*] We use 92x (gcc53x) for POWHEG and 71x (gcc48x) for Madgraph gridpacks, they can be then used on all the CMSSW versions
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Yes I agree, but for the moment we have validated POWHEG using gcc530. We were not aware of the switch to gcc630 for MC v2 production. |
It sounds like POWHEG workflows need to become part of the routine CMS validation... then we'd all be aware of its status on gcc630 or other compilers that CMS may wish to move towards.
Lets find out if POWHEG+gcc630 works or not and worry next week if it doesn't.
… On Sep 15, 2017, at 4:56 PM, perrozzi ***@***.***> wrote:
Yes I agree, but for the moment we have validated POWHEG using gcc530. We were not aware of the switch to gcc630 for MC v2 production.
We can try to validate it asap in 93x/gcc630, hoping that there are no hiccups. I assume that it would be ok.
Anticipating possible problems, what shall we do in case gcc630 doesn't work?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I am collecting the issues here |
No description provided.