<html>
<head>
<title>Leptoquark Processes</title>
<link rel="stylesheet" type="text/css" href="pythia.css"/>
<link rel="shortcut icon" href="pythia32.gif"/>
</head>
<body>
<h2>Leptoquark Processes</h2>
Leptoquarks arise in many scenarios, and can have widely different
characteristics, with respect to spin, isospin am d flavour.
The current implementation in no sense attempts to exhaust these
possibilities, but only to encode one of the simplest possibilities,
with a single scalar leptoquark, denoted <i>LQ</i> and assigned PDG
code 42. The leptoquark is assumed to carry specific quark
and lepton quantum numbers, by default <i>u</i> quark plus electron.
These flavour numbers are conserved, i.e. a process such as
<i>u e^- -> LQ -> d nu_e</i> is not allowed.
<p/>
Although only one leptoquark is implemented, its flavours may be
changed arbitrarily to study the different possibilities. The
flavours of the leptoquark are defined by the quark and lepton
flavours in the decay mode list. Therefore, to change from the
current <i>u e^-</i> to <i>c mu^+</i>, say, you only need
a line
<br/><code>pythia.readString("42:0:products = 4 -13");</code>
<br/>in your main program, or the equivalent in a command file.
The former must always be a quark, while the latter could be a lepton
or an antilepton; a charge-conjugate partner is automatically defined
by the program. At initialization, the charge is recalculated as a
function of the flavours defined; also the leptoquark name is redefined
to be of the type <code>LQ_q,l</code>, where actual quark and lepton
flavours are displayed.
<p/>
The leptoquark is likely to be fairly long-lived, in which case it
could have time to fragment into a mesonic- or baryonic-type state, which
would decay later on. Currently this possibility is not handled; therefore
the leptoquark is always assumed to decay before fragmentation.
For that reason the leptoquark can also not be put stable.
<h3>Production processes</h3>
Four production processes have been implemented, which normally would
not overlap and therefore could be run together.
<p/><code>flag </code><strong> LeptoQuark:all </strong>
(<code>default = <strong>off</strong></code>)<br/>
Common switch for the group of lowest-order <i>LQ</i> production
processes, i.e. the four ones below.
<p/><code>flag </code><strong> LeptoQuark:ql2LQ </strong>
(<code>default = <strong>off</strong></code>)<br/>
Scatterings <i>q l -> LQ</i>.
Code 3201.
<p/><code>flag </code><strong> LeptoQuark:qg2LQl </strong>
(<code>default = <strong>off</strong></code>)<br/>
Scatterings <i>q g -> LQ l</i>.
Code 3202.
<p/><code>flag </code><strong> LeptoQuark:gg2LQLQbar </strong>
(<code>default = <strong>off</strong></code>)<br/>
Scatterings <i>g g -> LQ LQbar</i>.
Code 3203.
<p/><code>flag </code><strong> LeptoQuark:qqbar2LQLQbar </strong>
(<code>default = <strong>off</strong></code>)<br/>
Scatterings <i>q qbar -> LQ LQbar</i>.
Code 3204.
<h3>Parameters</h3>
In the above scenario the main free parameters are the leptoquark flavour
content, set as already described, and the <i>LQ</i> mass, set as usual.
In addition there is one further parameter.
<p/><code>parm </code><strong> LeptoQuark:kCoup </strong>
(<code>default = <strong>1.0</strong></code>; <code>minimum = 0.0</code>)<br/>
multiplicative factor in the <i>LQ -> q l</i> squared Yukawa coupling,
and thereby in the <i>LQ</i> width and the <i>q l -> LQ</i> and
other cross sections. Specifically, <i>lambda^2/(4 pi) = k alpha_em</i>,
i.e. it corresponds to the $k$ factor of [<a href="Bibliography.html" target="page">Hew88</a>].
</body>
</html>
<!-- Copyright (C) 2013 Torbjorn Sjostrand -->
