-
Notifications
You must be signed in to change notification settings - Fork 33
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
Fixes for iconfig-channel mappings in coloramps.h (obsolete, will be closed) #873
Conversation
…d for push/manual, disabled for PRs) Note: the FPE crashes in madgraph5#783 are not shown here because they need FPTYPE=f builds. I will add those in a more complex workflow with one codegen job and several build/test jobs.
…t into two separate jobs, and add a codegen cache (which is really a compulsory build artifact)
…eat the build/test jobs twice (for FPTYPE=d,f) This must be cleaned up - the cache cleanup job must be split up (codegen cache cleanup once, build cache cleanup once per build type) - the Process+fptype tag must become a more general build tag for caches (eventually add inl, hrdcod)
…also affected by madgraph5#696 [avalassi@itscrd80 gcc11.2/cvmfs] /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/nobm_gg_tt.sa/SubProcesses/P1_Sigma_loop_sm_no_b_mass_gg_ttx> make HRDCOD=1 OMPFLAGS=-fopenmp AVX=512y FPTYPE=d HELINL=0 HRDCOD=1 RNDGEN=hasCurand Building in BUILDDIR=. for tag=512y_d_inl0_hrd1_hasCurand (USEBUILDDIR is not set) make -C ../../src -f cudacpp_src.mk make[1]: Entering directory '/data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/nobm_gg_tt.sa/src' AVX=512y ccache /cvmfs/sft.cern.ch/lcg/releases/gcc/11.2.0-ad950/x86_64-centos8/bin/g++ -O3 -std=c++17 -I. -fPIC -Wall -Wshadow -Wextra -ffast-math -fopenmp -march=skylake-avx512 -mprefer-vector-width=256 -DMGONGPU_FPTYPE_DOUBLE -DMGONGPU_FPTYPE2_DOUBLE -DMGONGPU_HARDCODE_PARAM -c Parameters_loop_sm_no_b_mass.cc -o Parameters_loop_sm_no_b_mass.o In file included from Parameters_loop_sm_no_b_mass.cc:15: Parameters_loop_sm_no_b_mass.h: In function ‘const Parameters_loop_sm_no_b_mass_dependentCouplings::DependentCouplings_sv Parameters_loop_sm_no_b_mass_dependentCouplings::computeDependentCouplings_fromG(const fptype_sv&)’: Parameters_loop_sm_no_b_mass.h:291:46: error: ‘COND’ was not declared in this scope 291 | const fptype_sv mdl_GWcft_UV_t_1EPS_ = COND( mdl_MT, 0., -( ( mdl_G__exp__2 ) / ( 2. * 48. * ( ( M_PI ) * ( M_PI ) ) ) ) * 4. * mdl_TF ); | ^~~~ Parameters_loop_sm_no_b_mass.h:300:138: error: ‘reglog’ was not declared in this scope 300 | const fptype_sv mdl_G_UVt_FIN_ = COND( mdl_MT, 0., -( ( mdl_G__exp__2 ) / ( 2. * 48. * ( ( M_PI ) * ( M_PI ) ) ) ) * 4. * mdl_TF * reglog( mdl_MT__exp__2 / mdl_MU_R__exp__2 ) ); | ^~~~~~ make[1]: *** [cudacpp_src.mk:241: Parameters_loop_sm_no_b_mass.o] Error 1 make[1]: Leaving directory '/data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/nobm_gg_tt.sa/src' make: *** [makefile:520: ../../lib/libmg5amc_common.so] Error 2
… ttW and ttZ production
… list of physics processes (test madgraph5#783?)
…xt (for debugging madgraph5#701) cp dump_SIGMA_SM_NO_B_MASS_GD_TTXWMU_CPU_MadgraphTest.CompareMomentaAndME_0.txt ../../../CODEGEN/PLUGIN/CUDACPP_SA_OUTPUT/test/ref/dump_CPUTest.Sigma_sm_no_b_mass_gd_ttxwmu.txt This is necessary because runTest was failing otherwise pushd nobm_pp_ttW.mad/SubProcesses/P1_gd_ttxwmu make cleanall; HRDCOD=1 make -j ./runTest.exe Before this succeeds however, it is necessary to rebuild
…p_ttW: results have changed and seem more correct... INFO: The application is built for skylake-avx512 (AVX512VL) and the host supports it [ FAILED ] SIGMA_SM_NO_B_MASS_GD_TTXWMU_CPU/MadgraphTest.CompareMomentaAndME/0, where GetParam() = 0x7ac410 (10 ms) [----------] 1 test from SIGMA_SM_NO_B_MASS_GD_TTXWMU_CPU/MadgraphTest (10 ms total) [----------] 1 test from SIGMA_SM_NO_B_MASS_GD_TTXWMU_GPU/MadgraphTest [ RUN ] SIGMA_SM_NO_B_MASS_GD_TTXWMU_GPU/MadgraphTest.CompareMomentaAndME/0 INFO: Opening reference file ../../test/ref/dump_CPUTest.Sigma_sm_no_b_mass_gd_ttxwmu.txt MadgraphTest.h:299: Failure The difference between testDriver->getMatrixElement( ievt ) and referenceData[iiter].MEs[ievt] is 1.4553189634594381e-10, which exceeds toleranceMEs * referenceData[iiter].MEs[ievt], where testDriver->getMatrixElement( ievt ) evaluates to 1.4553189634594381e-10, referenceData[iiter].MEs[ievt] evaluates to 0, and toleranceMEs * referenceData[iiter].MEs[ievt] evaluates to 0. Google Test trace: MadgraphTest.h:278: In comparing event 0 from iteration 0 0 7.500000000000000e+02 0.000000000000000e+00 0.000000000000000e+00 7.500000000000000e+02 ref0 7.500000000000000e+02 0.000000000000000e+00 0.000000000000000e+00 7.500000000000000e+02 1 7.500000000000000e+02 0.000000000000000e+00 0.000000000000000e+00 -7.500000000000000e+02 ref1 7.500000000000000e+02 0.000000000000000e+00 0.000000000000000e+00 -7.500000000000000e+02 2 2.045233209356228e+02 6.877986897204741e+01 -1.905381248013139e+02 2.818406336784427e+01 ref2 2.045233209356227e+02 6.877986897204741e+01 -1.905381248013139e+02 2.818406336784428e+01 3 5.474933604313479e+02 -4.596225360107567e+02 3.030720946352406e+01 2.959350894402092e+02 ref3 5.474933604313477e+02 -4.596225360107564e+02 3.030720946352398e+01 2.959350894402091e+02 4 5.014688717565998e+02 4.188441856206845e+02 2.572754903817052e+02 -9.924666020293013e+01 ref4 5.014688717565996e+02 4.188441856206844e+02 2.572754903817050e+02 -9.924666020293004e+01 5 2.465144468764298e+02 -2.800151858197540e+01 -9.704457504391526e+01 -2.248724926051235e+02 ref5 2.465144468764297e+02 -2.800151858197538e+01 -9.704457504391526e+01 -2.248724926051234e+02 ME 1.455318963459438e-10 r.ME 0.000000000000000e+00 [ FAILED ] SIGMA_SM_NO_B_MASS_GD_TTXWMU_GPU/MadgraphTest.CompareMomentaAndME/0, where GetParam() = 0x7c5f20 (37 ms) [----------] 1 test from SIGMA_SM_NO_B_MASS_GD_TTXWMU_GPU/MadgraphTest (37 ms total)
CUDACPP_RUNTEST_DUMPEVENTS=1 ./runTest.exe ; mv dump_CPUTest* ../../../CODEGEN/PLUGIN/CUDACPP_SA_OUTPUT/test/ref/
…h, add some debug printouts about comparison of generated code
….yml, disable on:push triggers to avoid launching two jobs instead of one
…h, fix a bash bug and disable comparisons to the existing repo
…bleFPE (which already exists in testsuite_oneprocess)
…false (e.g. do not stop double jobs if float has failed)
Fix conflicts: .github/workflows/testsuite_allprocesses.yml .github/workflows/testsuite_oneprocess.yml epochX/cudacpp/CODEGEN/generateAndCompare.sh
… Node 16 to Node 20
…t channelId for susy_gg_t1t1 (fix issue madgraph5#826)
…ot channelId (and note that iconfig=1 is ok)
…g_t1t1 (will give zero cross section madgraph5#826)
… test a different iconfig In particular: the following triggers a SIGFPE reported in madgraph5#855 (crash in rotxxx that can be fixed adding volatile?) ./tmad/madX.sh -ggttgg -iconfig 104 -makeclean This also triggers a similar SIGFPE (initially reported in madgraph5#826) ./tmad/madX.sh -susyggt1t1 -iconfig 2 -makeclean
…SIGFPE madgraph5#855, and add volatile in aloha_functions.f to try to fix it The SIGFPE crash madgraph5#855 does seem to disappear in ./tmad/madX.sh -ggttgg -iconfig 104 -makeclean However, there is now a DIFFERENT issue, an lhe file mismatch between fortran and cpp (madgraph5#856) This is probably due to the iconfig/channel mapping issue reported by Olivier in madgraph5#852
…ebug SIGFPE madgraph5#855, and add volatile in aloha_functions.f to try to fix it The SIGFPE crash madgraph5#855 does seem to disappear in ./tmad/madX.sh -susyggt1t1 -iconfig 2 -makeclean Then no cross section is printed also for this iconfig (same as madgraph5#826 for iconfig 1), but this is a DIFFERENT issue
…: note that SIGFPE madgraph5#855 is still fixed because volatile has been added
…adgraph5#855 and prepare codegen backport
…dgraph5#855 in rotxxx The issue was observed and fixed in gg_ttgg (iconfig 104) and susy_gg_t1t1 (iconfig 2), the backport as usual is from gg_tt Note that aloha_functions.f is now added to the list of files to include when preparing patch.common ./CODEGEN/generateAndCompare.sh gg_tt --mad --nopatch git diff --no-ext-diff -R gg_tt.mad/Source/makefile gg_tt.mad/Source/dsample.f gg_tt.mad/Source/DHELAS/aloha_functions.f gg_tt.mad/Source/genps.inc gg_tt.mad/SubProcesses/makefile > CODEGEN/PLUGIN/CUDACPP_SA_OUTPUT/MG5aMC_patches/PROD/patch.common git diff --no-ext-diff -R gg_tt.mad/bin/internal/banner.py gg_tt.mad/bin/internal/gen_ximprove.py gg_tt.mad/bin/internal/madevent_interface.py >> CODEGEN/PLUGIN/CUDACPP_SA_OUTPUT/MG5aMC_patches/PROD/patch.common git diff --no-ext-diff -R gg_tt.mad/SubProcesses/P1_gg_ttx/auto_dsig1.f gg_tt.mad/SubProcesses/P1_gg_ttx/driver.f gg_tt.mad/SubProcesses/P1_gg_ttx/matrix1.f > CODEGEN/PLUGIN/CUDACPP_SA_OUTPUT/MG5aMC_patches/PROD/patch.P1 git checkout gg_tt.mad
…syggt1t1 to test madgraph5#855 fix while still exposing madgraph5#826 and madgraph5#856
… my O/S - no change, no new files
Hi @oliviermattelaer I think that this is ready for review. Can you please have a look? Thanks! (I still need to run some manual tests before merging, but the PR is ready for review as nothing will really change functionally). |
pls note I'm looking into this and I think its understood, will reply later in #826 |
…aph5#856 in tmad) STARTED AT Fri Jun 28 06:58:24 PM CEST 2024 ./tput/teeThroughputX.sh -mix -hrd -makej -eemumu -ggtt -ggttg -ggttgg -gqttq -ggttggg -makeclean ENDED(1) AT Fri Jun 28 08:31:16 PM CEST 2024 [Status=0] ./tput/teeThroughputX.sh -flt -hrd -makej -eemumu -ggtt -ggttgg -inlonly -makeclean ENDED(2) AT Fri Jun 28 08:46:49 PM CEST 2024 [Status=0] ./tput/teeThroughputX.sh -makej -eemumu -ggtt -ggttg -gqttq -ggttgg -ggttggg -flt -bridge -makeclean ENDED(3) AT Fri Jun 28 08:54:47 PM CEST 2024 [Status=0] ./tput/teeThroughputX.sh -eemumu -ggtt -ggttgg -flt -rmbhst ENDED(4) AT Fri Jun 28 08:57:29 PM CEST 2024 [Status=0] ./tput/teeThroughputX.sh -eemumu -ggtt -ggttgg -flt -curhst ENDED(5) AT Fri Jun 28 09:00:08 PM CEST 2024 [Status=0] ./tput/teeThroughputX.sh -eemumu -ggtt -ggttgg -flt -common ENDED(6) AT Fri Jun 28 09:02:53 PM CEST 2024 [Status=0] ./tput/teeThroughputX.sh -mix -hrd -makej -susyggtt -susyggt1t1 -smeftggtttt -heftggbb -makeclean ENDED(7) AT Fri Jun 28 09:14:39 PM CEST 2024 [Status=0]
…n heft madgraph5#833, susy madgraph5#826 and also gqttq madgraph5#845 - but ggttgg madgraph5#856 is fixed) Note two points: - gqttq madgraph5#845 is normally intermittent, so it is interesting that it showed up here (even without OMP) - the tmad CI also shows pptt012j madgraph5#872, but I am not running pptt012j tests in the tmad suite yet STARTED AT Fri Jun 28 09:14:39 PM CEST 2024 (SM tests) ENDED(1) AT Sat Jun 29 01:37:39 AM CEST 2024 [Status=0] (BSM tests) ENDED(1) AT Sat Jun 29 01:47:20 AM CEST 2024 [Status=0] 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_eemumu_mad/log_eemumu_mad_d_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_eemumu_mad/log_eemumu_mad_f_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_eemumu_mad/log_eemumu_mad_m_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttggg_mad/log_ggttggg_mad_d_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttggg_mad/log_ggttggg_mad_f_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttggg_mad/log_ggttggg_mad_m_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttgg_mad/log_ggttgg_mad_d_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttgg_mad/log_ggttgg_mad_f_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttgg_mad/log_ggttgg_mad_m_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttg_mad/log_ggttg_mad_d_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttg_mad/log_ggttg_mad_f_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttg_mad/log_ggttg_mad_m_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggtt_mad/log_ggtt_mad_d_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggtt_mad/log_ggtt_mad_f_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggtt_mad/log_ggtt_mad_m_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_gqttq_mad/log_gqttq_mad_d_inl0_hrd0.txt 16 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_gqttq_mad/log_gqttq_mad_f_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_gqttq_mad/log_gqttq_mad_m_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_heftggbb_mad/log_heftggbb_mad_d_inl0_hrd0.txt 1 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_heftggbb_mad/log_heftggbb_mad_f_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_heftggbb_mad/log_heftggbb_mad_m_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_smeftggtttt_mad/log_smeftggtttt_mad_d_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_smeftggtttt_mad/log_smeftggtttt_mad_f_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_smeftggtttt_mad/log_smeftggtttt_mad_m_inl0_hrd0.txt 0 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_susyggt1t1_mad/log_susyggt1t1_mad_d_inl0_hrd0.txt 0 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_susyggt1t1_mad/log_susyggt1t1_mad_f_inl0_hrd0.txt 0 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_susyggt1t1_mad/log_susyggt1t1_mad_m_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_susyggtt_mad/log_susyggtt_mad_d_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_susyggtt_mad/log_susyggtt_mad_f_inl0_hrd0.txt 24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_susyggtt_mad/log_susyggtt_mad_m_inl0_hrd0.txt
I have completed also all manual tests - this is ready to be merged |
Hi Andrea, Changing the base since I need to see what you did change compare to my fix_826 branch. |
Hi Olivier, this is causing conflicts. And fix_826 itself has conflicts to the latest master now I guess. I spent quite some effort fixing conflicts to make sure this can be merged into master. I will not do this again, sorry. But if it helps you to review, ok. However when/if we decide to merge, this must merge into master, not into fix_826 Thanks Andrea |
PS Please FIRST review mg5amcnlo/mg5amcnlo#115. This #873 depends on that. |
Anyway, apart from logs, test scripts etc, the only relevant changes are the MG5AMC upgrade and this
|
Essentially I went back to my three step mapping instead of your one step mapping. Given how complex this is (see the fact that even export_cpp and export_v4 disagree due to fortran/cpp indexing in mg5amcnlo/mg5amcnlo#115), I really think this makes it clearer. And the generated code diffs are these
|
And this means I remove the first element of the channel-to-config array, to just keep the fortran mappings: essentially this array does the fortran-to-fortran mapping, then some variables handle the -1 translation to C indexing. There are Ndiag+1 (7 here) entries in Olivier's code and Ndiag in mine (6 here), note that only Ndiag mappings are needed, not Ndiag+1.
|
…t on Olivier's latest fix_826 commit d23e773 1) Note about Olivier's latest fix_826 commit d23e773 Olivier's 75c05c5 includes his initial 6 commits in fix_826: git log upstream/master --oneline -n1 0992927 (upstream/master, origin/color2, origin/actions) Merge pull request madgraph5#857 from valassi/tmad git log --oneline 0992927..75c05c5 75c05c5 Merge branch 'master_june24' into fix_826 92a8284 better comment in coloramps 2bcea76 trying to fix git issue 63494ef change to Andrea convention of naming (but removing step variable) 5b6d065 increase readibility and move from map to array 41ddc38 fix a issue for omp compilation bed2e12 try to fix the segfault on issue 826 Olivier's d23e773 is then a merge of the latest upstream/master in 75c05c5, fixing the MG5AMC conflict by setting it to 74fd166c1 git show d23e773 Merge: 75c05c5 0992927 update this branch with andrea fix in master diff --cc MG5aMC/mg5amcnlo - Subproject commit 10378b3c0971e1a241fd9dc365e592c92d1f13ba -Subproject commit f274cab55d5d983c5612ca7ab3417ee796aa1a8c ++Subproject commit 74fd166c1e22bde2dfe01b2e001ac3b177628165 2) Note that, in MG5AMC, 74fd166c1 (obsolete branch gpucpp_826) is the same as 09c96dd17 (branch gpucpp): git diff 74fd166c1 09c96dd17 [NO DIFF] git log --oneline e428e38c6..09c96dd17 09c96dd17 (origin/gpucpp) allow for second exporter to have access to all variable used in the fortran exporter 9abf6a3ad Merge pull request madgraph5#113 from valassi/valassi_volatile f274cab55 (ghav/valassi_volatile, valassi_volatile) Workaround for SIGFPE crashes in function rotxxx (madgraph5#855): add 'volatile' to prevent optimizations 0b8678984 Merge pull request madgraph5#112 from valassi/valassi_uninitialised111 18696c1cf Merge pull request madgraph5#110 from valassi/valassi_leak109 4f8fbb7f3 (ghav/valassi_uninitialised111) Workaround for issue madgraph5#111 reported by valgrind (initialise goodjet array in function setclscales in reweight.f) f6d90fa58 (ghav/valassi_leak109, valassi_leak109) Fix memory leak madgraph5#109 in madevent_driver.f (close file dname.mg) f9f957918 (valgrind) Fix validity time check for UFO pickle (madgraph5#97) 619f5db45 avoid that some parameter switch type when loading model git log --oneline e428e38c6..74fd166c 74fd166c1 (HEAD, origin/gpucpp_826, gpucpp_826) Merge remote-tracking branch 'origin/gpucpp' (PR madgraph5#113 for madgraph5#855 crash in rotxxx) into gpucpp_826 9abf6a3ad Merge pull request madgraph5#113 from valassi/valassi_volatile f274cab55 (ghav/valassi_volatile, valassi_volatile) Workaround for SIGFPE crashes in function rotxxx (madgraph5#855): add 'volatile' to prevent optimizations e4d9df4ab Merge remote-tracking branch 'origin/gpucpp' (PRs madgraph5#110 and madgraph5#112 for issues madgraph5#109 and madgraph5#111) into gpucpp_826 0b8678984 Merge pull request madgraph5#112 from valassi/valassi_uninitialised111 18696c1cf Merge pull request madgraph5#110 from valassi/valassi_leak109 4f8fbb7f3 (ghav/valassi_uninitialised111) Workaround for issue madgraph5#111 reported by valgrind (initialise goodjet array in function setclscales in reweight.f) f6d90fa58 (ghav/valassi_leak109, valassi_leak109) Fix memory leak madgraph5#109 in madevent_driver.f (close file dname.mg) 10378b3c0 allow for second exporter to have access to all variable used in the fortran exporter f9f957918 (valgrind) Fix validity time check for UFO pickle (madgraph5#97) 619f5db45 avoid that some parameter switch type when loading model 3) Note that color includes the following submodule updates, passing through 09c96dd17 to ba54a4153 git show --oneline upstream/master..color ../../MG5aMC/ 4b29496 [color] update MG5AMC to ba54a4153 in th egpuccp branch, with a minor fix in a comment for my icolamp patch Submodule MG5aMC/mg5amcnlo 99e064157..ba54a4153: > minor fix in a printout in my previous patch in export_cpp.py 1c2a02d [color] update MG5AMC to 99e064157, fixing bug madgraph5#856 (and related ones) about the icolamp array in coloramps.h Submodule MG5aMC/mg5amcnlo 09c96dd17..99e064157: > In export_cpp.py fix bug madgraph5#114 in get_icolamp_lines, resulting in different icolamp arrays for F77 and CPP (see madgraph5#873) 0a60262 [color] update MG5AMC to 09c96dd17: this is the latest gpucpp branch, now including Olivier's extra commit previously in gpucpp_826 Submodule MG5aMC/mg5amcnlo 10378b3c0...09c96dd17: > allow for second exporter to have access to all variable used in the fortran exporter > Merge pull request madgraph5#113 from valassi/valassi_volatile > Merge pull request madgraph5#112 from valassi/valassi_uninitialised111 > Merge pull request madgraph5#110 from valassi/valassi_leak109 < allow for second exporter to have access to all variable used in the fortran exporter 16ff942 try to fix the segfault on issue 826 Submodule MG5aMC/mg5amcnlo f9f957918..10378b3c0: > allow for second exporter to have access to all variable used in the fortran exporter 4b12e79 [color] temporarely downgrade back MG5AMC to the common base of gpucpp and gpucpp_826, to allow cherry-picking Olivier's fix_826 changes > Submodule MG5aMC/mg5amcnlo f274cab55..f9f957918 (rewind): < Workaround for SIGFPE crashes in function rotxxx (madgraph5#855): add 'volatile' to prevent optimizations < Merge pull request madgraph5#112 from valassi/valassi_uninitialised111 < Merge pull request madgraph5#110 from valassi/valassi_leak109 => Therefore I can simply merge origin/color into color2 and fix the MG5AMC conflict by setting it to ba54a4153 (valassi_icolamp114, before more recent changes)
…eplacing madgraph5#873) Fix conflicts: MG5aMC/mg5amcnlo epochX/cudacpp/CODEGEN/PLUGIN/CUDACPP_SA_OUTPUT/madgraph/iolibs/template_files/gpu/coloramps.h epochX/cudacpp/CODEGEN/PLUGIN/CUDACPP_SA_OUTPUT/madgraph/iolibs/template_files/gpu/process_sigmaKin_function.inc epochX/cudacpp/CODEGEN/PLUGIN/CUDACPP_SA_OUTPUT/model_handling.py In all four cases, simply take the code version from branch color. In particular, fix the MG5AMC conflict by setting it to ba54a4153 (valassi_icolamp114 in mg5amcnlo/mg5amcnlo#115, before more recent changes) Note: the content of this branch is now identical to color git log color --oneline -n5 93a547f (origin/color, color) [color] ** COMPLETE COLOR ** add a tmad/gitdifftmad.sh for easier diffs of tmad logs 643466f [color] add a tput/gitdifftput.sh for easier diffs of tput logs 46356d6 [color] rerun 30 tmad tests on itscrd90 - all as expected (failures in heft madgraph5#833, susy madgraph5#826 and also gqttq madgraph5#845 - but ggttgg madgraph5#856 is fixed) 2194e83 [color] rerun 102 tput tests on itscrd90 - all ok (after fixing madgraph5#856 in tmad) b3046e1 [color] in .github/workflows/testsuite_oneprocess.sh, temporarely reenable bypasses for know issues madgraph5#826 in susy and madgraph5#872 in pp_tt012j - the CI tests should pass now git diff 93a547f [NO DIFF]
…adgraph5#852 and color2 PR madgraph5#877, instead of color PR madgraph5#873) into fpe
For the record I did delete the obsolete color branch |
This is a clean WIP MR for iconfig-color mapping issues in coloramps.h. It starts from the current upstream/master, which already includes all relevant changes for rotxxx crashes.
It includes all of Olivier's commits in PR #852, as well as the relevant commits from my PR #853. It also supersedes the tests in WIP PR #870.
It is meant to address #856 (lhe color mismatches in ggttgg) and related issues, like possibly #845.
It is NOT meant to address #826 (no cross section in susy) and has most likely nothing to do with 826 (or susy), even if it includes fragments from 'fix_826" and 'gpucpp_826' and 'susy' branches.