This page describes the technical modifications necessary to compute Loop-Induced processes times tree-level diagrams with MadEvent and the Loop-Induced module of MG5aMC. Notice that there is no official support for such computation in MG5aMC as of now, so that the procedure below must be performed with care and should be cross-checks in some limits before as we cannot guarantee the same level of reliability as with other MG5aMC functionalities. It was however already successfully used and tested for g g > h > t t~ g.

You can try to adapt this recipe to the latest version of MG5aMC or use directly v2.3.3 for which you should have a one-to-one correspondance with my intstructions.

---

a) First download the latest version of MG5_aMC, either using the tarball link:

​https://launchpad.net/mg5amcnlo/2.0/2.3.0/+download/MG5_aMC_v2.3.3.tar.gz

b) Untar the 'special_loop_sm' UFO loop model file attached to this email and place it in the 'model' directory of your MG distribution. Notice that this model is a simple copy of the default 'loop_sm' model but contains modifications in the file 'CT_vertices' which now contains special 'UVtree' counterterms, which are precisely those which will emulate the QCD background you are interfering against. Have a look at them; they are placed under the comment:

#########################################################################
# Fake UVCT vertices for loop-induced and tree interference computation #
#########################################################################

Depending on the tree-level diagrams you will want to interfere against you might need to place additional copies of the regular tree-level vertices here, with the type UVTree and involving couplings defined in 'CT_couplings.py' with the coupling_order type 'BKGQCD'. You would for example need to add copies of the electroweak vertices for example if they played a role in your tree-level background. In your case however, the tree-level diags are g g > t t~, so this model should be fine.

c) Bring the following changes to the MG5_aMC python source code:

c.1) Anywhere in the class 'LoopUVCTDiagram' of the file '<MG_root_path>/madgraph/loop/loop_base_objects.py', add the following two functions:

    def get_contracted_loop_diagram(self, model, struct_rep=None):
        return copy.copy(self)    
    def get_contracted_loop_diagram_without_tag(self, struct_rep=None):
        return copy.copy(self)

c.2) In the file '<MG_root_path>/madgraph/loop/loop_diagram_generation.py' change the folllowing:

c.2.i) Around line 740, change:

        if self['process']['has_born']:
            self.set_Born_CT()

into

        if True:
            self.set_Born_CT()

c.2.ii) Around line 1190, change

        UVCTsuccessful, UVCTdiagrams = \
          super(LoopAmplitude, self).generate_diagrams(True)

into

        # Back up of the original process characteristics
        bu = copy.copy(self['process']['required_s_channels'])
        bu_orders = copy.copy(self['process']['orders'])
        self['process']['required_s_channels'] = []
        for order in self['process']['model'].get_coupling_orders():
            self['process']['orders'][order] = 0
        self['process']['orders']['UVCT_SPECIAL'] = 999
        # Specify here the coupling orders desired for the background. By default, all.
        self['process']['orders']['BKGQCD'] = 999
        UVCTsuccessful, UVCTdiagrams = \
          super(LoopAmplitude, self).generate_diagrams(True)
        # Restore backed up properties
        self['process']['required_s_channels'] = copy.copy(bu)        
        for order, value in bu_orders.items():
            self['process']['orders'][order] = value

(Note that you can add above further modifications of selfprocessorders and selfprocessrequired_s_channels to have a finer selection of your tree-level interfering diagrams, but for your purposes that shouldn't be needed. Notice that thanks to the line selfprocessrequired_s_channels = [] the '> h >' constraint on the original process definition will not apply to the interfering tree-level diagrams.)

c.2.iii) Around line 1212, change

            if UVCTdiag.get_order('UVCT_SPECIAL')==1:

into

            if True:

c.3) Around line 1900 of the file '<MG_root_path>/madgraph/loop/loop_helas_objects.py' change:

            ref_orders = [lao[0] for lao in loop_orders+ct_amp_orders]

into

            ref_orders = [lao[0] for lao in loop_orders+ct_amp_orders+uvct_amp_orders]

d) Now that all the necessary modifications have been performed, you should be able to run the code for simulation of the loop-induced vs tree interference as follows:

d.1) First start the interface by running the script './bin/mg5' from within the directory <MG_root_path> d.2) Whenever you plan on running event generation (i.e. not necessary when doing MadLoop standalone), make sure that the grouping of subprocess is disabled, with

    MG5_aMC>set group_subprocesses False

d.3) then load the model with

    MG5_aMC>import model special_loop_sm

This loads the special model for this sort of computation (with the fake 'background' UVCT vertices). (Here I show an example for the process g g > h > t t~ g, so that it is clear that it is more general that what you wanted to do in the first place, namely g g > h > t t~)

d.4) Generate the process in one of the two following ways (feel free to change the process definition at will):

If you want to run MadLoop in standalone to evaluate this interference for local phase-space points for cross-checks, run:

    MG5_aMC>generate g g > h > t t~ g [virt=QCD BKGQCD]

(You will automatically be able to see the individual contribution of the signal squared, interference term and background squared) Instead, for the generation of the process which will be output with MadEvent to generate events, use:

    MG5_aMC>generate g g > h > t t~ g [noborn=QCD BKGQCD] BKGQCD^2==3

for the generation of the process which will be output with MadEvent to generate events for this interference only.

Notice that in the second syntax, you can substitute the initial state gluons with 'p' and the final-state ones with 'j' to include the quark channels as well. This works.

d.5) You can now output the process to a directory of a chosen name 'MyOutputDirName'

MG5_aMC>output MyOutputDirName

d.6) And finally launch it with

MG5_aMC>launch

or alternatively, you can specify the directory name if you are returning to the interface and want to launch an existing output:

MG5_aMC>launch MyOutputDirName

d.7) MadGraph5_aMC@NLO will then ask you questions related to the details of either the MadLoop standalone run you are doing or the event generation run.