Skip to content

Regenerate code for 849#939

Merged
valassi merged 461 commits intomadgraph5:less_patchfrom
valassi:patchMadsh
Jul 29, 2024
Merged

Regenerate code for 849#939
valassi merged 461 commits intomadgraph5:less_patchfrom
valassi:patchMadsh

Conversation

@valassi
Copy link
Member

@valassi valassi commented Jul 24, 2024

Hi @oliviermattelaer this is just regenerating code for your #849.
Ok for me (as long as you want 849 - I trust you on that)
Can you please review? Thanks
Andrea

valassi and others added 30 commits June 27, 2024 16:54
…of known issues (e.g. remove rotxxx crashes): enable bypasses, tests should succeed
…ng of tmad known issues, the CI will fail, signaling these issues are pending
Fix SIGFPE crash (855) in rotxxx by adding volatile in aloha_functions.f
…p and gpucpp_826, to allow cherry-picking Olivier's fix_826 changes

(later on, will include Olivier's gpucpp_826 change into gpucpp directly)

Revert "[tmad] update mg5amcnlo to f274cab55, adding volatile to prevent madgraph5#855 crashes in rotxxx (move this upstream as suggested by Olivier)"
This reverts commit 720ae02.

Revert "[valgrind] upgrade MG5AMC to include the merge of PR madgraph5#110 and PR madgraph5#112 into the gpucpp branch"
This reverts commit 7d3dc34.

Revert "[valgrind] upgrade MG5AMC to include the workaround for uninitialised values mg5amcnlo/mg5amcnlo#111"
This reverts commit f355965.

Revert "[valgrind] upgrade MG5AMC to include the fix for memory leak mg5amcnlo/mg5amcnlo#109"
This reverts commit 7bb4142.
… now including Olivier's extra commit previously in gpucpp_826

This should complete the merge in madgraph4gpu master of the gpucpp_826 and gpucpp branches of MG5AMC.
It should now be possible to remove the gpucpp_826 branch from MG5AMC.
…y branch (WIP PR madgraph5#853) to allow cherry-picking the next commit

git checkout 335d6d2 susy_gg_t1t1.mad/CODEGEN_mad_susy_gg_t1t1_log.txt
…rt (just check that the merge so far was ok)
Revert "[color] temporarely regenerate susy_gg_t1t1.mad, no change, will revert (just check that the merge so far was ok)"
This reverts commit dbfb3bc.
…rangely, clang formatting was not complaining?)
… comma is allowed in the std::map initializer list
Note: cuda compilation 'make -j BACKEND=cuda' fails with
  coloramps.h(14): error: dynamic initialization is not supported for a __device__ variable
…p as constexpr, this fails with a different error

ccache /usr/local/cuda-12.0/bin/nvcc  -I. -I../../src  -Xcompiler -O3 -gencode arch=compute_70,code=compute_70 -gencode arch=compute_70,code=sm_70 -lineinfo -use_fast_math -I/usr/local/cuda-12.0/include/ -DUSE_NVTX  -std=c++17  -ccbin /usr/lib64/ccache/g++ -DMGONGPU_FPTYPE_DOUBLE -DMGONGPU_FPTYPE2_DOUBLE -Xcompiler -fPIC -c -x cu CPPProcess.cc -o CPPProcess_cuda.o
coloramps.h(14): error: expression must have a constant value
coloramps.h(14): note #2703-D: cannot call non-constexpr function "std::map<_Key, _Tp, _Compare, _Alloc>::map(std::initializer_list<std::map<_Key, _Tp, _Compare, _Alloc>::value_type>, const _Compare &, const std::map<_Key, _Tp, _Compare, _Alloc>::allocator_type &) [with _Key=int, _Tp=int, _Compare=std::less<int>, _Alloc=std::allocator<std::pair<const int, int>>]"
/usr/include/c++/11/bits/stl_map.h(228): here
coloramps.h(14): error: a constexpr variable must have a literal type or a reference type
CPPProcess.cc(1012): error: no operator "[]" matches these operands
            operand types are: const std::map<int, int, std::less<int>, std::allocator<std::pair<const int, int>>> [ const unsigned int ]
3 errors detected in the compilation of "CPPProcess.cc".
…making the map constexpr

Revert "[susy] in susy_gg_t1t1.mad, try to fix coloramps.h by defining the map as constexpr, this fails with a different error"
This reverts commit 38b3afd.
…ncludes clang format fixes)

This code now compiles... but it does not seem to fix the empty cross section problem
…graph5#826 is NOT fixed) after Olivier's first two commits in PR madgraph5#852

./tmad/teeMadX.sh -susyggt1t1 +10x -makeclean

(PS: it is NOW quite obvious to me that PR madgraph5#852 should be tested against different issues like ggttgg madgraph5#856, NOT against susy madgraph5#826)
(PS: will now therefore slowly move to different tests - first, however, recover my coloramps.h proposal in susy and Olivier's later changes)
…n and tmad logs

Revert "[color] temporarely regenerate susy_gg_t1t1 again, just to check all is ok - will revert"
This reverts commit 28a0177.

Revert "[color] rerun tmad test for susy_gg_t1t1: still no cross section (madgraph5#826 is NOT fixed) after Olivier's first two commits in PR madgraph5#852"
This reverts commit 6baf004.
… to allow merging his next commits

git checkout 1585a75 CODEGEN/PLUGIN/
valassi and others added 16 commits July 16, 2024 14:10
…aster with OMP madgraph5#900 and submod madgraph5#897) into gtest

Fix conflicts in epochX/cudacpp/gg_tt.mad/CODEGEN_mad_gg_tt_log.txt
  git checkout clang gg_tt.mad/CODEGEN_mad_gg_tt_log.txt

Note: MG5AMC has been updated including mg5amcnlo#107
…s from the latest upstream/master for easier merging

git checkout upstream/master $(git ls-tree --name-only HEAD */CODEGEN*txt)
Fix clang16 and clang17 builds
…aster with clang madgraph5#905, OMP madgraph5#900 and submod madgraph5#897) into gtest

Fix conflicts in epochX/cudacpp/gg_tt.mad/CODEGEN_mad_gg_tt_log.txt
  git checkout clang gg_tt.mad/CODEGEN_mad_gg_tt_log.txt

Note: MG5AMC has been updated including mg5amcnlo#107
…ogs from the latest upstream/master for easier merging

git checkout upstream/master $(git ls-tree --name-only HEAD */CODEGEN*txt)
Fix segfault from constexpr_math.h and adapt testmisc.cc to higher tolerances when running through valgrind
Fix runTest segfault (remove cudaDeviceReset) and simplify googletest template usage
…' by 'ECHO' alias to leave a blank line (workaround for github issue)
…adgraph5#927

Revert "[actions] in .github/workflows, TEMPORARELY reduce CI tests to only one gg_tt "new ci" test while debugging madgraph5#937"
This reverts commit 5b71191.
Fix issues in the new CI (tput_test was not executed)
… into patchMadsh (current upstream/master)

Fix conflicts in MG5aMC/mg5amcnlo (use upstream/master version)
…Olivier's patch in PR madgraph5#849

No c++/frtran code changes: only the two gen_ximprove.py and madevent_interface.py are modified in .mad directories
@valassi valassi requested a review from oliviermattelaer July 24, 2024 15:01
@valassi valassi self-assigned this Jul 24, 2024
Copy link
Member

@oliviermattelaer oliviermattelaer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is good to go for me.

Thanks,

Olivier

@valassi valassi changed the base branch from master to less_patch July 29, 2024 15:19
@valassi
Copy link
Member Author

valassi commented Jul 29, 2024

Yes, this is good to go for me.

Thanks,

Olivier

Thanks Olivier :-)

I had forgotten that 849 has conflicts, fixed here. So I changed this to be merged into less_patch for 849, then I will merge 849 into master.

Merging now.

@valassi valassi merged commit 6e4357d into madgraph5:less_patch Jul 29, 2024
valassi added a commit to valassi/madgraph4gpu that referenced this pull request Jul 29, 2024
valassi added a commit to valassi/madgraph4gpu that referenced this pull request Jul 29, 2024
valassi added a commit to valassi/madgraph4gpu that referenced this pull request Jul 29, 2024
…rder madgraph5#918, and smaller patch madgraph5#939 and madgraph5#849) into susy2

Note: there is no change with respect to the previous origin/susy2 after this merge (no need to rerun the CI)
valassi added a commit to valassi/madgraph4gpu that referenced this pull request Jul 29, 2024
@valassi valassi linked an issue Jul 30, 2024 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove gen_ximprove.py and madevent_interface.py from patch.common?

2 participants