 
<chapter name="MLM jet merging"> 
 
<h2>MLM jet merging</h2> 
 
This manual page describes the parton-jet matching interfaces for 
PYTHIA8. In this approach, usually referred to as MLM merging 
<ref>Man02, Man07</ref>, the final jets after parton-shower evolution 
and jet clustering are matched to the original partons. The event is 
accepted if a reasonable match is found, and rejected if not. The 
rejection step in an approximate way introduces a Sudakov form factor 
on to the hard processes. Notably the parton shower should not generate 
an emission that would doublecount hard activity already included in 
the matrix-element description. Within this general ansatz, different 
technical solutions can be adopted. We provide two alternatives, one 
based on the algorithm used in ALPGEN <ref>Man03</ref>, and another on 
the one used in Madgraph <ref>Alw11</ref>, both reimplemented from 
scratch here. The main points of these two algorithms are outlined 
further down on this page. 
 
<p/>We also allow for two alternative sources of external events, 
one in the ALPGEN native format and one in the Madgraph LHEF-based one. 
All four combinations of input format and scheme are 
implemented. In the following it is therefore important to keep 
the two aspects apart, whenever the ALPGEN and Madgraph labels 
are used. 
 
<p/>Currently all the files of interest are located in the 
<code>include/Pythia8Plugins/</code> subdirectory: 
<ul> 
<li><code>JetMatching.h</code> contains the machinery for the 
parton-jet matching, in the two <code>JetMatchingAlpgen</code> 
and <code>JetMatchingMadgraph</code> classes. 
</li> 
<li><code>GeneratorInput.h</code> contains three classes for the 
reading of ALPGEN event and parameter files, and one for the reading 
of Madgraph parameters. 
</li> 
<li><code>CombineMatchingInput.h</code> contains three classes that 
combine the reading of events with the merging of them. 
</li> 
<li> 
<code>main32.cc, main32.cmnd</code> : a sample main program and card 
file showing the usage of the previous files/classes. 
</li> 
</ul> 
 
<h3>Event input source</h3> 
 
External sources of partons are used in the parton-jet matching 
process. The source of the partons has been separated from the 
implementation of the algorithm. By default, PYTHIA8 
contains a machinery to process 
<aloc href="LHEF">Les Houches Event Files</aloc> (LHEFs) 
Madgraph5 adheres to this format, but also contains some further 
non-standardized information that can be used. The parsing of the native 
ALPGEN file format is described on the 
<aloc href="AlpgenEventInterface">Alpgen Event Interface</aloc> page. 
 
<p/>Commonly, the source of external partons also contains information 
about how a particular type of algorithm should be employed. 
This information is handled by the <code>AlpgenPar</code> class for 
ALPGEN files, and <code>MadgraphPar</code> for LHEFs. 
The user can choose to set default merging parameters using the 
<code><aloc href="AlpgenEventInterface">Alpgen:setMLM</aloc></code> 
flag for ALPGEN files. For LHEFs, instead, the setting of default 
parameters is controlled with the <code>JetMatching:setMad</code> flag: 
 
<flag name="JetMatching:setMad" default="on"> 
When enabled, the merging parameters are set according to the values 
in the LHEF header. Specifically, the header must set the 
<code>ickkw</code>, <code>xqcut</code>, <code>maxjetflavor</code> 
and <code>alpsfact</code> values, and <code>ickkw</code> must be nonzero. 
Note that these labels are Madgraph-specific. For other programs 
with LHEF output, or for Madgraph files lacking this information, 
these parameters should be set by the user (or one can rely on the 
default values). The following parameters (described below) must then 
be specified: 
<ul> 
<li> <code>JetMatching:doMerge = ickkw</code>, </li> 
<li> <code>JetMatching:qCut = xqcut</code>, </li> 
<li> <code>JetMatching:nQmatch = maxjetflavor</code>, </li> 
<li> <code>JetMatching:clFact = alpsfact. </code> </li> 
</ul> 
With this flag on, the values from the LHEF for these parameters take 
precedence over other values. 
</flag> 
 
<h3> Jet Matching parameters </h3> 
 
A class <code>JetMatching</code>, derived from <code>UserHooks</code>, is 
used to define the basic structure of a parton-jet matching algorithm. 
Two versions are implemented here, based on the FORTRAN code provided 
by the ALPGEN and Madgraph packages, respectively: 
<code>JetMatchingAlpgen</code> and <code>JetMatchingMadgraph</code>. 
The merging parameters are defined with the <code>JetMatching:*</code> 
keyword. 
 
<h4> Scheme and Usage </h4> 
 
<flag name="JetMatching:merge" default="off"> 
Master switch to activate parton-jet matching. 
When off, all external events are accepted (unless they 
are rejected due to weighting or event processing problems). 
</flag> 
 
<modepick name="JetMatching:scheme" default="1" min="1" max="2"> 
The parton-jet MLM-style merging scheme. 
<option value="1"> The one inspired by the Madgraph scheme, 
here implemented in the <code>JetMatchingMadgraph</code> class.</option> 
<option value="2"> The one inspired by the ALPGEN scheme, 
here implemented in the <code>JetMatchingAlpgen</code> class.</option> 
</modepick> 
 
<h4>Jet algorithm</h4> 
 
The choice of jet algorithm and associated parameters can be adjusted with 
the settings below. The PYTHIA8 internal <code>CellJet</code> and 
<code>SlowJet</code> routines are used for jet finding.  See the 
<aloc href="EventAnalysis">Event Analysis</aloc> page for more details. 
 
<modepick name="JetMatching:jetAlgorithm" default="1" min="1" max="2"> 
The choice of jet algorithm to use when merging against hard partons. 
Currently, only <code>SlowJet</code> with the k<sub>T</sub> algorithm (and 
<code>useStandardR = false</code>) is supported for Madgraph-style 
merging, while there is full freedom for the ALPGEN-style merging. 
<option value="1">The <code>CellJet</code> cone algorithm.</option> 
<option value="2">The <code>SlowJet</code> clustering algorithm.</option> 
</modepick> 
 
<modepick name="JetMatching:slowJetPower" default="-1" min="-1" max="1"> 
The power to use in the <code>SlowJet</code> algorithm. 
<option value="-1">The anti-k<sub>T</sub> algorithm.</option> 
<option value="0">The Cambridge/Aachen algorithm.</option> 
<option value="1">The k<sub>T</sub> algorithm.</option> 
</modepick> 
 
<modepick name="JetMatching:nEta" default="100" min="50"> 
Specific to the <code>CellJet</code> algorithm, the number of bins 
in pseudorapidity. 
</modepick> 
 
<modepick name="JetMatching:nPhi" default="60" min="30"> 
Specific to the <code>CellJet</code> algorithm, the number of bins in phi. 
</modepick> 
 
<parm name="JetMatching:eTseed" default="1.5" min="0.0"> 
Specific to the <code>CellJet</code> algorithm, the minimum <ei>eT</ei> 
for a cell to be acceptable as the trial center of a jet. 
</parm> 
 
<parm name="JetMatching:eTthreshold" default="0.1"> 
Specific to the <code>CellJet</code> algorithm, cells with 
<ei>eT &lt; eTthreshold</ei> are completely neglected by the jet algorithm. 
</parm> 
 
<h4>Merging parameters</h4> 
 
The following options are the three main parameters for the merging 
procedure. Although here they are in principle free parameters, they should 
be heavily influenced by the hard process generation cuts. 
These values can be set automatically based on the information in the 
ALPGEN file or LHEF. 
 
<parm name="JetMatching:eTjetMin" default="20.0" min="5.0"> 
For the <code>CellJet</code> algorithm, this gives the minimum transverse 
energy inside a cone for a jet to be accepted. For the <code>SlowJet</code> 
algorithm, this is instead the minimum transverse momentum required for a 
cluster to be accepted as a jet. For the Madgraph scheme, this 
parameter should match the <code>qCut</code> parameter described later. 
</parm> 
 
<parm name="JetMatching:coneRadius" default="0.7" min="0.1"> 
For the <code>CellJet</code> algorithm, this gives the size of the cone 
in <ei>(eta, phi)</ei> space drawn around the geometric center of the jet. 
For the <code>SlowJet</code> algorithm, this gives the <ei>R</ei> parameter. 
</parm> 
 
<parm name="JetMatching:etaJetMax" default="2.5" min="0.1"> 
For both jet algorithms, this defines the maximum pseudorapidity that 
the detector is assumed to cover. In this context, however, it is tied 
to the phase space region in which partons have been generated. 
For the Alpgen scheme, particles within 
<ei>etaJetMax + coneRadius</ei> are passed to the jet algorithm, 
with only jets within <ei>etaJetMax</ei> retained in the merging. 
For the Madgraph scheme, only particles within <ei>etaJetMax</ei> 
are used. 
</parm> 
 
<h4>Exclusive mode</h4> 
 
The following settings determine whether clustered jets which do not 
match an original hard parton are allowed. They are typically permitted 
in the highest jet multiplicity sample, where the parton shower may 
produce extra hard jets, without risk of double counting. Any 
extra jet produced by the shower must be softer than any matched light 
jet, or else the event is vetoed. 
 
<modepick name="JetMatching:exclusive" default="2" min="0" max="2"> 
Exclusive or inclusive merging. 
<option value="0"> 
The merging is run in inclusive mode. All partons must match jets, but 
additional jets are allowed, provided they are not harder than the 
matched jets. 
</option> 
<option value="1"> 
The merging is run in exclusive mode.  All partons must match jets, 
and no additional jets are allowed. 
</option> 
<option value="2"> 
If <ei>nJet &lt; nJetMax</ei>, then the merging is run in exclusive 
mode, otherwise it is run in inclusive mode. For the Madgraph scheme, 
this is checked on an event-by-event basis, which is useful when an LHEF 
contains a "soup" of partonic multiplicities. 
If <ei>nJetMax &lt; 0</ei> or <ei>nJet &lt; 0</ei>, then the 
algorithm defaults to exclusive mode. 
</option> 
</modepick> 
 
<modepick name="JetMatching:nJet" default="-1" min="-1"> 
When <code>JetMatching:exclusive = 2</code>, <ei>nJet</ei> indicates 
the minimum number of additional light jets in the incoming process. 
This value may be set automatically. 
</modepick> 
 
<modepick name="JetMatching:nJetMax" default="-1" min="-1"> 
When <code>JetMatching:exclusive = 2</code>, <ei>nJetMax</ei> is used to 
indicate the maximum number of jets that will be matched. 
</modepick> 
 
<h4>Jet matching</h4> 
 
The following parameters control the criteria for matching a clustered jet 
to a hard parton. 
 
<modepick name="JetMatching:jetAllow" default="1" min="1" max="2"> 
Controls which particles are clustered by the jet algorithm. 
<option value="1"> 
This option explicitly disallows top quarks, leptons and photons. All other 
particle types are passed to the jet algorithm. 
</option> 
<option value="2"> 
No extra particles are disallowed. 
</option> 
</modepick> 
 
<h3> Alpgen-specific parameters </h3> 
 
<modepick name="JetMatching:jetMatch" default="1" min="1" max="2"> 
Criteria for matching a clustered jet to a parton. 
<option value="1"> 
This option can be used with both the <code>CellJet</code> and 
<code>SlowJet</code> algorithms. The <ei>delta R</ei> between each parton 
and jet is taken, and the minimal value compared against 
<ei>coneMatchLight * coneRadius</ei> for light jets or 
<ei>coneMatchHeavy * coneRadiusHeavy</ei> for heavy jets. 
Note that by default <ei>coneRadiusHeavy = coneRadius</ei>, see below. 
If below this value, the parton and jet are considered to match. 
With <code>CellJet</code>, the <ei>delta R</ei> measure is in 
<ei>(eta, phi)</ei>, while with <code>SlowJet</code> it is in 
<ei>(y, phi)</ei>. 
</option> 
<option value="2"> 
This option can only be used with the <code>SlowJet</code> algorithm. 
The hard partons are inserted into the parton level event as "ghost" 
particles, but at the correct <ei>(y, phi)</ei> position. If this 
particle is then clustered into a jet, it is considered a match. 
</option> 
</modepick> 
 
<parm name="JetMatching:coneMatchLight" default="1.5" min="0.1"> 
The <ei>coneMatchLight</ei> parameter used when 
<code>JetMatching:jetMatch = 1</code>. 
</parm> 
 
<parm name="JetMatching:coneRadiusHeavy" default="-1.0"> 
The <ei>coneRadiusHeavy</ei> parameter used when 
<code>JetMatching:jetMatch = 1</code>. When assigned a negative value, 
the value of <code>JetMatching:coneRadius</code> is used. 
</parm> 
 
<parm name="JetMatching:coneMatchHeavy" default="1.0" min="0.1"> 
The <ei>coneMatchHeavy</ei> parameter used when 
<code>JetMatching:jetMatch = 1</code>. 
</parm> 
 
<h3>Madgraph-specific parameters </h3> 
 
<flag name="JetMatching:doShowerKt" default="off"> 
This switch changes the merging prescription to the shower-kT scheme 
outlined in <ref>Alw08</ref>. This scheme differs from "classical" MLM jet 
merging with respect to when the matching veto is checked. The shower-kT 
scheme considers already immediately after the first shower emission if an 
event should be discarded. 
</flag> 
 
<parm name="JetMatching:qCut" default="10.0" min="0.0"> 
k<sub>T</sub> scale for merging shower products into jets. 
</parm> 
 
<modepick name="JetMatching:nQmatch" default="5" min="3" max="6"> 
Controls the treatment of heavy quarks. 
<option value="5"> 
All quarks (except top) are treated as light quarks for matching. 
</option> 
<option value="4"> 
Bottom quarks are treated separately.  Currently, they are unmatched. 
</option> 
</modepick> 
 
<parm name="JetMatching:clFact" default="1.0"> 
The <ei>clFact</ei> parameter determines how jet-to parton matching 
is done. A match is defined as a squared cluster scale that equals: 
<br/><ei>|clFact| * qCut</ei> for inclusive mode, 
<br/><ei>|clFact| * max(qCut,min(p<sub>T</sub>(parton)))</ei> 
for exclusive mode, <ei>clFact</ei> &ge; 0, or 
<br/><ei>|clFact| * min(k<sub>T</sub>(parton))</ei> for exclusive mode, 
<ei>clFact</ei> &lt; 0. 
</parm> 
 
<flag name="JetMatching:doVeto" default="on"> 
If turned off, then no jet matching veto will be applied internally in Pythia. 
Instead, it is assumed that the (expert) user enforces all necessary vetoes 
externally by some other means. Do not change the default value unless 
you are an expert in MLM jet matching and want to use your own code 
to perform the necessary vetoes. 
</flag> 
 
<p/> 
A preliminary implementation of the FxFx prescription for combining multiple 
NLO calculations <ref>Fre12</ref> is available. We would like to stress that 
this implementation is still undergoing validation. FxFx merging with aMC@NLO 
shares most parameters with the leading-order (MadGraph-style) MLM 
prescriptions and can be activated by using the three additional settings 
below. 
 
<flag name="JetMatching:doFxFx" default="off"> 
If turned on, then FxFx merging with aMC@NLO inputs is performed. Note that 
this requires event samples that are specifically generated for this task. 
</flag> 
 
<mode name="JetMatching:nPartonsNow" default="-1"> 
The number of partons in Born-like events for the current input LHEF. If 
the current sample e.g. contains <ei>pp &rarr; e+e- + 2 partons</ei> 
Born-like configurations, and <ei>pp &rarr; e+e- + 3 partons</ei> 
Real-emission-type events, then <code>JetMatching:nPartonsNow = 2</code> 
applies. 
</mode> 
 
<parm name="JetMatching:qCutME" default="10.0"> 
The cut applied to regulate multi-jet matrix elements. Note that this cut can 
differ from the matching scale. 
</parm> 
 
<h3>Alpgen-style parton-jet merging</h3> 
 
This section describes the Alpgen-style MLM merging algorithm for PYTHIA8. 
The most common reference to the algorithm is <ref>Man02</ref>. In many 
respects, however, the implementation provided in the ALPGEN package should 
be considered the official description of the MLM merging procedure. 
Although designed primarily to work with events generated with ALPGEN, it 
can in principle also be used with events from a different source. This 
should not be done without thought, however, and it is up to the user to 
understand the details of the algorithm and the implications of using a 
different hard process generator. 
 
<p/> 
First, either the <code>CellJet</code> or <code>SlowJet</code> jet 
algorithm is chosen. Both of these algorithms have an <ei>R</ei> and 
an <ei>etaMax</ei> parameter. In addition, <code>CellJet</code> has an 
<ei>eTmin</ei> and <code>SlowJet</code> has a <ei>pTmin</ei> parameter. 
These are the primary three parameters of the merging procedure, and in 
practice are set dependent on the cuts applied to the matrix element (ME) 
generation. We stress that the merging procedure is not tied to the 
geometry of a specific physical detector, but only to the match between 
the original partons and the resulting jets, using standard jet algorithms 
in the phase space region where partons have been generated. 
 
<p/> 
ME samples with different jet multiplicities are run through the event 
generator, and the generation interrupted after parton showers have been 
applied, but before resonance decays and beam remnants have been 
processed. Note in particular that top quarks will not yet be decayed, 
which may lead to slight differences with the PYTHIA 6 interface included 
with the ALPGEN package. In what follows, the hardness measure of 
jets/partons is taken to be <ei>eT</ei> when <code>CellJet</code> 
is used and <ei>pT</ei> when <code>SlowJet</code> is used. The hard 
system (ignoring all MPI systems) is then analysed: 
<ul> 
  <li> 
    The particles in the original matrix element process are sorted into 
    light partons, heavy partons and other particles. For backwards 
    compatibility, a light parton is defined as the set <ei>(d, u, s, c, 
    b, g)</ei> with zero mass. A heavy parton is defined as the set 
    <ei>(c, b, t)</ei> with non-zero mass. 
  </li> 
  <li> 
    All particles not originating from the heavy partons or other 
    particles are passed to the jet algorithm and clustered. 
  </li> 
  <li> 
    Clustered jets are matched to the light partons in the original ME 
    process. There are two different methods which can be used: 
    <ul> 
      <li> 
        Method 1: The following is done for each parton, in order 
        of decreasing hardness. The <ei>delta R</ei> between the parton 
        and all jets is calculated and the smallest value taken. If 
        this is less than the jet <ei>R</ei> parameter, possibly 
        multiplied by a constant, the jet and parton are considered to 
        match, and the jet is removed from further consideration. 
        Note that for <code>CellJet</code> the <ei>delta R</ei> measure 
        is in <ei>(eta, phi)</ei>, while for <code>SlowJet</code>, it is 
        in <ei>(y, phi)</ei>. 
      </li> 
      <li> 
        Method 2: This method is only possible when using the 
        <code>SlowJet</code> algorithm. Before the clustering is performed, 
        extremely soft "ghost" particles are added to the event at the 
        <ei>(y, phi)</ei> coordinates of the original matrix element 
        partons. If such a particle is clustered into a jet, the parton 
        and jet are considered to match. The idea of "ghost" particles 
        was originally introduced by FastJet as a way to measure jet 
        areas <ref>Cac06</ref> and should not affect clustering with an 
        infrared-safe jet algorithm. 
      </li> 
    </ul> 
  </li> 
  <li> 
    If there is a light ME parton remaining which has not been matched 
    to a jet, then the event is vetoed. If all ME partons have been 
    matched to a jet, but there are still some extra jets remaining, 
    then two options are possible: 
    <ul> 
      <li> 
        Exclusive mode: the event is vetoed. This is typically used when 
        there are ME samples with higher jet multiplicities, which would 
        fill in the extra jets. 
      </li> 
      <li> 
        Inclusive mode: the event is retained if the extra jets are softer 
        than the softest matched jet. This is typically used when 
        there is no ME sample with higher jet multiplicity, so the parton 
        shower should be allowed to give extra jets. 
      </li> 
    </ul> 
  </li> 
  <li> 
    All particles originating from the heavy partons are passed to the 
    jet algorithm and clustered. 
  </li> 
  <li> 
    The clustered jets are again matched to the original partons, but 
    there is no requirement for a match to be present; all matched jets 
    are immediately discarded. The matching procedure is much the same 
    as for light partons, but with two differences when <ei>delta R</ei> 
    matching is used. First, a different <ei>R</ei> parameter than that 
    used by the jet algorithm may optionally be given. Second, all jets 
    that are within the given radius of the parton are matched, not 
    just the one with the smallest <ei>delta R</ei> measure. If there 
    are still extra jets remaining then in exclusive mode the event is 
    immediately vetoed, while in inclusive mode the event is retained if 
    the extra jets are softer than the softest <em>light</em> matched jet. 
  </li> 
</ul> 
 
<p/> 
Some different options are provided, specified further above in the 
parameters section. These are set so that, by default, the algorithm 
closely follows the official MLM interface provided in the ALPGEN package. 
 
<p/> 
All vetoing of events is done through the usual 
<aloc href="UserHooks">User Hooks</aloc> machinery, and is 
therefore already taken into account in the cross section. In the output 
from <code><aloc href="EventStatistics">Pythia::stat()</aloc></code>, 
the difference between the "Selected" and "Accepted" columns gives the 
number of events that have not survived the vetoing procedure. It is 
still the responsibility of the user to add together the results from 
runs with different jet multiplicities. In the simplest case, when 
ALPGEN input is used and the hard process parameters are used to guide 
the merging procedure, it is enough to set the 
<code>JetMatching:nJetMax</code> parameter. 
 
<h3>Madgraph-style parton-jet merging</h3> 
 
<p/> 
This section describes the Madgraph parton-jet merging algorithm 
for PYTHIA8. 
 
<p/> 
First, the k<sub>T</sub> jet algorithm is applied using the PYTHIA8 
<code>SlowJet</code> implementation. The <code>useStandardR = false</code> 
is used, ie. the <ei>(delta R)^2</ei> separation is defined as 
<ei>2 (cosh(delta y) - cos(delta phi))</ei> rather than the more common 
<ei>(delta y)^2 + delta phi)^2</ei>. The <ei>R</ei>, <ei>etaMax</ei>, 
and a <ei>pTmin</ei> parameters are specified. By default, <ei>R = 1</ei> 
and <ei>pTmin = qCut </ei>. It is not recommended to change these. 
These should match the algorithm parameters used in the Madgraph 
Matrix Element (ME) generation. 
 
<p/> 
ME samples with different jet multiplicities are run through the event 
generator, and the generation is interrupted after parton showers have 
been applied, but before resonance decays and beam remnants have been 
processed. In what follows, the hardness measure of jets/partons is taken 
to be <ei>k<sub>T</sub></ei> relative to <ei>qCut</ei>. 
The hard system (ignoring all MPI systems) is analyzed: 
<ul> 
  <li> 
    The hard partons in the original matrix element process, provided by 
    the LHEF, are sorted into light partons, heavy partons and other 
    particles. A heavy parton is defined by the 
    <code>JetMatching:nQmatch</code> or by the <code>maxjetflavor</code> 
    value in the LHEF. <ei>nQmatch</ei> refers to the absolute value of 
    the quark PDG identity code. 
  </li> 
  <li> 
    All partons arising from the parton shower are sorted based on their 
    motherhood. A showered parton arising from a heavy parton or "other" 
    parton classified in the previous step is not passed to the jet 
    algorithm. All other partons are clustered into light jets. 
  </li> 
  <li> It is checked whether there are "too few" or "too many" light jets. 
    If the number of light jets is less than the number of light partons 
    defined by <ei>nQmatch</ei>, the event is vetoed. If the number is 
    larger, the event is vetoed only in exclusive mode (defined below). 
  </li> 
  <li> In exclusive mode, the number of jets matches the number of light 
    partons. In inclusive mode, the jets are re-clustered until the number 
    of jets equals the number of light partons. Next, each light hard 
    parton is clustered, one at a time, with the jets until a match is found. 
    A match is defined as a squared cluster scale that equals: 
    <ul> 
      <li><ei>|clFact| * qCut</ei> for inclusive mode,</li> 
      <li><ei>|clFact| * max(qCut,min(p<sub>T</sub>(parton)))</ei> 
         for exclusive mode, <ei>clFact</ei> &ge; 0, or</li> 
      <li><ei>|clFact| * min(k<sub>T</sub>(parton))</ei> for exclusive 
         mode, <ei>clFact</ei> &lt; 0.</li> 
    </ul> 
    If no match is found, the event is vetoed. When a parton 
    matches a jet, the jet is removed from the collection, and 
    the process continues. The process terminates when all partons 
    are matched to a jet, or a parton is unmatched. 
  </li> 
  <li> 
    All particles originating from the heavy partons are not used. 
  </li> 
</ul> 
In exclusive mode, it is expected that ME samples with higher parton 
multiplicity are available to fill the phase space above <ei>qCut</ei>. 
The inclusive mode is when there are no such samples, and the parton 
shower is used to fill the phase space. 
 
<p/> 
Some different options are provided, specified further above. These 
are set so that, by default, the algorithm closely follows the 
FORTRAN interface <code>ME2Pythia</code> provided in the Madgraph 
package. 
 
<p/> 
All vetoing of events is done through the usual 
<aloc href="UserHooks">User Hooks</aloc> machinery, and is 
therefore already taken into account in the cross section. In the output 
from <code><aloc href="EventStatistics">Pythia::stat()</aloc></code>, 
the difference between the "Selected" and "Accepted" columns gives the 
number of events that have not survived the vetoing procedure. It is 
still the responsibility of the user to add together the results from 
runs with different jet multiplicities. In the simplest case, when 
the hard process parameters are used to guide the merging procedure, 
events will be matched in the exclusive mode. 
 
<h4>Madgraph scheme with no internal vetoes (assuming an external 
veto implementation)</h4> 
 
<p/> 
This section describes the facilities that allow expert users to use their own 
veto code to perform a Madgraph-style merging. This can e.g. be useful 
to assess parameter changes without having to process the same input 
events multiple times. 
 
<p/> As a first step, any vetoes in the Pythia Jet Matching need to be 
disabled by using <code>JetMatching:doVeto = off</code>. In this mode, 
Pythia only stores all the information that is necessary to check (and apply) 
the shower-kT or kT-MLM vetoes externally by hand. This information can be 
accessed by calling the functions 
 
<method name="Event JetMatchingMadgraph::getWorkEventJet()"> 
Return the event after parton showering, without resonance decay products and 
particles that should not be included in the jet matching, as necessary to 
implement the vetoes in the kT-MLM scheme. 
</method> 
 
<method name="Event JetMatchingMadgraph::getProcessSubset()"> 
Return the event record containing the hard process, without resonance decay 
products and particles that should not be included in the jet matching, as 
necessary to implement the vetoes in the shower-kT and kT-MLM schemes. In the 
former, this event is needed to find the lowest pT in the ME inputs. In 
the latter, the event record is used to count the number of hard-process 
partons, minimal hard process pT, and to perform the matching of hard-process 
particles to shower jets. 
</method> 
 
<method name="bool  JetMatchingMadgraph::getExclusive()"> 
Return flag to identify if exclusive or inclusive vetoes should be applied 
to this event. 
</method> 
 
<method name="double JetMatchingMadgraph::getPTfirst()"> 
Return the transverse momentum (w.r.t. the beam) of the first parton 
shower emission, as needed for the shower-kT scheme. 
</method> 
 
<method name="vector &lt;double&gt; JetMatchingMadgraph::getDJR()"> 
Return a vector of jet clustering scales produced by running the jet algorithm 
used for jet matching on the event record without resonance decay products and 
particles that should not be included in the matching. In this vector, 
clustering scales for combining few jets appear before scales from combining 
many jets. This function is useful for the 
kT-MLM scheme, or to have quick access to this information for histogramming 
and sanity checks. 
</method> 
 
<p/> 
We do not currently supply example code for this very advanced functionality. 
Interested expert users should feel free to contact the Pythia authors for 
further explanations. 
 
 
<p/> 
 
<h3>A note on combining UserHooks</h3> 
 
As have been noted above, the matching is implemented using classes 
derived from the <code><aloc href="UserHooks">UserHooks</aloc></code> 
class, thereby gaining access to the event generation process at the 
relevant locations. For native ALPGEN files, which do not adhere to 
the Les Houches standards, it is also necessary to intervene with 
a <code>UserHooks</code>-derived  <code>AlpgenHooks</code> to handle 
the extraction and setting of relevant extra information. 
 
<p/> 
One must then combine multiple <code>UserHooks</code> classes, 
such that the functionality of both is present. A prerequisite 
is that the different <code>UserHooks</code> classes should be 
declared with virtual inheritance, e.g. 
<pre> 
  class JetMatching : virtual public UserHooks 
</pre> 
Without this option, when combining two <code>UserHooks</code>-derived 
classes, two copies of the base <code>UserHooks</code> class would be 
created, leading to ambiguities. 
 
<p/> 
The two first classes in <code>CombineMatchingInput.h</code> combine 
ALPGEN input with the two different matching schemes, e.g. for the first 
<pre> 
class JetMatchingAlpgenInputAlpgen : public AlpgenHooks, 
  public JetMatchingAlpgen { 
public: 
  // Constructor and destructor. 
  JetMatchingAlpgenInputAlpgen(Pythia& pythia) : AlpgenHooks(pythia), 
    JetMatchingAlpgen() { } 
  ~JetMatchingAlpgenInputAlpgen() {} 
  // Initialisation. 
  virtual bool initAfterBeams() { 
    if (!AlpgenHooks::initAfterBeams()) return false; 
    if (!JetMatchingAlpgen::initAfterBeams()) return false; 
    return true; 
  } 
  // Process level vetos. 
  virtual bool canVetoProcessLevel() { 
    return JetMatchingAlpgen::canVetoProcessLevel(); 
  } 
  .... 
}; 
</pre> 
This class inherits from both <code>AlpgenHooks</code> and 
<code>JetMatchingAlpgen</code>. Any functions which are present 
in both classes should be overridden with a function that calls 
the different parent methods in the desired order. In the 
above example, the only shared methods are the constructor and 
<code>initAfterBeams()</code>. 
 
</chapter> 
 
<!-- Copyright (C) 2020 Torbjorn Sjostrand --> 
