MG5aMC status #867

oliviermattelaer · 2024-06-21T10:26:18Z

oliviermattelaer · 2024-07-04T12:54:06Z

LOOP INDUCED

coupling access:
- The loop matrix-element does not have dedicated vector_id instruction
- model has it
- value is anyway passed correctly, so no need to specify that we always use the first value)
had to change the signature of smatrix$id
- changing the signature is not enough since color/helicity assignment is then buggy
- removed the hel_buff from loop_induced (both from sum and MC over hel)
  - random_hel is obviously useless for MC over hel ...
- add the nice fortran function to associated color

oliviermattelaer · 2024-07-19T15:36:33Z

MADEVENT no grouping

fail to compile (note 3.6.0 does not have such issue)

	    auto_dsig.f:521:31:

	      202 |       SUBROUTINE WRITE_GOOD_HEL(STREAM_ID)
	          |                               2
	    ......
	      521 |       SUBROUTINE WRITE_GOOD_HEL(STREAM_ID)

also code duplication for READ_GOOD_HEL -> wrong template


	      388 |       IF (PASSCUTS(PP)) THEN
	          |                     1
	    Error: Symbol ‘pp’ at (1) has no IMPLICIT type; did you mean ‘lpp’?

-> passed to P1
-> not good -> remove the passcuts for the moment (via export_v4.py)
-> need to check that cut are indeed apply higher in the code (like they should)

auto_dsig.f:391:12:

	      391 |             IB(1) = 1
	          |            1
	    Error: Function ‘ib’ at (1) has no IMPLICIT type
	    auto_dsig.f:392:12:

	      392 |             IB(2) = 2
	          |            1
	    Error: Function ‘ib’ at (1) has no IMPLICIT type
	    auto_dsig.f:394:12:

-> added definition of IB(1)/IB(2) even if variable is not used in this context

coupl.inc:34:41:

	       34 |       DOUBLE COMPLEX GC_10(VECSIZE_MEMMAX), GC_11(VECSIZE_MEMMAX)
	          |                                         1
	    Error: Symbol ‘vecsize_memmax’ at (1) has no IMPLICIT type
	    matrix.f:312:44:

	      312 |       CALL VVV1P0_1(W(1,1),W(1,2),GC_10(IVEC),ZERO, FK_ZERO,W(1,5))
	          |                                            1
	    Error: Symbol ‘ivec’ at (1) has no IMPLICIT type; did you mean ‘ic’?

-> need update of madgraph/iolibs/template_files/matrix_madevent_v4.inc

	    Undefined symbols for architecture arm64:
	      "_get_helicities_", referenced from:
	          _write_leshouche_ in unwgt.o
	      "_prepare_grouping_choice_", referenced from:
	          _sample_full_ in libdsample.a(dsample.o)
	      "_select_color_", referenced from:
	          _smatrix_ in matrix.o
	      "_select_grouping_", referenced from:
	          _sample_full_ in libdsample.a(dsample.o)
	    ld: symbol(s) not found for architecture arm64
	    collect2: error: ld returned 1 exit status
	    make: *** [madevent] Error 1

-> added dummy function for prepare_grouping_choice/select_grouping function
-> define (from the group mode) the missing function in the non group auto_dsig version

At line 656 of file auto_dsig.f
Fortran runtime error: Index '2' of dimension 3 of array 'icolamp' above upper bound of 1

-> need to adapt the select color? -> enforce IPROC=1 solves the issue

wrong cross-section

cross-section matches only in fix-scale
issue with the running point by point ...
more specifically the issue is with mu_R not with mu_F (and therefore not with the computation of the dynamical scale)
no call to update_scale_coupling in auto_dsig.f -> added via a context -> fixed
but CKKW merging scale not working (PDF called before setting of the scale!) -> move the computation before the call to the PDF -> fixed

oliviermattelaer · 2024-08-08T09:02:25Z

Drell-Yan +3 j issues

helicity recycling crashing

occurs both for ickkw=0 and ickkw=1
p p > l+ l- 3g works in standalone
g g > l+ l- 3j has the issue!

 cluster.f: Error. Invalid combination.
 error for clustering
 cluster.f: Error. Invalid combination.
 error for clustering
 cluster.f: Error. Invalid combination.
 error for clustering
 cluster.f: Error. Invalid combination.
 error for clustering
 cluster.f: Error. Invalid combination.
 error for clustering
At line 669 of file cluster.f
Fortran runtime error: Index '1665470336' of dimension 1 of array 'imap' above upper bound of 7

one potential fix is

--- a/Template/LO/SubProcesses/cluster.f
+++ b/Template/LO/SubProcesses/cluster.f
@@ -552,6 +552,8 @@ c**************************************************************************
       if (btest(mlevel,1))
      $   write (*,*)'New event'

+      iwin = 0
+      jwin = 0
       cluster=.false.
       clustered=.false.
       do i=0,3
@@ -663,7 +665,8 @@ c        Set info for LH clustering output
 c     initialize graph storage
       igraphs(0)=0
       nleft=nexternal
-c     cluster
+c     cluster
+      if (iwin.eq.0.or.jwin.eq.0) stop 21
       do n=1,nexternal-2
 c     combine winner
          imocl(n)=imap(iwin,2)+imap(jwin,2)
diff --git a/Template/LO/SubProcesses/reweight.f b/Template/LO/SubProcesses/reweight.f
index a51f0e4c3..76ea80172 100644
--- a/Template/LO/SubProcesses/reweight.f
+++ b/Template/LO/SubProcesses/reweight.f
@@ -643,7 +643,10 @@ c     Variables for keeping track of jets
             enddo
             s_rwfact(ivec)=1d0
          endif
-      return
+         return
+      elseif(init_mode)then ! helicity recycling mode
+          scale = 91.188
+          return ! avoid CKKW scale choice for hel-recycling to avoid isssue with channel-flipping
       endif
 c
 c   Cluster the configuration

The modification of the first file is a pure sanity check to ensure that such issue only occur when checking helicity recycling.
The second is assuming that the clustering does not work in seaking helicity due to the swapping between channel ...
and just use a fix scale here ...
It might be better to do that in setscales.f and to switch fortran variable for fix-scale ...
But the real ugly point is why this is occuring... (3.6.0 does not have such issue), so this sounds a work around to a bug that remains (and that will annoy us later?)
But I guess for the moment, I will check the cross-section

patch confirmed to fix the helicity crash for all subprocesses

missmatch of cross-section

p p > l+ l- 3g OK (LTS: 2.083 +- 0.006164 pb vs gpucpp_for360: 2.088 +- 0.005693 pb)
g g > l+ l- 3j OK (LTS: 7.957 +- 0.02209 pb vs gpucpp_for360: 7.931 +- 0.02541)
full OK (helicity issue bypassed + no ickkw): 67.75 +- 0.1716 pb vs 68.34 +- 0.2027 pb (LTS)
full 4 sigma (helicity issue bypassed + with ickkw): 122.8 pb vs 125.1 pb (LTS)
full OK (helicity issue bypassed + with ickkw, no pdf rewgt, chcluster=F): 103.1 +- 0.2657 vs 104 +- 0.2829(LTS)
full 4.5 sigma (helicity issue bypassed + with ickkw, no pdf rewgt, chcluster=T): 96.41 +- 0.2482 pb vs 99.15 +- 0.2743 pb
full 4sigma (helicity issue bypassed + with ickkw, pdf rewgt, chcluster=F): 122.8 pb vs 125.1 pb (LTS)

oliviermattelaer · 2024-08-08T16:11:47Z

oliviermattelaer · 2024-08-09T13:19:54Z

CROSS-SECTION MISSMATCH EP collision

default test: LTS: 3959+-30 GPU: 3870+-50
NO CKM: 4524 +- 33 GPU: 4555 +- 56.42
NO CKM (dyn_scale=3): 4524 +- 33 GPU: 4555 +- 56.42
default test (500k): LTS: 3932 +- 1.701 GPU: 3932 +- 1.774

-> NO ISSUE HERE (just need to update central value for the test)

oliviermattelaer · 2024-08-12T15:02:13Z

test_ML_check_full_epem_ttx

simpler reproducer via script

set loop_optimized_output False
set gauge unitary
generate e+ e- > t t~ [virt=QCD]
output
launch

observation:

seems working if loop_optimized_output True
diff with LTS has the following weird diff for loop_num (see below)
fixing the loop_num file seems to fix the issue
linked to a "not safe" try ... except in helas_call_writers
now code is crashing with an explicit "KeyError : 'LC(1)'"
debug file point to "model vectorization" change to the code: if coupling_dep and 'aS' in coupling_dep[c]: (helas_objects.py", line 1589)
FIXED

weird diff in loop_num

diff ./loop_num.f /Users/omattelaer/Documents/git_workspace/LTS/PROC_SA_loop_sm_1/SubProcesses/P0_epem_ttx/loop_num.f
136,138c136,138
<
<
<
---
>           CALL FFV1LP0_3(WL(1,2),W(1,WE(1),H),LC(1),ML(3),ZERO,WL(1,3))
>           CALL FFV1L_2(W(1,WE(2),H),WL(1,3),LC(2),ML(4),ZERO,WL(1,4))
>           CALL FFV1L_2(WL(1,4),W(1,WE(3),H),LC(3),ML(5),ZERO,WL(1,5))
146,148c146,149
<
<
<
---
>           CALL FFV1LP0_3(WL(1,2),W(1,WE(1),H),LC(1),ML(3),ZERO,WL(1,3))
>           CALL FFV1L_2(W(1,WE(2),H),WL(1,3),LC(2),ML(4),ZERO,WL(1,4))
>           CALL FFV2_5L_2(WL(1,4),W(1,WE(3),H),LC(3),LC(4),ML(5),ZERO
>      $     ,WL(1,5))
316,318c317,322
<
<
<
---
>           CALL MP_FFV1LP0_3(WL(1,2),W(1,WE(1),H),LC(1),ML(3),ZERO,WL(1
>      $     ,3))
>           CALL MP_FFV1L_2(W(1,WE(2),H),WL(1,3),LC(2),ML(4),ZERO,WL(1,4)
>      $     )
>           CALL MP_FFV1L_2(WL(1,4),W(1,WE(3),H),LC(3),ML(5),ZERO,WL(1,5)
>      $     )

oliviermattelaer · 2024-08-13T20:42:41Z

Merging with branch gpucpp_goodhel (and therefore latest 3.6.0 commit)

fail unitest on file_writers (function had a merging issue that I overlooked)

oliviermattelaer · 2024-08-14T19:42:48Z

parralel test gpucpp

FAILED (failures=15)
test_short_cross_sqso1 test_gauge_4_e500 test_gauge_6_e500 test_gauge_6_e90 test_long_sm_vs_stored_HCR_dxd_wpwm_QCD test_long_sm_vs_stored_HCR_dxd_wpwm_QED test_long_sm_vs_stored_HCR_dxd_zz_QCD test_long_sm_vs_stored_HCR_dxd_zz_QED test_long_sm_vs_stored_HCR_uxd_wmz_QCD test_long_sm_vs_stored_HCR_uxd_wmz_QED test_long_sm_vs_stored_HCR_uxu_wpwm_QCD test_long_sm_vs_stored_HCR_uxu_wpwm_QED test_long_sm_vs_stored_HCR_uxu_zz_QCD test_long_sm_vs_stored_HCR_uxu_zz_QED test_long_sm_vs_stored_HCR_wpwm_wpwm_QED
FAILED ( errors=16)
test_mg5_heft_23 test_mg5_minitest_mssm test_mg5_minitest_sm test_mg5_mssm_13 test_mg5_mssm_23_p1 test_mg5_mssm_23_p2 test_mg5_sm_13 test_mg5_sm_22 test_mg5_sm_23_p3 test_short_cross_pol test_short_cross_sm1 test_short_OfflineHEPToolsInstaller test_short_mw_tt_full_lept test_short_mw_tt_semi test_short_mw_wa_refine test_short_ppgogo_amcatnlo_nlo
Bypassed 11:
test_long_mssm_vs_stored_HCR_gg_t1t1xg_QCD test_long_mssm_vs_stored_HCR_uux_gogog_QCD test_mg5_mssm_22 test_mg5_sm_23_p1 test_mg5_sm_23_p2 test_paralel_cross_sm test_cross_gauge_p2 test_gauge_2 test_gauge_loop_p1 test_gauge_loop_p2 test_short_jet_veto_xsec

status for 360

FAILED (failures=12)
test_gauge_4_e500 test_long_sm_vs_stored_HCR_dxd_wpwm_QCD test_long_sm_vs_stored_HCR_dxd_wpwm_QED test_long_sm_vs_stored_HCR_dxd_zz_QCD test_long_sm_vs_stored_HCR_dxd_zz_QED test_long_sm_vs_stored_HCR_uxd_wmz_QCD test_long_sm_vs_stored_HCR_uxd_wmz_QED test_long_sm_vs_stored_HCR_uxu_wpwm_QCD test_long_sm_vs_stored_HCR_uxu_wpwm_QED test_long_sm_vs_stored_HCR_uxu_zz_QCD test_long_sm_vs_stored_HCR_uxu_zz_QED test_long_sm_vs_stored_HCR_wpwm_wpwm_QED
FAILED ( errors=14)
test_mg5_heft_23 test_mg5_minitest_mssm test_mg5_minitest_sm test_mg5_mssm_13 test_mg5_mssm_22 test_mg5_mssm_23_p1 test_mg5_mssm_23_p2 test_mg5_sm_13 test_mg5_sm_22 test_mg5_sm_23_p1 test_mg5_sm_23_p2 test_mg5_sm_23_p3 test_paralel_cross_sm test_short_OfflineHEPToolsInstaller
Bypassed 2:
test_cross_gauge_p2 test_short_jet_veto_xsec

to investigate first:

test_short_cross_pol

from madevent_forhel
At line 1228 of file auto_dsig.f
Fortran runtime error: Index '2' of dimension 1 of array 'icolamp' above upper bound of 1

test_short_cross_sm1
test_short_mw_tt_full_lept

 gfortran -w -fPIC  -ffixed-line-length-132 -w  -c -o auto_dsig1.o auto_dsig1.f
	    auto_dsig1.f:87:16:

	       87 |           QSCALE=0D0
	          |                1
	    Error: Symbol ‘qscale’ at (1) has no IMPLICIT type
	    auto_dsig1.f:84:14:

	       84 |       IF (ABS(LPP(IB(1))).GE.1) THEN
	          |              1
	    Error: Function ‘lpp’ at (1) has no IMPLICIT type
	    auto_dsig1.f:86:18:

test_short_mw_tt_semi
test_short_mw_wa_refine
test_short_ppgogo_amcatnlo_nlo (in 3.6.0 (sudakov) parralel test failing for 3.6.0 mg5amcnlo/mg5amcnlo#129):
- fixed in 3.6.0 by marco (need to be merged in this branch but I consider it fixed for the moment)

Adding CI for

oliviermattelaer mentioned this issue Jun 21, 2024

Updated workplan (May 2023) towards a first alpha release #671

Open

oliviermattelaer self-assigned this Jul 4, 2024

oliviermattelaer pinned this issue Jul 5, 2024

oliviermattelaer mentioned this issue Aug 8, 2024

DY+3 jets cross section decreases by a factor 10 when changing vector size from 16384 to 32? #959

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

MG5aMC status #867

MG5aMC status #867

oliviermattelaer commented Jun 21, 2024 •

edited

Loading

oliviermattelaer commented Jul 4, 2024 •

edited

Loading

oliviermattelaer commented Jul 19, 2024 •

edited

Loading

oliviermattelaer commented Aug 8, 2024 •

edited

Loading

oliviermattelaer commented Aug 8, 2024 •

edited

Loading

oliviermattelaer commented Aug 9, 2024 •

edited

Loading

oliviermattelaer commented Aug 12, 2024 •

edited

Loading

oliviermattelaer commented Aug 13, 2024 •

edited

Loading

oliviermattelaer commented Aug 14, 2024 •

edited

Loading

MG5aMC status #867

MG5aMC status #867

Comments

oliviermattelaer commented Jun 21, 2024 • edited Loading

oliviermattelaer commented Jul 4, 2024 • edited Loading

LOOP INDUCED

oliviermattelaer commented Jul 19, 2024 • edited Loading

MADEVENT no grouping

wrong cross-section

oliviermattelaer commented Aug 8, 2024 • edited Loading

Drell-Yan +3 j issues

helicity recycling crashing

missmatch of cross-section

oliviermattelaer commented Aug 8, 2024 • edited Loading

Acceptance tests:

oliviermattelaer commented Aug 9, 2024 • edited Loading

oliviermattelaer commented Aug 12, 2024 • edited Loading

test_ML_check_full_epem_ttx

weird diff in loop_num

oliviermattelaer commented Aug 13, 2024 • edited Loading

Merging with branch gpucpp_goodhel (and therefore latest 3.6.0 commit)

oliviermattelaer commented Aug 14, 2024 • edited Loading

parralel test gpucpp

status for 360

to investigate first:

Adding CI for

oliviermattelaer commented Jun 21, 2024 •

edited

Loading

oliviermattelaer commented Jul 4, 2024 •

edited

Loading

oliviermattelaer commented Jul 19, 2024 •

edited

Loading

oliviermattelaer commented Aug 8, 2024 •

edited

Loading

oliviermattelaer commented Aug 8, 2024 •

edited

Loading

oliviermattelaer commented Aug 9, 2024 •

edited

Loading

oliviermattelaer commented Aug 12, 2024 •

edited

Loading

oliviermattelaer commented Aug 13, 2024 •

edited

Loading

oliviermattelaer commented Aug 14, 2024 •

edited

Loading