Calculating cross section with auxiliary propagators

Asked by sehar ajmal

Hi, My model contains contact interactions so i'm using auxiliary propagators in order to calculate the production cross section and it worked fine in calchep but in Madgraph the production cross section is giving me errors or zero value when we tried to calculate the diagrams with auxiliary propagators. However, when we remove the diagram with auxiliary propagators it is giving us a non zero cross section. The error i'm getting is following

INFO: Update the dependent parameter of the param_card.dat
Generating 10000 events with run name run_01
survey run_01
INFO: compile directory
compile Source Directory
Using random number seed offset = 21
INFO: Running Survey
Creating Jobs
Working on SubProcesses
INFO: Compiling for process 1/1.
INFO: P1_qq_e0l
INFO: P1_qq_e0l
INFO: Idle: 1, Running: 0, Completed: 0 [ current time: 11h14 ]

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0 0x105fd0b17
#1 0x105fcfbab
#2 0x192baac43
rm: results.dat: No such file or directory
ERROR DETECTED

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0 0x107918b17
#1 0x107917bab
#2 0x192baac43
rm: results.dat: No such file or directory
ERROR DETECTED
INFO: Idle: 0, Running: 0, Completed: 1 [ 0.4s ]
INFO: Idle: 0, Running: 0, Completed: 1 [ 0.4s ]
INFO: End survey
refine 10000
Creating Jobs
INFO: Refine results to 10000
INFO: Generating 10000.0 unweighted events.
Error when reading /Users/seharajmal/MG5_aMC_v3_1_0/bin/M1/SubProcesses/P1_qq_e0l/G1/results.dat
Command "generate_events run_01" interrupted with error:
Exception : Reported error: End code 139.0
  Full associated log:
  Process in group number 1
  A PDF is used, so alpha_s(MZ) is going to be modified
  Old value of alpha_s from param_card: 0.11839999999999999
   ****************************************

        NNPDFDriver version 1.0.3
    Grid: NNPDF23_lo_as_0130_qed_mem0.grid
   ****************************************
  New value of alpha_s from PDF nn23lo1: 0.13000000000000000
  Define smin to 29160000.000000000
  *****************************************************
  * MadGraph/MadEvent *
  * -------------------------------- *
  * http://madgraph.hep.uiuc.edu *
  * http://madgraph.phys.ucl.ac.be *
  * http://madgraph.roma2.infn.it *
  * -------------------------------- *
  * *
  * PARAMETER AND COUPLING VALUES *
  * *
  *****************************************************

   External Params
   ---------------------------------

  mdl_cabi = 0.22773599999999999
  mdl_lc = 5400.0000000000000
  mdl_MUU = 5400.0000000000000
  mdl_MPi = 1000.0000000000000
  mdl_FPi = 5000.0000000000000
  mdl_cabi2 = 0.22773599999999999
  mdl_MB = 4.7000000000000002
  mdl_MT = 172.00000000000000
  mdl_MM = 0.10566000000000000
  mdl_MTA = 1.7769999999999999
  mdl_MZ = 91.187600000000003
  mdl_MH = 120.00000000000000
  aEWM1 = 127.90000000000001
  mdl_Gf = 1.1663700000000000E-005
  aS = 0.11839999999999999
  mdl_ymb = 4.7000000000000002
  mdl_ymt = 172.00000000000000
  mdl_ymtau = 1.7769999999999999
  mdl_WT = 1.5083359999999999
  mdl_WZ = 2.4952000000000001
  mdl_WW = 2.0850000000000000
  mdl_WH = 5.7530880000000000E-003
  mdl_WEs = 30.000000000000000
  mdl_WMus = 30.000000000000000
  mdl_WTaus = 30.000000000000000
  mdl_WNc1 = 30.000000000000000
  mdl_WNc2 = 30.000000000000000
  mdl_WNc3 = 30.000000000000000
  mdl_WEc = 30.000000000000000
  mdl_WMuc = 30.000000000000000
  mdl_WTauc = 30.000000000000000
  mdl_WN01 = 30.000000000000000
  mdl_WN02 = 30.000000000000000
  mdl_WN03 = 30.000000000000000
  mdl_WPic1 = 30.000000000000000
  mdl_WPi0u = 30.000000000000000
  mdl_WPi0d = 30.000000000000000
   Internal Params
   ---------------------------------

  mdl_cos__cabi = 0.97418004031982097
  mdl_CKM1x1 = (0.97418004031982097,0.0000000000000000)
  mdl_sin__cabi = 0.22577256042856930
  mdl_CKM1x2 = (0.22577256042856930,0.0000000000000000)
  mdl_CKM2x1 = (-0.22577256042856930,0.0000000000000000)
  mdl_CKM2x2 = (0.97418004031982097,0.0000000000000000)
  mdl_ONE1x1 = 1.0000000000000000
  mdl_ONE1x2 = 1.0000000000000000
  mdl_ONE1x3 = 1.0000000000000000
  mdl_ONE2x1 = 1.0000000000000000
  mdl_ONE2x2 = 1.0000000000000000
  mdl_ONE2x3 = 1.0000000000000000
  mdl_ONE3x1 = 1.0000000000000000
  mdl_ONE3x2 = 1.0000000000000000
  mdl_ONE3x3 = 1.0000000000000000
  mdl_gstar = 3.5449077018110318
  mdl_MZ__exp__2 = 8315.1783937600012
  mdl_MZ__exp__4 = 69142191.720053151
  mdl_sqrt__2 = 1.4142135623730951
  mdl_MH__exp__2 = 14400.000000000000
  mdl_complexi = (0.0000000000000000,1.0000000000000000)
  mdl_FPi__exp__2 = 25000000.000000000
  mdl_lc__exp__2 = 29160000.000000000
  mdl_conjg__CKM1x1 = (0.97418004031982097,-0.0000000000000000)
  mdl_conjg__CKM1x2 = (0.22577256042856930,-0.0000000000000000)
  mdl_conjg__CKM2x1 = (-0.22577256042856930,-0.0000000000000000)
  mdl_conjg__CKM2x2 = (0.97418004031982097,-0.0000000000000000)
  mdl_aEW = 7.8186082877247844E-003
  mdl_MW = 79.824359746197842
  mdl_sqrt__aEW = 8.8422894590285753E-002

 Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

 Backtrace for this error:
 #0 0x105fd0b17
 #1 0x105fcfbab
 #2 0x192baac43

 ls status:
 input_app.txt
 run1_app.log

Please report this bug on https://bugs.launchpad.net/mg5amcnlo
More information is found in '/Users/seharajmal/MG5_aMC_v3_1_0/bin/M1/run_01_tag_1_debug.log'.
Please attach this file to your report.

Thank you!
Best Regards

Question information

Language:
English Edit question
Status:
Solved
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Solved by:
Olivier Mattelaer
Solved:
Last query:
Last reply:
Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said :
#1

Hi,

The segmentation fault seems to be occuring during the evaluation of the coupling of your model since I do not see any coupling printed inside the log file of the associated segfault.

After that, I can not comment more on the exact formula that create the segfault.
Do you use the same UFO model in calchep? If not it might be a model exporter issue?
In that case which tool are you using to generate your UFO model?

In any case, it might be usefull that you share your model (and more details on your process) such that I can check if your UFO model does make sense.

Cheers,

Olivier

Revision history for this message
sehar ajmal (sajmal0) said :
#2

Hi, Thanks for your reply. I am using Feynrules in order to create UFO model and CH model. I am sharing the link in which i uploaded UFO model: https://drive.google.com/drive/folders/1YDXMo4FPkXLB53v36eY7Zr3p3tyS7Z1S?usp=sharing
About the process i am taking production of Excited fermions p p > e0 e+

Thanks
Best regards

Revision history for this message
Best Olivier Mattelaer (olivier-mattelaer) said :
#3

So the issue seems to be with the custom propagator:

I see that you use the following aloha routine:
FFS3PV0_3.f
and only by the name of the function, you can see that particle 3 is taken as scalar by the lorentz structure and vector for the propagator.

Which explains the following error on my mac:
>At line 27 of file FFS3PV0_3.f
>Fortran runtime error: Index '4' of dimension 1 of array 's3' above upper bound of 3

In propagators.py you can indeed see that the auxiliary propagator is designed for vector.

However it is also used for scalar particle in particles.py ((first one I have seen is

AL01__plus__ = Particle(pdg_code = 9000006,
                        name = 'AL01+',
                        antiname = 'AL01~',
                        spin = 1,
                        color = 1,
                        mass = Param.lc,
                        width = Param.ZERO,
                        propagator = Prop.V0,
                        texname = 'AL01+',
                        antitexname = 'AL01~',
                        charge = 1,
   GhostNumber = 0,
                        LeptonNumber = 0,
                        Y = 0)

Beyond that, I can only refer you to FeynRules authors/manual to fix that issue.

Cheers,

Olivier

Revision history for this message
sehar ajmal (sajmal0) said (last edit ):
#4

Ok, Thanks alot for guidance. I'll contact feynrules authors and I'm marking this problem as solved

best regards
Sehar

Revision history for this message
sehar ajmal (sajmal0) said :
#5