problem with VBF [QCD] for the Higgs production

Hi,

The first error seems to be related to a problem of the machine on which you run.
Looks like the /tmp was corrupted/cleaned when you create your code.

For the second error, I let Marco reply.

Cheers,

Olivier

The process VBF p p > h j j [QCD] receives contribution from IR-divergent pentagon loop diagrams for the subprocesses where the two quark lines have the same flavor.
These pentagon loops involve two weak-boson loop lines and are therefore excluded by MadLoop because there are not formally pure QCD correction (according to MadLoop categorization of QCD loops) .
This is why you must have seen the following warning:

WARNING: Some loop diagrams contributing to this process are discarded because they are not pure (QCD)-perturbation.
Make sure you did not want to include them.

There are two ways to remedy the situation:

----

1) These pentagon loops are color suppressed and most importantly kinematically suppressed since the gluon connects to quark lines travelling in opposite directions.
It has been checked that their contribution is negligible for most intended purposes and you can neglect their finite part (while still pretending to keep their IR poles so as to insure pole cancellation).
This, in practice, means that you can do the computation exactly as you intended to perform it, but simply disabling the Pole check.
You can do so by modifying the following entry in the file 'FKS_params.dat' in the 'Cards' directory of your process:

#IRPoleCheckThreshold
1.0d-5

->

#IRPoleCheckThreshold
-1.0d0

And then launch your process again.

-----

2) You can also decide that you want to compute these contributions and MadLoop can do that, but you have to tweak the code a bit so that the missing pentagons are not filtered away. Here is how you can do so:

You will need to edit the file 'madgraph/loop/loop_interface.py' around line 515 and change the following line:

            if (diag.get_loop_line_types()-set(allowedpart))!=set() or \
                                                       pert_loop_order==set([]):
                valid_diag=False

--> to

            if (diag.get_loop_line_types()-set(allowedpart))!=set() or \
                                                       pert_loop_order==set([]):
                valid_diag=True

and then in the function 'def user_filter(self, model, structs, filter=None):' around line 377, you can change the following line:

        edit_filter_manually = False

to

        edit_filter_manually = True

Finally add the following filter under the ' for diag in self['loop_diagrams']:' do-loop in this 'user_filter' function (next to the other commented examples):

             # Select only the pentagon QCD correction to the VBF, and kick out the other genuine EW corrections.
            if any(abs(pdg) in [22,23,24,25] for pdg in diag.get_loop_lines_pdgs()) and len(diag.get_loop_lines_pdgs())!=5:
                valid_diag = False

You should then be able to run your process:

./bin/mg5_aMC
MG5_aMC> set gauge Feynman
MG5_aMC> import model loop_sm
MG5_aMC> generate p p > h j j [QCD]

You should see the following warning now as well:

WARNING:
    The user-defined loop diagrams filter is turned on and discarded 24 loops

And when looking at the diagrams generated (either in the process output or with the command 'display diagrams' [warning: it will display diagrams for all channels]) you will see that the pentagon loops are included.

The IR pole cancellation should then be successful in this case.
Let me know if you try this and it works for you.

PS: In general, for loops with EW boson running in, the default 'model loop_sm' will not provide a correct result, and you need to load the model 'loop_qcd_qed_sm' to compute them correctly.
However, for this specific case of the pentagons, it will also be correct when computed in the 'loop_sm' model because these loops are UV-finite and do no receive any so-called R2 contributions.

----

Hi Olivier,

Thank you. I removed the /tmp , rm -rf /tmp/amoohamm/* (please correct me if I'm wrong. This on lxplus), and I relaunch the process again. But I got the same error for the process p p > h j j $$ w+ w- z [QCD]. However, this time I manged to copy the error message from the binning, and it looks like this:

""INFO: Compiling P0_uxux_huxux...
INFO: P0_su_hcd done.
INFO: Compiling P0_uxcx_huxcx...
WARNING: fct <function compile_dir at 0x1af6aa0> does not return 0. Stopping the code in a clean way. The error was:
A compilation Error occurs when trying to compile /afs/cern.ch/work/a/amoohamm/private/MONTICARLO/MG5_aMC_v2_4_3/pp_VBF_h_w_z_NLO/SubProcesses/P0_uxu_hddx.
The compilation fails with the following output message:
    /afs/cern.ch/sw/lcg/contrib/gcc/4.9.3/x86_64-slc6-gcc49-opt/bin/gfortran -O -fno-automatic -ffixed-line-length-132 -c -I. check_poles.f
    check_poles.f:124.15:

         1 pmass_rambo, prambo)
                   1
    Warning: Actual argument contains too few elements for dummy argument 'xm' (6/100) at (1)
    check_poles.f:154.19:

         1 pmass_rambo, prambo)
                       1
    Warning: Actual argument contains too few elements for dummy argument 'xm' (6/100) at (1)
    run.inc:79.21:
        Included at check_poles.f:48:

          common/to_rwgt/ do_rwgt_scale, rw_Fscale_down, rw_Fscale_up, rw_Rscale_down, rw_Rscale_up,
                         1
    Warning: Padding of 4 bytes required before 'rw_fscale_down' in COMMON 'to_rwgt' at (1); reorder elements or use -fno-align-commons
    /afs/cern.ch/sw/lcg/contrib/gcc/4.9.3/x86_64-slc6-gcc49-opt/bin/gfortran -O -fno-automatic -ffixed-line-length-132 -c -I. BinothLHA.f
    /afs/cern.ch/sw/lcg/contrib/gcc/4.9.3/x86_64-slc6-gcc49-opt/bin/gfortran -O -fno-automatic -ffixed-line-length-132 -c -I. born_hel.f
    for dir in `ls -d V*`; do cd $dir; make; cd ../; done
    make[1]: Entering directory `/afs/cern.ch/work/a/amoohamm/private/MONTICARLO/MG5_aMC_v2_4_3/pp_VBF_h_w_z_NLO/SubProcesses/P0_uxu_hddx/V0_uxu_hddx'
    rm -f ../libMadLoop.a
    /afs/cern.ch/sw/lcg/contrib/gcc/4.9.3/x86_64-slc6-gcc49-opt/bin/gfortran -fno-automatic -ffixed-line-length-132 -O3 -c polynomial.f -o polynomial.o
    /afs/cern.ch/sw/lcg/contrib/gcc/4.9.3/x86_64-slc6-gcc49-opt/bin/gfortran -O -fno-automatic -ffixed-line-length-132 -c loop_matrix.f -I /afs/cern.ch/work/a/amoohamm/private/MONTICARLO/MG5_aMC_v2_4_3/HEPTools/include
    MadLoopParams.inc:18.22:
        Included at loop_matrix.f:214:

          common /MADLOOP/CTModeInit,CTModeRun,NRotations_DP,NRotations_QP,
                          1
    Warning: Padding of 4 bytes required before 'zerothres' in COMMON 'madloop' at (1); reorder elements or use -fno-align-commons
    MadLoopParams.inc:18.22:
        Included at loop_matrix.f:1662:

          common /MADLOOP/CTModeInit,CTModeRun,NRotations_DP,NRotations_QP,
                          1
    Warning: Padding of 4 bytes required before 'zerothres' in COMMON 'madloop' at (1); reorder elements or use -fno-align-commons
    MadLoopParams.inc:18.22:
        Included at loop_matrix.f:1605:

          common /MADLOOP/CTModeInit,CTModeRun,NRotations_DP,NRotations_QP,
                          1
    Warning: Padding of 4 bytes required before 'zerothres' in COMMON 'madloop' at (1); reorder elements or use -fno-align-commons
    MadLoopParams.inc:18.22:
        Included at loop_matrix.f:1779:

          common /MADLOOP/CTModeInit,CTModeRun,NRotations_DP,NRotations_QP,
                          1
    Warning: Padding of 4 bytes required before 'zerothres' in COMMON 'madloop' at (1); reorder elements or use -fno-align-commons
    MadLoopParams.inc:18.22:
        Included at loop_matrix.f:2149:

          common /MADLOOP/CTModeInit,CTModeRun,NRotations_DP,NRotations_QP,
                          1
    Warning: Padding of 4 bytes required before 'zerothres' in COMMON 'madloop' at (1); reorder elements or use -fno-align-commons
    /afs/cern.ch/sw/lcg/contrib/gcc/4.9.3/x86_64-slc6-gcc49-opt/bin/gfortran -O -fno-automatic -ffixed-line-length-132 -c improve_ps.f -I /afs/cern.ch/work/a/amoohamm/private/MONTICARLO/MG5_aMC_v2_4_3/HEPTools/include
    gfortran: internal compiler error: Segmentation fault (program f951)
    0x409edc execute
     ../../gcc-4.9.3/gcc/gcc.c:2854
    0x40a2a4 do_spec_1
     ../../gcc-4.9.3/gcc/gcc.c:4658
    0x40cb66 process_brace_body
     ../../gcc-4.9.3/gcc/gcc.c:5941
    0x40cb66 handle_braces
     ../../gcc-4.9.3/gcc/gcc.c:5855
    0x40b119 do_spec_1
     ../../gcc-4.9.3/gcc/gcc.c:5312
    0x40cb66 process_brace_body
     ../../gcc-4.9.3/gcc/gcc.c:5941
    0x40cb66 handle_braces
     ../../gcc-4.9.3/gcc/gcc.c:5855
    0x40b119 do_spec_1
     ../../gcc-4.9.3/gcc/gcc.c:5312
    0x40ae83 do_spec_1
     ../../gcc-4.9.3/gcc/gcc.c:5427
    0x40cb66 process_brace_body
     ../../gcc-4.9.3/gcc/gcc.c:5941
    0x40cb66 handle_braces
     ../../gcc-4.9.3/gcc/gcc.c:5855
    0x40b119 do_spec_1
     ../../gcc-4.9.3/gcc/gcc.c:5312
    0x40cb66 process_brace_body
     ../../gcc-4.9.3/gcc/gcc.c:5941
    0x40cb66 handle_braces
     ../../gcc-4.9.3/gcc/gcc.c:5855
    0x40b119 do_spec_1
     ../../gcc-4.9.3/gcc/gcc.c:5312
    0x40bc36 do_spec_2
     ../../gcc-4.9.3/gcc/gcc.c:4359
    0x40d248 do_spec(char const*)
     ../../gcc-4.9.3/gcc/gcc.c:4326
    Please submit a full bug report,
    with preprocessed source if appropriate.
    Please include the complete backtrace with any bug report.
    See <http://gcc.gnu.org/bugs.html> for instructions.
    make[1]: *** [improve_ps.o] Error 4
    make[1]: Leaving directory `/afs/cern.ch/work/a/amoohamm/private/MONTICARLO/MG5_aMC_v2_4_3/pp_VBF_h_w_z_NLO/SubProcesses/P0_uxu_hddx/V0_uxu_hddx'
    /afs/cern.ch/sw/lcg/contrib/gcc/4.9.3/x86_64-slc6-gcc49-opt/bin/gfortran -o check_poles parton_lum_1.o parton_lum_2.o parton_lum_3.o parton_lum_chooser.o matrix_1.o matrix_2.o matrix_3.o real_me_chooser.o fks_inc_chooser.o leshouche_inc_chooser.o genps_fks.o setcuts.o setscales.o born.o sborn_sf.o b_sf_001.o b_sf_002.o b_sf_003.o b_sf_004.o b_sf_005.o b_sf_006.o fks_Sij.o trapfpe.o fastjetfortran_madfks_core.o fjcore.o fastjet_wrapper.o fks_singular.o veto_xsec.o montecarlocounter.o reweight_xsec.o boostwdir2.o configs_and_props_inc_chooser.o initcluster.o cluster.o reweight.o get_color.o FKSParamReader.o iproc_map.o MC_integer.o reweight_xsec_events_pdf_dummy.o appl_interface_dummy.o cuts.o pythia_unlops.o recluster.o check_poles.o BinothLHA.o born_hel.o -L../../lib/ libMadLoop.a -lcts -liregi -L/afs/cern.ch/work/a/amoohamm/private/MONTICARLO/MG5_aMC_v2_4_3/HEPTools/lib/ -lninja -L../../lib/ -ldhelas -lgeneric -lmodel -lpdf -lcernlib -lstdc++ -lstdc++
    gfortran: error: libMadLoop.a: No such file or directory
    make: *** [check_poles] Error 1

Please try to fix this compilations issue and retry.
Help might be found at https://answers.launchpad.net/mg5amcnlo.
If you think that this is a bug, you can report this at https://bugs.launchpad.net/mg5amcnlo
INFO: P0_uxd_huxd done.
INFO: P0_uxc_hsdx done.
INFO: P0_uxu_huux done.
INFO: P0_uxc_huxc done.
INFO: P0_uxs_huxs done.
INFO: P0_uxux_huxux done.
INFO: P0_uxcx_huxcx done. ""

The other process (p p > h j j [QCD]) has been nicely handled by Valentin. But I have some issue with the madspin.

Cheers,

abdualazem.

________________________________________
From: <email address hidden> [<email address hidden>] on behalf of Olivier Mattelaer [<email address hidden>]
Sent: 22 August 2016 21:13
To: Abdualazem Fadol Mohammed
Subject: Re: [Question #356087]: problem with VBF [QCD] for the Higgs production

Your question #356087 on MadGraph5_aMC@NLO changed:
https://answers.launchpad.net/mg5amcnlo/+question/356087

    Status: Open => Answered

Olivier Mattelaer proposed the following answer:
Hi,

The first error seems to be related to a problem of the machine on which you run.
Looks like the /tmp was corrupted/cleaned when you create your code.

For the second error, I let Marco reply.

Cheers,

Olivier

--
If this answers your question, please go to the following page to let us
know that it is solved:
https://answers.launchpad.net/mg5amcnlo/+question/356087/+confirm?answer_id=0

If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https://answers.launchpad.net/mg5amcnlo/+question/356087

You received this question notification because you asked the question.

Hi Valentin,

Thank you. I tried the first suggestion with the madspin on. It seems fine up to the point where I got the output events.lhe.gz. But when it try to generate the Madspin matrix element I got this print at the end:

""INFO:
INFO: generating the production square matrix element
INFO: generate p p > h j j --no_warning=duplicate;define pert_QCD = -4 -3 -2 -1 1 2 3 4 21;add process p p > h j j pert_QCD --no_warning=duplicate;
INFO: Done 21.58
Command "launch auto " interrupted with error:
Exception : No decay define for process.
Please report this bug on https://bugs.launchpad.net/mg5amcnlo
More information is found in '/afs/cern.ch/work/a/amoohamm/private/MONTICARLO/MG5_aMC_v2_4_3/pp_VBF_h_NLO/run_02_tag_1_debug.log'.
Please attach this file to your report.
INFO:

quit
INFO:

MG5_aMC>
""

I think everything here is fine, But I have no idea why I am getting this message.

Cheers,

Abdualazem.

________________________________________
From: <email address hidden> [<email address hidden>] on behalf of Valentin Hirschi [<email address hidden>]
Sent: 23 August 2016 00:37
To: Abdualazem Fadol Mohammed
Subject: Re: [Question #356087]: problem with VBF [QCD] for the Higgs production

Your question #356087 on MadGraph5_aMC@NLO changed:
https://answers.launchpad.net/mg5amcnlo/+question/356087

Valentin Hirschi proposed the following answer:
The process VBF p p > h j j [QCD] receives contribution from IR-divergent pentagon loop diagrams for the subprocesses where the two quark lines have the same flavor.
These pentagon loops involve two weak-boson loop lines and are therefore excluded by MadLoop because there are not formally pure QCD correction (according to MadLoop categorization of QCD loops) .
This is why you must have seen the following warning:

WARNING: Some loop diagrams contributing to this process are discarded because they are not pure (QCD)-perturbation.
Make sure you did not want to include them.

There are two ways to remedy the situation:

----

1) These pentagon loops are color suppressed and most importantly kinematically suppressed since the gluon connects to quark lines travelling in opposite directions.
It has been checked that their contribution is negligible for most intended purposes and you can neglect their finite part (while still pretending to keep their IR poles so as to insure pole cancellation).
This, in practice, means that you can do the computation exactly as you intended to perform it, but simply disabling the Pole check.
You can do so by modifying the following entry in the file 'FKS_params.dat' in the 'Cards' directory of your process:

#IRPoleCheckThreshold
1.0d-5

->

#IRPoleCheckThreshold
-1.0d0

And then launch your process again.

-----

2) You can also decide that you want to compute these contributions and
MadLoop can do that, but you have to tweak the code a bit so that the
missing pentagons are not filtered away. Here is how you can do so:

You will need to edit the file 'madgraph/loop/loop_interface.py' around
line 515 and change the following line:

            if (diag.get_loop_line_types()-set(allowedpart))!=set() or \
                                                       pert_loop_order==set([]):
                valid_diag=False

--> to

            if (diag.get_loop_line_types()-set(allowedpart))!=set() or \
                                                       pert_loop_order==set([]):
                valid_diag=True

and then in the function 'def user_filter(self, model, structs,
filter=None):' around line 377, you can change the following line:

        edit_filter_manually = False

to

        edit_filter_manually = True

Finally add the following filter under the ' for diag in
self['loop_diagrams']:' do-loop in this 'user_filter' function (next to
the other commented examples):

             # Select only the pentagon QCD correction to the VBF, and kick out the other genuine EW corrections.
            if any(abs(pdg) in [22,23,24,25] for pdg in diag.get_loop_lines_pdgs()) and len(diag.get_loop_lines_pdgs())!=5:
                valid_diag = False

You should then be able to run your process:

./bin/mg5_aMC
MG5_aMC> set gauge Feynman
MG5_aMC> import model loop_sm
MG5_aMC> generate p p > h j j [QCD]

You should see the following warning now as well:

WARNING:
    The user-defined loop diagrams filter is turned on and discarded 24 loops

And when looking at the diagrams generated (either in the process output
or with the command 'display diagrams' [warning: it will display
diagrams for all channels]) you will see that the pentagon loops are
included.

The IR pole cancellation should then be successful in this case.
Let me know if you try this and it works for you.

PS: In general, for loops with EW boson running in, the default 'model loop_sm' will not provide a correct result, and you need to load the model 'loop_qcd_qed_sm' to compute them correctly.
However, for this specific case of the pentagons, it will also be correct when computed in the 'loop_sm' model because these loops are UV-finite and do no receive any so-called R2 contributions.

----

--
If this answers your question, please go to the following page to let us
know that it is solved:
https://answers.launchpad.net/mg5amcnlo/+question/356087/+confirm?answer_id=1

If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https://answers.launchpad.net/mg5amcnlo/+question/356087

You received this question notification because you asked the question.

Dear Valentine,

To avoid the problem of the compiler I switched to lxplus7 which has a new version of gcc, 4.8.5. Hence I downloaded MadGraph5 in a new working space. Then I setupATLAS inside the MadgGraph5. . Afterword, I implemented the lines that you suggested to change. But the file you talk about it, loop_interface.py is not in madgraph/loop/. I found it in loop/interface/. However, I found the lines you are asking me to change i the file loop_diagram_generation.py. When I did the following:

./bin/mg5_aMC
MG5_aMC> set gauge Feynman
MG5_aMC> import model loop_qcd_qed_sm
MG5_aMC> generate p p > h j j [QCD]

I got this WARNING:

"WARNING: Some loop diagrams contributing to this process are discarded because they are not pure (QCD)-perturbation.
Make sure you did not want to include them.
WARNING:
    The user-defined loop diagrams filter is turned on and discarded 0 loops.
"

After this is done I launched the output and switched the shower and the madspin OFF. As I'm planning to shower them after I got the sample by using pythia8. Then I got this "INFO: Compiling P0_uux_hccx...
INFO: Compiling P0_uux_hddx...
Gtk-Message: Failed to load module "canberra-gtk-module"
INFO: P0_us_hcd done.
INFO: Compiling P0_uux_hssx... " when it was compiling, but it didn't stop and continuous until it gave me the following:

"INFO: Result for test_MC:
INFO: Passed.
INFO: Result for check_poles:
Error detected in "launch auto "
write debug file /afs/cern.ch/work/a/amoohamm/private/MG/MG5_aMC_v2_4_3/pp_VBF_h_j_j_@NLO/run_01_tag_1_debug.log
If you need help with this issue please contact us on https://answers.launchpad.net/mg5amcnlo
aMCatNLOError : Poles do not cancel, run cannot continue
quit
INFO:

MG5_aMC>exit

"
INFO: P0_du_hdu done.
INFO: Compiling P0_dcx_hdcx...
INFO: P0_usx_husx done.
INFO: Compiling P0_ddx_huux...
WARNING: fct <function compile_dir at 0x2829d70> does not return 0. Stopping the code in a clean way. The error was:
A compilation Error occurs when trying to compile /afs/cern.ch/work/a/amoohamm/private/MONTICARLO/MG5_aMC_v2_4_3/pp_VBF_h_NLO/SubProcesses/P0_ds_hds.
The compilation fails with the following output message:
    /afs/cern.ch/sw/lcg/contrib/gcc/4.9.3/x86_64-slc6-gcc49-opt/bin/gfortran -O -fno-automatic -ffixed-line-length-132 -c -I. symmetry_fks_test_ME.f
    run.inc:79.21:
        Included at symmetry_fks_test_ME.f:15:

          common/to_rwgt/ do_rwgt_scale, rw_Fscale_down, rw_Fscale_up, rw_Rscale_down, rw_Rscale_up,
                         1
    Warning: Padding of 4 bytes required before 'rw_fscale_down' in COMMON 'to_rwgt' at (1); reorder elements or use -fno-align-commons
    /afs/cern.ch/sw/lcg/contrib/gcc/4.9.3/x86_64-slc6-gcc49-opt/bin/gfortran -lstdc++ -o test_ME symmetry_fks_test_ME.o parton_lum_1.o parton_lum_2.o parton_lum_3.o parton_lum_chooser.o matrix_1.o matrix_2.o matrix_3.o real_me_chooser.o fks_inc_chooser.o leshouche_inc_chooser.o genps_fks.o setcuts.o setscales.o born.o sborn_sf.o b_sf_001.o b_sf_002.o b_sf_003.o b_sf_004.o b_sf_005.o b_sf_006.o fks_Sij.o trapfpe.o fastjetfortran_madfks_core.o fjcore.o fastjet_wrapper.o fks_singular.o veto_xsec.o montecarlocounter.o reweight_xsec.o boostwdir2.o configs_and_props_inc_chooser.o initcluster.o cluster.o reweight.o get_color.o FKSParamReader.o iproc_map.o MC_integer.o reweight_xsec_events_pdf_dummy.o appl_interface_dummy.o BinothLHADummy.o cuts.o pythia_unlops.o recluster.o -L../../lib/ -ldhelas -lgeneric -lmodel -lpdf -lcernlib -lstdc++
    collect2: error: /usr/bin/nm terminated with signal 11 [Segmentation fault]
    make: *** [test_ME] Error 1

Please try to fix this compilations issue and retry.
Help might be found at https://answers.launchpad.net/mg5amcnlo.
If you think that this is a bug, you can report this at https://bugs.launchpad.net/mg5amcnlo
INFO: P0_dux_hscx done.
INFO: P0_dcx_hdcx done.
INFO: P0_dc_hsu done.
INFO: P0_dc_hdc done.
INFO: P0_dd_hdd done.
INFO: P0_dux_hdux done.
INFO: P0_ddx_huux done.
^CWARNING: Fail to compile the Subprocesses
INFO:

INFO: Checking test output:
INFO: P0_uu_huu
INFO: Result for test_ME:
"

When it;s compiling. However, it stopped for awhile when I pressed ctr+ C then it continue to the end with no more errors and give me the output , event.lhe.zp, at the end.

PS:
Regarding the question that Oliver asked, For MadSpin, did you include a decay for the Higgs in the madspin_card?, for the process p p > h j j $$ w+ w- z [QCD]. I stopped the madspin as I'm planing to do this when I'm showering the sample using pythia 8.
And I still got the same error that I posted earlier.

Many thanks to both of you.

Cheers,

Abdualazem.

Dear Abdualazem,

You are right, I had a typo in my message and the file you are supposed to modify is indeed

madgraph/loop/loop_diagram_generation.py

Now you should try with the 'loop_sm-no_b_mass' model and specify the QCD=0 Born amplitude order in your process definition.
You can test the setup before running the full thing with:

./bin/mg5_aMC
MG5_aMC> set gauge Feynman
MG5_aMC> import model loop_sm-no_b_mass
MG5_aMC> generate u u~ > h u u~ QCD=0 [QCD]
MG5_aMC> display diagrams

And make sure you have the expected loops (the QCD triangles along with the QCD pentagons).

Then only try the full run and you should have the poles cancelling. Let me know if you don't find the correct loops or if the poles don't cancel with the setup above (along with the modifications I mentioned in my earlier message).

Hi Valentin,

Thank you.

./bin/mg5_aMC
MG5_aMC> set gauge Feynman
MG5_aMC> import model loop_sm-no_b_mass
MG5_aMC> generate u u~ > h u u~ QCD=0 [QCD]
MG5_aMC> display diagrams

everything is fine up to the display diagrams in which I can see the QCD triangles along with
the QCD pentagons. But the problem comes when I launch it. I got this"

"INFO: Result for test_MC:
INFO: Passed.
INFO: Result for check_poles:
Error detected in "launch auto "
write debug file /afs/cern.ch/work/a/amoohamm/private/MG/MG5_aMC_v2_4_3/uu_test/run_01_tag_1_debug.log
If you need help with this issue please contact us on https://answers.launchpad.net/mg5amcnlo
aMCatNLOError : Poles do not cancel, run cannot continue
quit
INFO:"

This was for the specific test you showed me. I think it's worthy to show you snapshot from the beginning:

"MG5_aMC>import model loop_sm-no_b_mass
INFO: Restrict model loop_sm with file models/loop_sm/restrict_no_b_mass.dat .
INFO: Run "set stdout_level DEBUG" before import for more information.
INFO: Change particles name to pass to MG5 convention
Pass the definition of 'j' and 'p' to 5 flavour scheme.
Kept definitions of multiparticles l- / vl / l+ / vl~ unchanged
Defined multiparticle all = g gh gh~ d u s c b d~ u~ s~ c~ b~ a ve vm vt e- mu- ve~ vm~ vt~ e+ mu+ t t~ z w+ h g0 g+ w- g- ta- ta+
MG5_aMC>generate u u~ > h u u~ QCD=0 [QCD]
WARNING: Process: u u~ > h u u~ QCD=0 [ all = QCD ] can have real emission processes which are not finite.
To avoid this, please use multiparticles when generating the process and be sure to include all the following particles in the multiparticle definition:
 g, b, c, s, u, d, d~, u~, s~, c~, b~
INFO: Generating FKS-subtracted matrix elements for born process: u u~ > h u u~ QCD=0 [ all = QCD ] (1 / 1)
INFO: Generating virtual matrix elements using MadLoop:
INFO: Generating virtual matrix element with MadLoop for process: u u~ > h u u~ QED<=3 QCD=0 [ all = QCD ] (1 / 1)
WARNING: Some loop diagrams contributing to this process are discarded because they are not pure (QCD)-perturbation.
Make sure you did not want to include them.
WARNING:
    The user-defined loop diagrams filter is turned on and discarded 0 loops.
INFO: Generated 1 subprocesses with 24 real emission diagrams, 2 born diagrams and 36 virtual diagrams
MG5_aMC>display diagrams
Drawing Process: u u~ > h u u~ g WEIGHTED<=7 QED<=3 QCD<=1 [ all = QCD ]
Wrote file /tmp/diagrams_0_uux_huuxg.eps
open /tmp/diagrams_0_uux_huuxg.eps
Drawing Process: g u~ > h u u~ u~ WEIGHTED<=7 QED<=3 QCD<=1 [ all = QCD ]
Wrote file /tmp/diagrams_0_gux_huuxux.eps
open /tmp/diagrams_0_gux_huuxux.eps
Drawing Process: u g > h u u u~ WEIGHTED<=7 QED<=3 QCD<=1 [ all = QCD ]
Wrote file /tmp/diagrams_0_ug_huuux.eps
open /tmp/diagrams_0_ug_huuux.eps
time to draw 0.0425329208374
Drawing Process: u u~ > h u u~ QCD=0 [ all = QCD ]
Wrote file /tmp/diagrams_0_uux_huux.eps
open /tmp/diagrams_0_uux_huux.eps
time to draw 0.00540781021118
Drawing Process: u u~ > h u u~ WEIGHTED<=6 QED<=3 QCD=0 [ all = QCD ]
Wrote file /tmp/diagrams_0_uux_huux.eps
open /tmp/diagrams_0_uux_huux.eps
time to draw 0.0325589179993
MG5_aMC>
"

Cheers,

abdualazem.

________________________________________
From: <email address hidden> [<email address hidden>] on behalf of Valentin Hirschi [<email address hidden>]
Sent: 24 August 2016 18:54
To: Abdualazem Fadol Mohammed
Subject: Re: [Question #356087]: problem with VBF [QCD] for the Higgs production

Your question #356087 on MadGraph5_aMC@NLO changed:
https://answers.launchpad.net/mg5amcnlo/+question/356087

Valentin Hirschi posted a new comment:
Dear Abdualazem,

You are right, I had a typo in my message and the file you are supposed
to modify is indeed

madgraph/loop/loop_diagram_generation.py

Now you should try with the 'loop_sm-no_b_mass' model and specify the QCD=0 Born amplitude order in your process definition.
You can test the setup before running the full thing with:

./bin/mg5_aMC
MG5_aMC> set gauge Feynman
MG5_aMC> import model loop_sm-no_b_mass
MG5_aMC> generate u u~ > h u u~ QCD=0 [QCD]
MG5_aMC> display diagrams

And make sure you have the expected loops (the QCD triangles along with
the QCD pentagons).

Then only try the full run and you should have the poles cancelling. Let
me know if you don't find the correct loops or if the poles don't cancel
with the setup above (along with the modifications I mentioned in my
earlier message).

--
You received this question notification because you asked the question.

I forgot that you must also worth within the complex mass scheme, otherwise
the W-boson width will be included in the real-emission diagrams but not in
the corresponding pentagon that should cancel its IR divergence.

You should therefore do:

./bin/mg5_aMC
MG5_aMC> set gauge Feynman
MG5_aMC> set complex_mass_scheme
MG5_aMC> import model loop_sm-no_b_mass
MG5_aMC> generate u u~ > h u u~ QCD=0 [QCD]
(MG5_aMC> display diagrams)
MG5_aMC> launch

then the pole should cancel (I just double-checked).

However, you must get the following message:

INFO: Generating virtual matrix element with MadLoop for process: u u~ > h
u u~ QCD=0 QED<=3 [ all = QCD ] (1 / 1)
WARNING: Some loop diagrams contributing to this process are discarded
because they are not pure (QCD)-perturbation.
Make sure you did not want to include them.
WARNING:
    The user-defined loop diagrams filter is turned on and discarded 24
loops.
INFO: Generated 1 subprocesses with 24 real emission diagrams, 2 born
diagrams and 12 virtual diagrams

which is not the same as yours since you seem not to have filtered any
loop. Let me copy here the exact start of the fonction user_filter that
you should use (i.e. where you should place the filter I gave you). So make
sure you indeed get exactly 12 diagrams for this subprocess (4 triangles, 8
pentagons).

Notice that we plan on simplifying the implementation of a custom diagram
filtering for the user in future MG5aMC versions.

    def user_filter(self, model, structs, filter=None):
        """ User-defined user-filter. By default it is not called, but the
expert
        user can turn it on and code here is own filter. Some default
examples
        are provided here.
        The tagging of the loop diagrams must be performed before using
this
        user loop filter"""

        # By default the user filter does nothing if filter is not set,
        # if you want to turn it on and edit it by hand, then set the
        # variable edit_filter_manually to True
        edit_filter_manually = True
        if not edit_filter_manually and filter in [None,'None']:
            return
        if isinstance(filter,str) and filter.lower() == 'true':
            edit_filter_manually = True
            filter=None

        if filter not in [None,'None']:
            filter_func = LoopAmplitude.get_loop_filter(filter)
        else:
            filter_func = None

        new_diag_selection = base_objects.DiagramList()
        discarded_diags = base_objects.DiagramList()
        i=0
        for diag in self['loop_diagrams']:
            if diag.get('tag')==[]:
                raise MadGraph5Error, "Before using the user_filter, please
"+\
                       "make sure that the loop diagrams have been tagged
first."
            valid_diag = True
            i=i+1

            # Apply the custom filter specified if any
            if filter_func:
                try:
                    valid_diag = filter_func(diag, structs, model, i)
                except Exception as e:
                    raise InvalidCmd("The user-defined filter '%s' did
not"%filter+
                                 " returned the following error:\n >
%s"%str(e))

            # Select only the pentagon QCD correction to the VBF, and kick
out the other genuine EW corrections.
            if any(abs(pdg) in [22,23,24,25] for pdg in
diag.get_loop_lines_pdgs()) and len(diag.get_loop_lines_pdgs())!=5:
                valid_diag = False

            [...]

Finally, notice that running a single partonic subprocess at NLO is of
course online fine for this test that pole cancels. But you should not
expect any physical result at NLO if you don't use the multiparticle labels
'p' and 'j' and instead specify the quark flavors.

Let me know if this works this time.

On Thu, Aug 25, 2016 at 5:02 AM, Abdualazem <
<email address hidden>> wrote:

> Question #356087 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/356087
>
> Abdualazem gave more information on the question:
>
> Hi Valentin,
>
> Thank you.
>
> ./bin/mg5_aMC
> MG5_aMC> set gauge Feynman
> MG5_aMC> import model loop_sm-no_b_mass
> MG5_aMC> generate u u~ > h u u~ QCD=0 [QCD]
> MG5_aMC> display diagrams
>
> everything is fine up to the display diagrams in which I can see the QCD
> triangles along with
> the QCD pentagons. But the problem comes when I launch it. I got this"
>
> "INFO: Result for test_MC:
> INFO: Passed.
> INFO: Result for check_poles:
> Error detected in "launch auto "
> write debug file /afs/cern.ch/work/a/amoohamm/
> private/MG/MG5_aMC_v2_4_3/uu_test/run_01_tag_1_debug.log
> If you need help with this issue please contact us on
> https://answers.launchpad.net/mg5amcnlo
> aMCatNLOError : Poles do not cancel, run cannot continue
> quit
> INFO:"
>
> This was for the specific test you showed me. I think it's worthy to show
> you snapshot from the beginning:
>
>
> "MG5_aMC>import model loop_sm-no_b_mass
> INFO: Restrict model loop_sm with file models/loop_sm/restrict_no_b_mass.dat
> .
> INFO: Run "set stdout_level DEBUG" before import for more information.
> INFO: Change particles name to pass to MG5 convention
> Pass the definition of 'j' and 'p' to 5 flavour scheme.
> Kept definitions of multiparticles l- / vl / l+ / vl~ unchanged
> Defined multiparticle all = g gh gh~ d u s c b d~ u~ s~ c~ b~ a ve vm vt
> e- mu- ve~ vm~ vt~ e+ mu+ t t~ z w+ h g0 g+ w- g- ta- ta+
> MG5_aMC>generate u u~ > h u u~ QCD=0 [QCD]
> WARNING: Process: u u~ > h u u~ QCD=0 [ all = QCD ] can have real emission
> processes which are not finite.
> To avoid this, please use multiparticles when generating the process and
> be sure to include all the following particles in the multiparticle
> definition:
> g, b, c, s, u, d, d~, u~, s~, c~, b~
> INFO: Generating FKS-subtracted matrix elements for born process: u u~ > h
> u u~ QCD=0 [ all = QCD ] (1 / 1)
> INFO: Generating virtual matrix elements using MadLoop:
> INFO: Generating virtual matrix element with MadLoop for process: u u~ > h
> u u~ QED<=3 QCD=0 [ all = QCD ] (1 / 1)
> WARNING: Some loop diagrams contributing to this process are discarded
> because they are not pure (QCD)-perturbation.
> Make sure you did not want to include them.
> WARNING:
> The user-defined loop diagrams filter is turned on and discarded 0
> loops.
> INFO: Generated 1 subprocesses with 24 real emission diagrams, 2 born
> diagrams and 36 virtual diagrams
> MG5_aMC>display diagrams
> Drawing Process: u u~ > h u u~ g WEIGHTED<=7 QED<=3 QCD<=1 [ all = QCD ]
> Wrote file /tmp/diagrams_0_uux_huuxg.eps
> open /tmp/diagrams_0_uux_huuxg.eps
> Drawing Process: g u~ > h u u~ u~ WEIGHTED<=7 QED<=3 QCD<=1 [ all = QCD ]
> Wrote file /tmp/diagrams_0_gux_huuxux.eps
> open /tmp/diagrams_0_gux_huuxux.eps
> Drawing Process: u g > h u u u~ WEIGHTED<=7 QED<=3 QCD<=1 [ all = QCD ]
> Wrote file /tmp/diagrams_0_ug_huuux.eps
> open /tmp/diagrams_0_ug_huuux.eps
> time to draw 0.0425329208374
> Drawing Process: u u~ > h u u~ QCD=0 [ all = QCD ]
> Wrote file /tmp/diagrams_0_uux_huux.eps
> open /tmp/diagrams_0_uux_huux.eps
> time to draw 0.00540781021118
> Drawing Process: u u~ > h u u~ WEIGHTED<=6 QED<=3 QCD=0 [ all = QCD ]
> Wrote file /tmp/diagrams_0_uux_huux.eps
> open /tmp/diagrams_0_uux_huux.eps
> time to draw 0.0325589179993
> MG5_aMC>
> "
>
>
> Cheers,
>
> abdualazem.
>
>
> ________________________________________
> From: <email address hidden> [<email address hidden>] on behalf of Valentin
> Hirschi [<email address hidden>]
> Sent: 24 August 2016 18:54
> To: Abdualazem Fadol Mohammed
> Subject: Re: [Question #356087]: problem with VBF [QCD] for the Higgs
> production
>
> Your question #356087 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/356087
>
> Valentin Hirschi posted a new comment:
> Dear Abdualazem,
>
> You are right, I had a typo in my message and the file you are supposed
> to modify is indeed
>
> madgraph/loop/loop_diagram_generation.py
>
> Now you should try with the 'loop_sm-no_b_mass' model and specify the
> QCD=0 Born amplitude order in your process definition.
> You can test the setup before running the full thing with:
>
> ./bin/mg5_aMC
> MG5_aMC> set gauge Feynman
> MG5_aMC> import model loop_sm-no_b_mass
> MG5_aMC> generate u u~ > h u u~ QCD=0 [QCD]
> MG5_aMC> display diagrams
>
> And make sure you have the expected loops (the QCD triangles along with
> the QCD pentagons).
>
> Then only try the full run and you should have the poles cancelling. Let
> me know if you don't find the correct loops or if the poles don't cancel
> with the setup above (along with the modifications I mentioned in my
> earlier message).
>
> --
> You received this question notification because you asked the question.
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
>

--
Valentin

Dear Valentin and Olivier,

It's now working fine for the process p p > h j j [QCD] and p p > h j j $$ w+ w- z.

Thank you all.

Cheers,

abdualazem.

________________________________________
From: <email address hidden> [<email address hidden>] on behalf of Valentin Hirschi [<email address hidden>]
Sent: 26 August 2016 17:47
To: Abdualazem Fadol Mohammed
Subject: Re: [Question #356087]: problem with VBF [QCD] for the Higgs production

Your question #356087 on MadGraph5_aMC@NLO changed:
https://answers.launchpad.net/mg5amcnlo/+question/356087

    Status: Open => Answered

Valentin Hirschi proposed the following answer:
I forgot that you must also worth within the complex mass scheme, otherwise
the W-boson width will be included in the real-emission diagrams but not in
the corresponding pentagon that should cancel its IR divergence.

You should therefore do:

./bin/mg5_aMC
MG5_aMC> set gauge Feynman
MG5_aMC> set complex_mass_scheme
MG5_aMC> import model loop_sm-no_b_mass
MG5_aMC> generate u u~ > h u u~ QCD=0 [QCD]
(MG5_aMC> display diagrams)
MG5_aMC> launch

then the pole should cancel (I just double-checked).

However, you must get the following message:

INFO: Generating virtual matrix element with MadLoop for process: u u~ > h
u u~ QCD=0 QED<=3 [ all = QCD ] (1 / 1)
WARNING: Some loop diagrams contributing to this process are discarded
because they are not pure (QCD)-perturbation.
Make sure you did not want to include them.
WARNING:
    The user-defined loop diagrams filter is turned on and discarded 24
loops.
INFO: Generated 1 subprocesses with 24 real emission diagrams, 2 born
diagrams and 12 virtual diagrams

which is not the same as yours since you seem not to have filtered any
loop. Let me copy here the exact start of the fonction user_filter that
you should use (i.e. where you should place the filter I gave you). So make
sure you indeed get exactly 12 diagrams for this subprocess (4 triangles, 8
pentagons).

Notice that we plan on simplifying the implementation of a custom diagram
filtering for the user in future MG5aMC versions.

    def user_filter(self, model, structs, filter=None):
        """ User-defined user-filter. By default it is not called, but the
expert
        user can turn it on and code here is own filter. Some default
examples
        are provided here.
        The tagging of the loop diagrams must be performed before using
this
        user loop filter"""

        # By default the user filter does nothing if filter is not set,
        # if you want to turn it on and edit it by hand, then set the
        # variable edit_filter_manually to True
        edit_filter_manually = True
        if not edit_filter_manually and filter in [None,'None']:
            return
        if isinstance(filter,str) and filter.lower() == 'true':
            edit_filter_manually = True
            filter=None

        if filter not in [None,'None']:
            filter_func = LoopAmplitude.get_loop_filter(filter)
        else:
            filter_func = None

        new_diag_selection = base_objects.DiagramList()
        discarded_diags = base_objects.DiagramList()
        i=0
        for diag in self['loop_diagrams']:
            if diag.get('tag')==[]:
                raise MadGraph5Error, "Before using the user_filter, please
"+\
                       "make sure that the loop diagrams have been tagged
first."
            valid_diag = True
            i=i+1

            # Apply the custom filter specified if any
            if filter_func:
                try:
                    valid_diag = filter_func(diag, structs, model, i)
                except Exception as e:
                    raise InvalidCmd("The user-defined filter '%s' did
not"%filter+
                                 " returned the following error:\n >
%s"%str(e))

            # Select only the pentagon QCD correction to the VBF, and kick
out the other genuine EW corrections.
            if any(abs(pdg) in [22,23,24,25] for pdg in
diag.get_loop_lines_pdgs()) and len(diag.get_loop_lines_pdgs())!=5:
                valid_diag = False

            [...]

Finally, notice that running a single partonic subprocess at NLO is of
course online fine for this test that pole cancels. But you should not
expect any physical result at NLO if you don't use the multiparticle labels
'p' and 'j' and instead specify the quark flavors.

Let me know if this works this time.

On Thu, Aug 25, 2016 at 5:02 AM, Abdualazem <
<email address hidden>> wrote:

> Question #356087 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/356087
>
> Abdualazem gave more information on the question:
>
> Hi Valentin,
>
> Thank you.
>
> ./bin/mg5_aMC
> MG5_aMC> set gauge Feynman
> MG5_aMC> import model loop_sm-no_b_mass
> MG5_aMC> generate u u~ > h u u~ QCD=0 [QCD]
> MG5_aMC> display diagrams
>
> everything is fine up to the display diagrams in which I can see the QCD
> triangles along with
> the QCD pentagons. But the problem comes when I launch it. I got this"
>
> "INFO: Result for test_MC:
> INFO: Passed.
> INFO: Result for check_poles:
> Error detected in "launch auto "
> write debug file /afs/cern.ch/work/a/amoohamm/
> private/MG/MG5_aMC_v2_4_3/uu_test/run_01_tag_1_debug.log
> If you need help with this issue please contact us on
> https://answers.launchpad.net/mg5amcnlo
> aMCatNLOError : Poles do not cancel, run cannot continue
> quit
> INFO:"
>
> This was for the specific test you showed me. I think it's worthy to show
> you snapshot from the beginning:
>
>
> "MG5_aMC>import model loop_sm-no_b_mass
> INFO: Restrict model loop_sm with file models/loop_sm/restrict_no_b_mass.dat
> .
> INFO: Run "set stdout_level DEBUG" before import for more information.
> INFO: Change particles name to pass to MG5 convention
> Pass the definition of 'j' and 'p' to 5 flavour scheme.
> Kept definitions of multiparticles l- / vl / l+ / vl~ unchanged
> Defined multiparticle all = g gh gh~ d u s c b d~ u~ s~ c~ b~ a ve vm vt
> e- mu- ve~ vm~ vt~ e+ mu+ t t~ z w+ h g0 g+ w- g- ta- ta+
> MG5_aMC>generate u u~ > h u u~ QCD=0 [QCD]
> WARNING: Process: u u~ > h u u~ QCD=0 [ all = QCD ] can have real emission
> processes which are not finite.
> To avoid this, please use multiparticles when generating the process and
> be sure to include all the following particles in the multiparticle
> definition:
> g, b, c, s, u, d, d~, u~, s~, c~, b~
> INFO: Generating FKS-subtracted matrix elements for born process: u u~ > h
> u u~ QCD=0 [ all = QCD ] (1 / 1)
> INFO: Generating virtual matrix elements using MadLoop:
> INFO: Generating virtual matrix element with MadLoop for process: u u~ > h
> u u~ QED<=3 QCD=0 [ all = QCD ] (1 / 1)
> WARNING: Some loop diagrams contributing to this process are discarded
> because they are not pure (QCD)-perturbation.
> Make sure you did not want to include them.
> WARNING:
> The user-defined loop diagrams filter is turned on and discarded 0
> loops.
> INFO: Generated 1 subprocesses with 24 real emission diagrams, 2 born
> diagrams and 36 virtual diagrams
> MG5_aMC>display diagrams
> Drawing Process: u u~ > h u u~ g WEIGHTED<=7 QED<=3 QCD<=1 [ all = QCD ]
> Wrote file /tmp/diagrams_0_uux_huuxg.eps
> open /tmp/diagrams_0_uux_huuxg.eps
> Drawing Process: g u~ > h u u~ u~ WEIGHTED<=7 QED<=3 QCD<=1 [ all = QCD ]
> Wrote file /tmp/diagrams_0_gux_huuxux.eps
> open /tmp/diagrams_0_gux_huuxux.eps
> Drawing Process: u g > h u u u~ WEIGHTED<=7 QED<=3 QCD<=1 [ all = QCD ]
> Wrote file /tmp/diagrams_0_ug_huuux.eps
> open /tmp/diagrams_0_ug_huuux.eps
> time to draw 0.0425329208374
> Drawing Process: u u~ > h u u~ QCD=0 [ all = QCD ]
> Wrote file /tmp/diagrams_0_uux_huux.eps
> open /tmp/diagrams_0_uux_huux.eps
> time to draw 0.00540781021118
> Drawing Process: u u~ > h u u~ WEIGHTED<=6 QED<=3 QCD=0 [ all = QCD ]
> Wrote file /tmp/diagrams_0_uux_huux.eps
> open /tmp/diagrams_0_uux_huux.eps
> time to draw 0.0325589179993
> MG5_aMC>
> "
>
>
> Cheers,
>
> abdualazem.
>
>
> ________________________________________
> From: <email address hidden> [<email address hidden>] on behalf of Valentin
> Hirschi [<email address hidden>]
> Sent: 24 August 2016 18:54
> To: Abdualazem Fadol Mohammed
> Subject: Re: [Question #356087]: problem with VBF [QCD] for the Higgs
> production
>
> Your question #356087 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/356087
>
> Valentin Hirschi posted a new comment:
> Dear Abdualazem,
>
> You are right, I had a typo in my message and the file you are supposed
> to modify is indeed
>
> madgraph/loop/loop_diagram_generation.py
>
> Now you should try with the 'loop_sm-no_b_mass' model and specify the
> QCD=0 Born amplitude order in your process definition.
> You can test the setup before running the full thing with:
>
> ./bin/mg5_aMC
> MG5_aMC> set gauge Feynman
> MG5_aMC> import model loop_sm-no_b_mass
> MG5_aMC> generate u u~ > h u u~ QCD=0 [QCD]
> MG5_aMC> display diagrams
>
> And make sure you have the expected loops (the QCD triangles along with
> the QCD pentagons).
>
> Then only try the full run and you should have the poles cancelling. Let
> me know if you don't find the correct loops or if the poles don't cancel
> with the setup above (along with the modifications I mentioned in my
> earlier message).
>
> --
> You received this question notification because you asked the question.
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
>

--
Valentin

--
If this answers your question, please go to the following page to let us
know that it is solved:
https://answers.launchpad.net/mg5amcnlo/+question/356087/+confirm?answer_id=8

If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https://answers.launchpad.net/mg5amcnlo/+question/356087

You received this question notification because you asked the question.

Dear Abdualazem,

For future reference, can you confirm that you managed to run the process using both of the solution I suggested for the IR pole cancellation failing:

1) Bypass the check
2) Compute the missing pentagon loops.

Thanks,

Thanks Olivier Mattelaer, that solved my question.