Fix bug in GPUFOHelasCallWriter format_coupling#822
Fix bug in GPUFOHelasCallWriter format_coupling#822valassi merged 4 commits intomadgraph5:masterfrom
Conversation
…elasCallWriter format_coupling that results in wrong params2order for susy_gg_t1t1
…riter bug madgraph5#821 - no change in the code (this probably affects BSM only?)
git checkout HEAD~ $(git ls-tree --name-only HEAD */CODEGEN*)
|
Yes this is perfect. The only thing that one might consider if is the line |
oliviermattelaer
left a comment
There was a problem hiding this comment.
see above.
I let you decide, in any case this is good to go!
…#821 as suggested by Olivier
Thanks Olivier! Interesting, I had not thought of "is"... But yes, let;s keep the more verbose and more clear version.
Yes I have done this. |
Ok I will merge this when the CI is done, just to get one out of the way. I will then update the other PRs. |
…fixing madgraph5#821) into susy
…fixing madgraph5#821) into susy2
…raph5#822 and madgraph5#985) into goodhel Fix conflicts: - MG5aMC/mg5amcnlo (keep current version) - epochX/cudacpp/CODEGEN/PLUGIN/CUDACPP_SA_OUTPUT/MG5aMC_patches/PROD/patch.P1 (use upstream/master, will rebuild anyway) - epochX/cudacpp/gg_tt.mad/SubProcesses/P1_gg_ttx/auto_dsig1.f (keep goodhel comment style) - epochX/cudacpp/gg_tt.mad/SubProcesses/P1_gg_ttx/matrix1.f (keep goodhel comment style) - epochX/cudacpp/gg_tt.mad/bin/internal/file_writers.py (keep goodhel version)
Hi @oliviermattelaer this is the PR closing #821
(This is also part of the fix for #820 and I will include it in PR #825 I think)
Can you please review?
Thanks
Andrea