| 1 | <html> |
|---|
| 2 | <head> |
|---|
| 3 | <title>The Particle Data Scheme</title> |
|---|
| 4 | <link rel="stylesheet" type="text/css" href="pythia.css"/> |
|---|
| 5 | <link rel="shortcut icon" href="pythia32.gif"/> |
|---|
| 6 | </head> |
|---|
| 7 | <body> |
|---|
| 8 | |
|---|
| 9 | <script language=javascript type=text/javascript> |
|---|
| 10 | function stopRKey(evt) { |
|---|
| 11 | var evt = (evt) ? evt : ((event) ? event : null); |
|---|
| 12 | var node = (evt.target) ? evt.target :((evt.srcElement) ? evt.srcElement : null); |
|---|
| 13 | if ((evt.keyCode == 13) && (node.type=="text")) |
|---|
| 14 | {return false;} |
|---|
| 15 | } |
|---|
| 16 | |
|---|
| 17 | document.onkeypress = stopRKey; |
|---|
| 18 | </script> |
|---|
| 19 | <?php |
|---|
| 20 | if($_POST['saved'] == 1) { |
|---|
| 21 | if($_POST['filepath'] != "files/") { |
|---|
| 22 | echo "<font color='red'>SETTINGS SAVED TO FILE</font><br/><br/>"; } |
|---|
| 23 | else { |
|---|
| 24 | echo "<font color='red'>NO FILE SELECTED YET.. PLEASE DO SO </font><a href='SaveSettings.php'>HERE</a><br/><br/>"; } |
|---|
| 25 | } |
|---|
| 26 | ?> |
|---|
| 27 | |
|---|
| 28 | <form method='post' action='ParticleDataScheme.php'> |
|---|
| 29 | |
|---|
| 30 | <h2>The Particle Data Scheme</h2> |
|---|
| 31 | |
|---|
| 32 | The particle data scheme may take somewhat longer to understand than |
|---|
| 33 | the settings one. In particular the set of methods to access information |
|---|
| 34 | is rather more varied, to allow better functionality for advanced usage. |
|---|
| 35 | However, PYTHIA does come with a sensible default set of particle |
|---|
| 36 | properties and decay tables. Thus there is no need to learn any of the |
|---|
| 37 | methods on this page to get going. Only when you perceive a specific need |
|---|
| 38 | does it make sense to learn the basics. |
|---|
| 39 | |
|---|
| 40 | <p/> |
|---|
| 41 | The central section on this page is the Operation one. The preceding |
|---|
| 42 | sections are there mainly to introduce the basic structure and the set |
|---|
| 43 | of properties that can be accessed. The subsequent sections provide a |
|---|
| 44 | complete listing of the existing public methods, which most users |
|---|
| 45 | probably will have little interaction with. |
|---|
| 46 | |
|---|
| 47 | <h3>Databases</h3> |
|---|
| 48 | |
|---|
| 49 | The management of particle data is based on three classes: |
|---|
| 50 | <ul> |
|---|
| 51 | <li><code>ParticleData</code>, which is the top-level class, with |
|---|
| 52 | methods that can be used to interrogate all particle data. It contains |
|---|
| 53 | a map of PDG particle identity numbers [<a href="Bibliography.php" target="page">Yao06</a>] onto the relevant |
|---|
| 54 | <code>ParticleDataEntry</code> objects,</li> |
|---|
| 55 | <li><code>ParticleDataEntry</code>, which stores the relevant information |
|---|
| 56 | on an individual particle species, and</li> |
|---|
| 57 | <li><code>DecayChannel</code>, which stores info on one particular decay |
|---|
| 58 | mode of a particle.</li> |
|---|
| 59 | |
|---|
| 60 | </ul> |
|---|
| 61 | The objects of these classes together form a database that is |
|---|
| 62 | continuously being used as the program has to assign particle masses, |
|---|
| 63 | select decay modes, etc. |
|---|
| 64 | |
|---|
| 65 | <p/> |
|---|
| 66 | Each <code>Pythia</code> object has a public member |
|---|
| 67 | <code>particleData</code> of the <code>ParticleData</code> class. |
|---|
| 68 | Therefore you access the particle data methods as |
|---|
| 69 | <code>pythia.particleData.command(argument)</code>, |
|---|
| 70 | assuming that <code>pythia</code> is an instance of the |
|---|
| 71 | <code>Pythia</code> class. Further, for some of the most frequent user |
|---|
| 72 | tasks, <code>Pythia</code> methods have been defined, so that |
|---|
| 73 | <code>pythia.command(argument)</code> |
|---|
| 74 | would work, see further below. |
|---|
| 75 | |
|---|
| 76 | <p/> |
|---|
| 77 | A fundamental difference between the particle data classes and the |
|---|
| 78 | settings ones is that the former are accessed regularly during the |
|---|
| 79 | event generation process, as a new particle is produced and its mass |
|---|
| 80 | need to be set, e.g., while the latter are mainly/only used |
|---|
| 81 | at the initialization stage. Nevertheless, it is not a good idea to |
|---|
| 82 | change data in either of them in mid-run, since this may lead to |
|---|
| 83 | inconsistencies. |
|---|
| 84 | |
|---|
| 85 | <h3>Stored properties for particles</h3> |
|---|
| 86 | |
|---|
| 87 | The main properties stored for each particle are as follows. |
|---|
| 88 | Different ways to set and get these properties will be described |
|---|
| 89 | further down. |
|---|
| 90 | |
|---|
| 91 | <ul> |
|---|
| 92 | |
|---|
| 93 | <li><code>name</code>: a character string with the name of the |
|---|
| 94 | particle. Particle and antiparticle names are stored separately, |
|---|
| 95 | with <code>void</code> returned when no antiparticle exists.</li> |
|---|
| 96 | |
|---|
| 97 | <li><code>spinType</code>: the spin type, of the form <i>2 s + 1</i>, |
|---|
| 98 | with special code 0 for entries of unknown or indeterminate spin.</li> |
|---|
| 99 | |
|---|
| 100 | <li><code>chargeType</code>: three times the charge (to make it an |
|---|
| 101 | integer).</li> |
|---|
| 102 | |
|---|
| 103 | <li><code>colType</code>: the colour type, with 0 uncoloured, 1 triplet, |
|---|
| 104 | -1 antitriplet and 2 octet. (A preliminary implementation of colour |
|---|
| 105 | sextets, available since version 8.150, further uses 3 for a sextet |
|---|
| 106 | and -3 for an antisextet.) </li> |
|---|
| 107 | |
|---|
| 108 | <li><code>m0</code>: the nominal mass <i>m_0</i> (in GeV).</li> |
|---|
| 109 | |
|---|
| 110 | <li><code>mWidth</code>: the width <i>Gamma</i> of the Breit-Wigner |
|---|
| 111 | distribution (in GeV).</li> |
|---|
| 112 | |
|---|
| 113 | <li><code>mMin</code>: the lower limit of the allowed mass range |
|---|
| 114 | generated by the Breit-Wigner (in GeV). Has no meaning for particles |
|---|
| 115 | without width, and would typically be 0 there.</li> |
|---|
| 116 | |
|---|
| 117 | <li><code>mMax</code>: the upper limit of the allowed mass range |
|---|
| 118 | generated by the Breit-Wigner (in GeV). If <i>mMax < mMin</i> then |
|---|
| 119 | no upper limit is imposed. Has no meaning for particles without width, |
|---|
| 120 | and would typically be 0 there.</li> |
|---|
| 121 | |
|---|
| 122 | <li><code>tau0</code>: the nominal proper lifetime <i>tau_0</i> |
|---|
| 123 | (in mm/c).</li> |
|---|
| 124 | |
|---|
| 125 | <li><code>isResonance</code>: a flag telling whether a particle species |
|---|
| 126 | is considered as a resonance or not. Here |
|---|
| 127 | <?php $filepath = $_GET["filepath"]; |
|---|
| 128 | echo "<a href='ResonanceDecays.php?filepath=".$filepath."' target='page'>";?>"resonance"</a> is used as shorthand |
|---|
| 129 | for any massive particle where the decay process should be counted as part |
|---|
| 130 | of the hard process itself, and thus be performed before showers and other |
|---|
| 131 | event aspects are added. Restrictions on allowed decay channels is also |
|---|
| 132 | directly reflected in the cross section of simulated processes, while |
|---|
| 133 | those of normal hadrons and other light particles are not. |
|---|
| 134 | In practice, it is reserved for states above the <i>b bbar</i> |
|---|
| 135 | bound systems in mass, i.e. for <i>W, Z, t</i>, Higgs states, |
|---|
| 136 | supersymmetric states and (most?) other states in any new theory. |
|---|
| 137 | All particles with <code>m0</code> above 20 GeV are by default |
|---|
| 138 | initialized to be considered as resonances.</li> |
|---|
| 139 | |
|---|
| 140 | <li><code>mayDecay</code>: a flag telling whether a particle species |
|---|
| 141 | may decay or not, offering the main user switch. Whether a given particle |
|---|
| 142 | of this kind then actually will decay also depends on it having allowed |
|---|
| 143 | decay channels, and on other flags for |
|---|
| 144 | <?php $filepath = $_GET["filepath"]; |
|---|
| 145 | echo "<a href='ParticleDecays.php?filepath=".$filepath."' target='page'>";?>particle decays</a>. |
|---|
| 146 | All particles with <code>tau0</code> below 1000 mm are |
|---|
| 147 | by default initialized to allow decays.</li> |
|---|
| 148 | |
|---|
| 149 | <li><code>doExternalDecays</code>: a flag telling whether a particle |
|---|
| 150 | should be handled by an external decay package or not, with the latter |
|---|
| 151 | default. Can be manipulated as described on this page, but should |
|---|
| 152 | normally not be. Instead the |
|---|
| 153 | <code><?php $filepath = $_GET["filepath"]; |
|---|
| 154 | echo "<a href='ExternalDecays.php?filepath=".$filepath."' target='page'>";?>Pythia::decayPtr(...)</a></code> |
|---|
| 155 | method should be provided with the list of relevant particles.</li> |
|---|
| 156 | |
|---|
| 157 | <li><code>isVisible</code>: a flag telling whether a particle species |
|---|
| 158 | is to be considered as visible in a detector or not, as used e.g. in |
|---|
| 159 | analysis routines. By default this includes neutrinos and a few BSM |
|---|
| 160 | particles (gravitino, sneutrinos, neutralinos) that have neither strong |
|---|
| 161 | nor electromagnetic charge, and are not made up of constituents that |
|---|
| 162 | have it. The value of this flag is only relevant if a particle is |
|---|
| 163 | long-lived enough actually to make it to a detector.</li> |
|---|
| 164 | |
|---|
| 165 | <li><code>doForceWidth</code>: a flag valid only for resonances where |
|---|
| 166 | PYTHIA contains code to calculate the width of the resonance from |
|---|
| 167 | encoded matrix-element expressions, i.e. the <i>Z^0</i>, <i>W^+-</i>, |
|---|
| 168 | <i>t</i>, <i>h^0</i>, and a few more. The normal behaviour |
|---|
| 169 | (<code>false</code>) is then that the width is calculated from the mass, |
|---|
| 170 | but it is possible to <?php $filepath = $_GET["filepath"]; |
|---|
| 171 | echo "<a href='ResonanceDecays.php?filepath=".$filepath."' target='page'>";?>force</a> the |
|---|
| 172 | resonance to retain the nominal width. Branching ratios and the running |
|---|
| 173 | of the total width are unaffected.</li> |
|---|
| 174 | |
|---|
| 175 | </ul> |
|---|
| 176 | |
|---|
| 177 | <h3>Stored properties for decays</h3> |
|---|
| 178 | |
|---|
| 179 | An unstable particle has a decay table consisting of one or more |
|---|
| 180 | decay channel. The following properties are stored for each such channel. |
|---|
| 181 | Again different ways to set and get these properties will be described |
|---|
| 182 | further down. |
|---|
| 183 | <ul> |
|---|
| 184 | |
|---|
| 185 | <li><code>onMode</code>: integer code for use or not of channel,<br/> |
|---|
| 186 | 0 if a channel is off,<br/> |
|---|
| 187 | 1 if on,<br/> |
|---|
| 188 | 2 if on for a particle but off for an antiparticle,<br/> |
|---|
| 189 | 3 if on for an antiparticle but off for a particle.<br/> |
|---|
| 190 | If a particle is its own antiparticle then 2 is on and 3 off |
|---|
| 191 | but, of course, for such particles it is much simpler and safer |
|---|
| 192 | to use only 1 and 0.<br/> |
|---|
| 193 | The 2 and 3 options can be used e.g. to encode CP violation in |
|---|
| 194 | B decays, or to let the <i>W</i>'s in a <i>q qbar -> W^+ W^-</i> |
|---|
| 195 | process decay in different channels. </li> |
|---|
| 196 | |
|---|
| 197 | <li><code>bRatio</code>: the branching ratio of the channel.</li> |
|---|
| 198 | |
|---|
| 199 | <li><code>meMode</code>: the mode of processing this channel, possibly |
|---|
| 200 | with matrix elements; see the |
|---|
| 201 | <?php $filepath = $_GET["filepath"]; |
|---|
| 202 | echo "<a href='ParticleDecays.php?filepath=".$filepath."' target='page'>";?>particle decays</a> description</li> |
|---|
| 203 | for the list of possibilities. |
|---|
| 204 | |
|---|
| 205 | <li><code>multiplicity</code>: the number of decay products of the |
|---|
| 206 | channel. Can be at most 8.</li> |
|---|
| 207 | |
|---|
| 208 | <li><code>product(i)</code>: the identity code of the decay products, |
|---|
| 209 | where <code>i</code> runs between <code>0</code> and |
|---|
| 210 | <code>multiplicity - 1</code>. Trailing positions are filled with 0. |
|---|
| 211 | </li> |
|---|
| 212 | |
|---|
| 213 | </ul> |
|---|
| 214 | |
|---|
| 215 | <h3>Operation</h3> |
|---|
| 216 | |
|---|
| 217 | The normal flow of the particle data operations is: |
|---|
| 218 | |
|---|
| 219 | <ol> |
|---|
| 220 | |
|---|
| 221 | <li> |
|---|
| 222 | When a <code>Pythia</code> object <code>pythia</code> is created, the |
|---|
| 223 | <code>pythia.particleData</code> member is asked to scan the |
|---|
| 224 | <code>ParticleData.xml</code> file. |
|---|
| 225 | |
|---|
| 226 | <p/> |
|---|
| 227 | All lines beginning with <code><particle</code> are scanned for |
|---|
| 228 | information on a particle species, and all lines beginning with |
|---|
| 229 | <code><channel</code> are assumed to contain a decay channel of the |
|---|
| 230 | enclosing particle. In both cases XML syntax is used, with attributes |
|---|
| 231 | used to identify the stored properties, and with omitted properties |
|---|
| 232 | defaulting back to 0 where meaningful. The particle and channel |
|---|
| 233 | information may be split over several lines, up to the > endtoken. |
|---|
| 234 | The format of a <code><particle</code> tag is: |
|---|
| 235 | <pre> |
|---|
| 236 | <particle id="..." name="..." antiName="..." spinType="..." chargeType="..." colType="..." |
|---|
| 237 | m0="..." mWidth="..." mMin="..." mMax="..." tau0="..."> |
|---|
| 238 | </particle> |
|---|
| 239 | </pre> |
|---|
| 240 | where the fields are the properties already introduced above. |
|---|
| 241 | Note that <code>isResonance</code>, <code>mayDecay</code>, |
|---|
| 242 | <code>doExternalDecay</code>, <code>isVisible</code> and |
|---|
| 243 | <code>doForceWidth</code> are not set here, but are provided with |
|---|
| 244 | default values by the rules described above. Once initialized, also |
|---|
| 245 | these latter properties can be changed, see below.<br/> |
|---|
| 246 | |
|---|
| 247 | The format of a <code><channel></code> tag is: |
|---|
| 248 | <pre> |
|---|
| 249 | <channel onMode="..." bRatio="..." meMode="..." products="..." /> |
|---|
| 250 | </pre> |
|---|
| 251 | again see properties above. The products are given as a blank-separated |
|---|
| 252 | list of <code>id</code> codes. |
|---|
| 253 | <br/><b>Important</b>: the values in the <code>.xml</code> file should not |
|---|
| 254 | be changed, except by the PYTHIA authors. Any changes should be done |
|---|
| 255 | with the help of the methods described below. |
|---|
| 256 | </li> |
|---|
| 257 | |
|---|
| 258 | <li> <p/> |
|---|
| 259 | Between the creation of the <code>Pythia</code> object and the |
|---|
| 260 | <code>init</code> call for it, you may use the methods of the |
|---|
| 261 | <code>ParticleData</code> class to modify some of the default values. |
|---|
| 262 | Several different approaches can be chosen for this. |
|---|
| 263 | |
|---|
| 264 | <p/> |
|---|
| 265 | a) Inside your main program you can directly set values with |
|---|
| 266 | <pre> |
|---|
| 267 | pythia.readString(string); |
|---|
| 268 | </pre> |
|---|
| 269 | where both the variable name and the value are contained inside |
|---|
| 270 | the character string, separated by blanks and/or a =, e.g. |
|---|
| 271 | <pre> |
|---|
| 272 | pythia.readString("111:mayDecay = off"); |
|---|
| 273 | </pre> |
|---|
| 274 | switches off the decays of the <i>pi^0</i>.<br/> |
|---|
| 275 | |
|---|
| 276 | The particle id (> 0) and the property to be changed must be given, |
|---|
| 277 | separated by a colon.<br/> |
|---|
| 278 | |
|---|
| 279 | The allowed properties are: <code>name</code>, <code>antiName</code>, |
|---|
| 280 | <code>spinType</code>, <code>chargeType</code>, <code>colType</code>, |
|---|
| 281 | <code>m0</code>, <code>mWidth</code>, <code>mMin</code>, |
|---|
| 282 | <code>mMax</code>, <code>tau0</code>, <code>isResonance</code>, |
|---|
| 283 | <code>mayDecay</code>, <code>doExternalDecay</code>, |
|---|
| 284 | <code>isVisible</code> and <code>doForceWidth</code>. All of these |
|---|
| 285 | names are case-insensitive. Names that do not match an existing |
|---|
| 286 | variable are ignored.<br/> |
|---|
| 287 | |
|---|
| 288 | Strings beginning with a non-alphanumeric character, like # or !, |
|---|
| 289 | are assumed to be comments and are not processed at all. For |
|---|
| 290 | <code>bool</code> values, the following notation may be used |
|---|
| 291 | interchangeably: <code>true = on = yes = ok = 1</code>, while everything |
|---|
| 292 | else gives <code>false</code> (including but not limited to |
|---|
| 293 | <code>false</code>, <code>off</code>, <code>no</code> and |
|---|
| 294 | <code>0</code>). |
|---|
| 295 | |
|---|
| 296 | <p/> |
|---|
| 297 | Particle data often comes in sets of closely related information. |
|---|
| 298 | Therefore some properties expect the value to consist of several |
|---|
| 299 | numbers. These can then be separated by blanks (or by commas). |
|---|
| 300 | A simple example is <code>names</code>, which expects both the |
|---|
| 301 | name and antiname to be given. A more interesting one is the |
|---|
| 302 | <code>all</code> property, |
|---|
| 303 | <pre> |
|---|
| 304 | id:all = name antiName spinType chargeType colType m0 mWidth mMin mMax tau0 |
|---|
| 305 | </pre> |
|---|
| 306 | where all the current information on the particle itself is replaced, |
|---|
| 307 | but any decay channels are kept unchanged. Using <code>new</code> instead |
|---|
| 308 | of <code>all</code> also removes any previous decay channels. |
|---|
| 309 | If the string contains fewer fields than expected the trailing |
|---|
| 310 | properties are set to vanish ("void", 0 or 0.). Note that such a |
|---|
| 311 | truncated string should not be followed by a comment, since this |
|---|
| 312 | comment would then be read in as if it contained the missing properties. |
|---|
| 313 | The truncation can be done anywhere, specifically a string with only |
|---|
| 314 | <code>id:new</code> defines a new "empty" particle. |
|---|
| 315 | As before, <code>isResonance</code>, <code>mayDecay</code>, |
|---|
| 316 | <code>doExternalDecay</code>, <code>isVisible</code> and |
|---|
| 317 | <code>doForceWidth</code> are (re)set to their default values, and |
|---|
| 318 | would have to be changed separately if required. |
|---|
| 319 | |
|---|
| 320 | <p/> |
|---|
| 321 | A further command is <code>rescaleBR</code>, which rescales each of the |
|---|
| 322 | existing branching ratios with a common factor, such that their new |
|---|
| 323 | sum is the provided value. This may be a first step towards adding |
|---|
| 324 | new decay channels, see further below. |
|---|
| 325 | |
|---|
| 326 | <p/> |
|---|
| 327 | Alternatively the <code>id</code> code may be followed by another integer, |
|---|
| 328 | which then gives the decay channel number. This then has to be |
|---|
| 329 | followed by the property specific to this channel, either |
|---|
| 330 | <code>onMode</code>, <code>bRatio</code>, <code>meMode</code> or |
|---|
| 331 | <code>products</code>. In the latter case all the products of |
|---|
| 332 | the channel should be given: |
|---|
| 333 | <pre> |
|---|
| 334 | id:channel:products = product1 product2 .... |
|---|
| 335 | </pre> |
|---|
| 336 | The line will be scanned until the end of the line, or until a |
|---|
| 337 | non-number word is encountered, or until the maximum allowed number |
|---|
| 338 | of eight products is encountered, whichever happens first. (Thus the |
|---|
| 339 | multiplicity of a decay channel need not be input; it is automatically |
|---|
| 340 | calculated from the products list.) It is also possible to replace all |
|---|
| 341 | the properties of a channel in a similar way: |
|---|
| 342 | <pre> |
|---|
| 343 | id:channel:all = onMode bRatio meMode product1 product2 .... |
|---|
| 344 | </pre> |
|---|
| 345 | To add a new channel at the end, use |
|---|
| 346 | <pre> |
|---|
| 347 | id:addChannel = onMode bRatio meMode product1 product2 .... |
|---|
| 348 | </pre> |
|---|
| 349 | |
|---|
| 350 | <p/> |
|---|
| 351 | It is currently not possible to remove a channel selectively, but |
|---|
| 352 | setting its branching ratio vanishing is as effective. If you want to |
|---|
| 353 | remove all existing channels and force decays into one new channel |
|---|
| 354 | you can use |
|---|
| 355 | <pre> |
|---|
| 356 | id:oneChannel = onMode bRatio meMode product1 product2 .... |
|---|
| 357 | </pre> |
|---|
| 358 | A first <code>oneChannel</code> command could be followed by |
|---|
| 359 | several subsequent <code>addChannel</code> ones, to build |
|---|
| 360 | up a completely new decay table for an existing particle. |
|---|
| 361 | |
|---|
| 362 | <p/> |
|---|
| 363 | When adding new channels or changing branching ratios in general, |
|---|
| 364 | note that, once a particle is to be decayed, the sum of branching |
|---|
| 365 | ratios is always rescaled to unity. Beforehand, <code>rescaleBR</code> |
|---|
| 366 | may be used to rescale an existing branching ratio by the given factor. |
|---|
| 367 | |
|---|
| 368 | <p/> |
|---|
| 369 | There are a few commands that will study all the decay channels of the |
|---|
| 370 | given particle, to switch them on or off as desired. The |
|---|
| 371 | <pre> |
|---|
| 372 | id:onMode = onMode |
|---|
| 373 | </pre> |
|---|
| 374 | will set the <code>onMode</code> property of all channels to the |
|---|
| 375 | desired value. The |
|---|
| 376 | <pre> |
|---|
| 377 | id:offIfAny = product1 product2 .... |
|---|
| 378 | id:onIfAny = product1 product2 .... |
|---|
| 379 | id:onPosIfAny = product1 product2 .... |
|---|
| 380 | id:onNegIfAny = product1 product2 .... |
|---|
| 381 | </pre> |
|---|
| 382 | will set the <code>onMode</code> 0, 1, 2 or 3, respectively, for all |
|---|
| 383 | channels which contain any of the enumerated products, where the matching |
|---|
| 384 | to these products is done without distinction of particles and |
|---|
| 385 | antiparticles. Note that "<code>Pos</code>" and "<code>Neg</code>" |
|---|
| 386 | are slightly misleading since it refers to the particle and antiparticle |
|---|
| 387 | of the <code>id</code> species rather than charge, but should still be |
|---|
| 388 | simpler to remember and understand than alternative notations. |
|---|
| 389 | Correspondingly |
|---|
| 390 | <pre> |
|---|
| 391 | id:offIfAll = product1 product2 .... |
|---|
| 392 | id:onIfAll = product1 product2 .... |
|---|
| 393 | id:onPosIfAll = product1 product2 .... |
|---|
| 394 | id:onNegIfAll = product1 product2 .... |
|---|
| 395 | </pre> |
|---|
| 396 | will set the <code>onMode</code> 0, 1, 2 or 3, respectively, for all |
|---|
| 397 | channels which contain all of the enumerated products, again without |
|---|
| 398 | distinction of particles and antiparticles. If the same product appears |
|---|
| 399 | twice in the list it must also appear twice in the decay channel, and |
|---|
| 400 | so on. The decay channel is allowed to contain further particles, |
|---|
| 401 | beyond the product list. By contrast, |
|---|
| 402 | <pre> |
|---|
| 403 | id:offIfMatch = product1 product2 .... |
|---|
| 404 | id:onIfMatch = product1 product2 .... |
|---|
| 405 | id:onPosIfMatch = product1 product2 .... |
|---|
| 406 | id:onPosIfMatch = product1 product2 .... |
|---|
| 407 | </pre> |
|---|
| 408 | requires the decay-channel multiplicity to agree with that of the product |
|---|
| 409 | list, but otherwise works as the <code>onIfAll/offIfAll</code> methods. |
|---|
| 410 | |
|---|
| 411 | <p/> |
|---|
| 412 | Note that the action of several of the commands depends on the order |
|---|
| 413 | in which they are executed, as one would logically expect. For instance, |
|---|
| 414 | <code>id:oneChannel</code> removes all decay channels of <code>id</code> |
|---|
| 415 | and thus all previous changes in this decay table, while subsequent |
|---|
| 416 | additions or changes would still take effect. Another example would be that |
|---|
| 417 | <code>23:onMode = off</code> followed by <code>23:onIfAny = 1 2 3 4 5</code> |
|---|
| 418 | would let the <i>Z^0</i> decay to quarks, while no decays would be |
|---|
| 419 | allowed if the order were to be reversed. |
|---|
| 420 | |
|---|
| 421 | <p/> |
|---|
| 422 | b) The <code>Pythia</code> <code>readString(string)</code> method actually |
|---|
| 423 | does not do changes itself, but sends on the string either to the |
|---|
| 424 | <code>ParticleData</code> class or to the <code>Settings</code> one, |
|---|
| 425 | depending on whether the string begins with a digit or a letter. |
|---|
| 426 | If desired, it is possible to communicate directly with the corresponding |
|---|
| 427 | <code>ParticleData</code> method: |
|---|
| 428 | <pre> |
|---|
| 429 | pythia.particleData.readString("111:mayDecay = off"); |
|---|
| 430 | pythia.particleData.readString("15:2:products = 16 -211"); |
|---|
| 431 | </pre> |
|---|
| 432 | In this case, changes intended for <code>Settings</code> would not be |
|---|
| 433 | understood. |
|---|
| 434 | |
|---|
| 435 | <p/> |
|---|
| 436 | c) Underlying this are commands for all the individual properties in |
|---|
| 437 | the <code>ParticleData</code> class, one for each. These are |
|---|
| 438 | further described below. Thus, an example now reads |
|---|
| 439 | <pre> |
|---|
| 440 | pythia.particleData.mayDecay(111, false); |
|---|
| 441 | </pre> |
|---|
| 442 | Boolean values should here be given as <code>true</code> or |
|---|
| 443 | <code>false</code>. |
|---|
| 444 | |
|---|
| 445 | <p/> |
|---|
| 446 | d) A simpler and more useful way is to collect all your changes |
|---|
| 447 | in a separate file, with one line per change, e.g. |
|---|
| 448 | <pre> |
|---|
| 449 | 111:mayDecay = off |
|---|
| 450 | </pre> |
|---|
| 451 | The file can be read by the |
|---|
| 452 | <pre> |
|---|
| 453 | pythia.readFile(fileName); |
|---|
| 454 | </pre> |
|---|
| 455 | method, where <code>fileName</code> is a string, e.g. |
|---|
| 456 | <code>pythia.readFile("main.cmnd")</code> (or an <code>istream</code> |
|---|
| 457 | instead of a <code>fileName</code>). Each line is processed as |
|---|
| 458 | described for the string in 2a). This file can freely mix commands to |
|---|
| 459 | the <code>Settings</code> and <code>ParticleData</code> classes. |
|---|
| 460 | </li> |
|---|
| 461 | |
|---|
| 462 | <li> <p/> |
|---|
| 463 | A routine <code>reInit(fileName)</code> is provided, and can be used to |
|---|
| 464 | zero the particle data table and reinitialize it from scratch. |
|---|
| 465 | Such a call might be useful if several subruns are to be made with |
|---|
| 466 | widely different particle data - normally the maps are only built |
|---|
| 467 | from scratch once, namely when the <code>Pythia()</code> object is |
|---|
| 468 | created. Also, there is no other possibility to restore the default |
|---|
| 469 | values, unlike for the settings. |
|---|
| 470 | </li> |
|---|
| 471 | |
|---|
| 472 | <li> <p/> |
|---|
| 473 | You may at any time obtain a listing of all the particle data by calling |
|---|
| 474 | <pre> |
|---|
| 475 | pythia.particleData.listAll(); |
|---|
| 476 | </pre> |
|---|
| 477 | The listing is by increasing <code>id</code> number. It shows the basic |
|---|
| 478 | quantities introduced above. Some are abbreviated in the header to fit on |
|---|
| 479 | the lines: <code>spn = spinType</code>, <code>chg = chargeType</code>, |
|---|
| 480 | <code>col = colType</code>, <code>res = isResonance</code>, |
|---|
| 481 | <code>dec = mayDecay && canDecay</code> (the latter checks that decay |
|---|
| 482 | channels have been defined), <code>ext = doExternalDecay</code>, |
|---|
| 483 | <code>vis = isVisible</code> and <code>wid = doForceWidth</code>.<br/> |
|---|
| 484 | |
|---|
| 485 | To list only those particles that were changed (one way or another, the |
|---|
| 486 | listing will not tell what property or decay channel was changed), instead use |
|---|
| 487 | <pre> |
|---|
| 488 | pythia.particleData.listChanged(); |
|---|
| 489 | </pre> |
|---|
| 490 | (This info is based on a further <code>hasChanged</code> flag of a particle |
|---|
| 491 | or a channel, set <code>true</code> whenever any of the changing methods are |
|---|
| 492 | used. It is possible to manipulate this value, but this is not recommended.) |
|---|
| 493 | By default the internal initialization of the widths of resonances such as |
|---|
| 494 | <i>gamma^*/Z^0, W^+-, t/tbar, H^0</i> do not count as changes; if you want |
|---|
| 495 | to list also those changes instead call <code>listChanged(true)</code>. |
|---|
| 496 | <br/> |
|---|
| 497 | |
|---|
| 498 | To list only one particle, give its <code>id</code> code as argument to |
|---|
| 499 | the <code>list(...)</code> function.. To list a restricted set of particles, |
|---|
| 500 | give in their <code>id</code> codes to <code>list(...)</code> as a |
|---|
| 501 | <code>vector<int></code>. |
|---|
| 502 | </li> |
|---|
| 503 | |
|---|
| 504 | <li> <p/> |
|---|
| 505 | For wholesale changes of particle properties all available data can be |
|---|
| 506 | written out, edited, and then read back in again. These methods are |
|---|
| 507 | mainly intended for expert users. You can choose between two alternative |
|---|
| 508 | syntaxes. |
|---|
| 509 | |
|---|
| 510 | <p/> |
|---|
| 511 | a) XML syntax, using the <code><particle</code> and |
|---|
| 512 | <code><channel</code> lines already described. You use the method |
|---|
| 513 | <code>particleData.listXML(fileName)</code> to produce such an XML |
|---|
| 514 | file and <code>particleData.readXML(fileName)</code> to read it back |
|---|
| 515 | in after editing. |
|---|
| 516 | |
|---|
| 517 | <p/> |
|---|
| 518 | b) Fixed/free format, using exactly the same information as illustrated |
|---|
| 519 | for the <code><particle</code> and <code><channel</code> lines |
|---|
| 520 | above, but now without any tags. This means that all information fields |
|---|
| 521 | must be provided (if there is no antiparticle then write |
|---|
| 522 | <code>void</code>), in the correct order (while the order is irrelevant |
|---|
| 523 | with XML syntax), and all on one line. Information is written out in |
|---|
| 524 | properly lined-up columns, but the reading is done using free format, |
|---|
| 525 | so fields need only be separated by at least one blank. Each new particle |
|---|
| 526 | is supposed to be separated by (at least) one blank line, whereas no |
|---|
| 527 | blank lines are allowed between the particle line and the subsequent |
|---|
| 528 | decay channel lines, if any. You use the method |
|---|
| 529 | <code>particleData.listFF(fileName)</code> to produce such a fixed/free |
|---|
| 530 | file and <code>particleData.readFF(fileName)</code> to read it back |
|---|
| 531 | in after editing. |
|---|
| 532 | |
|---|
| 533 | <p/> |
|---|
| 534 | As an alternative to the <code>readXML</code> and <code>readFF</code> |
|---|
| 535 | methods you can also use the |
|---|
| 536 | <code>particleData.reInit(fileName, xmlFormat)</code> method, where |
|---|
| 537 | <code>xmlFormat = true</code> (default) corresponds to reading an XML |
|---|
| 538 | file and <code>xmlFormat = false</code> to a fixed/free format one. |
|---|
| 539 | |
|---|
| 540 | <p/> |
|---|
| 541 | To check that the new particle and decay tables makes sense, you can use |
|---|
| 542 | the <code>particleData.checkTable()</code> method, either directly or by |
|---|
| 543 | switching it on among the standard |
|---|
| 544 | <?php $filepath = $_GET["filepath"]; |
|---|
| 545 | echo "<a href='ErrorChecks.php?filepath=".$filepath."' target='page'>";?>error checks</a>. |
|---|
| 546 | </li> |
|---|
| 547 | |
|---|
| 548 | </ol> |
|---|
| 549 | |
|---|
| 550 | <h2>The public methods</h2> |
|---|
| 551 | |
|---|
| 552 | In the following we present briefly the public methods in the three |
|---|
| 553 | classes used to build up the particle database. The order |
|---|
| 554 | is top-down, i.e from the full table of all particles to a single |
|---|
| 555 | particle to a single channel. |
|---|
| 556 | Note that these methods usually are less elegant and safe than the |
|---|
| 557 | input methods outlined above. If you use any of these methods, it is |
|---|
| 558 | likely to be the ones in the full database, i.e. the first ones to be |
|---|
| 559 | covered in the following. |
|---|
| 560 | |
|---|
| 561 | <p/> |
|---|
| 562 | For convenience, we have grouped related input and output methods |
|---|
| 563 | together. It should be obvious from the context which is which: |
|---|
| 564 | the input is of type <code>void</code> and has an extra last argument, |
|---|
| 565 | namely is the input value, while the output method returns a |
|---|
| 566 | quantity of the expected type. |
|---|
| 567 | |
|---|
| 568 | <h3>The ParticleData methods</h3> |
|---|
| 569 | |
|---|
| 570 | <a name="method1"></a> |
|---|
| 571 | <p/><strong>ParticleData::ParticleData() </strong> <br/> |
|---|
| 572 | the constructor has no arguments and does not do anything. Internal. |
|---|
| 573 | |
|---|
| 574 | |
|---|
| 575 | <a name="method2"></a> |
|---|
| 576 | <p/><strong>void ParticleData::initPtr(Info* infoPtr,Settings* settingsPtrIn, Rndm* rndmPtrIn, CoupSM* coupSMPtrIn) </strong> <br/> |
|---|
| 577 | initialize pointers to a few other classes. Internal. |
|---|
| 578 | |
|---|
| 579 | |
|---|
| 580 | <a name="method3"></a> |
|---|
| 581 | <p/><strong>bool ParticleData::init(string startFile = "../xmldoc/ParticleData.xml") </strong> <br/> |
|---|
| 582 | read in an XML-style file with particle data and initialize the |
|---|
| 583 | particle data tables accordingly. This command is executed |
|---|
| 584 | in the <code>Pythia</code> constructor, i.e. is mainly for |
|---|
| 585 | internal use. |
|---|
| 586 | <br/><code>argument</code><strong> startFile </strong> (<code>default = <strong>../xmldoc/ParticleData.xml</strong></code>) : |
|---|
| 587 | the name of the data file to be read. When called from the |
|---|
| 588 | <code>Pythia</code> constructor the directory is provided by the |
|---|
| 589 | <code><?php $filepath = $_GET["filepath"]; |
|---|
| 590 | echo "<a href='ProgramFlow.php?filepath=".$filepath."' target='page'>";?>PYTHIA8DATA</a></code> |
|---|
| 591 | environment variable, if set, else by the argument of this constructor, |
|---|
| 592 | which has the default value "../xmldoc". |
|---|
| 593 | |
|---|
| 594 | |
|---|
| 595 | |
|---|
| 596 | <a name="method4"></a> |
|---|
| 597 | <p/><strong>bool ParticleData::reInit(string startFile,bool xmlFormat = true) </strong> <br/> |
|---|
| 598 | overwrite the existing database by reading from the specified file. |
|---|
| 599 | Unlike <code>init</code> above this method is not called by the |
|---|
| 600 | <code>Pythia</code> constructor, but is entirely intended for users |
|---|
| 601 | who want to replace the existing particle data with their own. |
|---|
| 602 | <br/><code>argument</code><strong> startFile </strong> : the path and name of file to be read. |
|---|
| 603 | |
|---|
| 604 | <br/><code>argument</code><strong> xmlFormat </strong> : if true read the same kind of XML-style file |
|---|
| 605 | as used by <code>init</code>, if not use an alternative "free format" |
|---|
| 606 | file (i.e. without any XML tags, but with well-defined rules |
|---|
| 607 | specifying in which order properties are stored). |
|---|
| 608 | |
|---|
| 609 | |
|---|
| 610 | |
|---|
| 611 | <a name="method5"></a> |
|---|
| 612 | <p/><strong>void ParticleData::initWidths(vector<ResonanceWidths*> resonancePtrs) </strong> <br/> |
|---|
| 613 | initialize Breit-Wigner shape parameters for all particles, |
|---|
| 614 | and the detailed handling of resonances, i.e. particles with |
|---|
| 615 | perturbatively calculable partial widths, which can be used to |
|---|
| 616 | obtain a mass-dependent Breit-Wigner and a dynamic choice of |
|---|
| 617 | decay channels. Called from <code>Pythia::init()</code>. |
|---|
| 618 | |
|---|
| 619 | |
|---|
| 620 | <a name="method6"></a> |
|---|
| 621 | <p/><strong>bool ParticleData::readXML(string inFile, bool reset = true) </strong> <br/> |
|---|
| 622 | |
|---|
| 623 | <strong>void ParticleData::listXML(string outFile) </strong> <br/> |
|---|
| 624 | read in XML-style data from a file or write it out to a file. For the |
|---|
| 625 | former one can also decide whether to reset all particles to scratch, |
|---|
| 626 | or only overwrite those particles in the file. The former method is |
|---|
| 627 | used by <code>init</code> and <code>reInit</code> above. |
|---|
| 628 | |
|---|
| 629 | |
|---|
| 630 | <a name="method7"></a> |
|---|
| 631 | <p/><strong>bool ParticleData::readFF(string inFile, bool reset = true) </strong> <br/> |
|---|
| 632 | |
|---|
| 633 | <strong>void ParticleData::listFF(string outFile) </strong> <br/> |
|---|
| 634 | read in free-format-style data from a file or write it out to a file. |
|---|
| 635 | For the former one can also decide whether to reset all particles to |
|---|
| 636 | scratch, or only overwrite those particles in the file. The former |
|---|
| 637 | method is used by <code>reInit</code> above. |
|---|
| 638 | |
|---|
| 639 | |
|---|
| 640 | <a name="method8"></a> |
|---|
| 641 | <p/><strong>bool ParticleData::readString(string line, bool warn = true, ostream& os = cout) </strong> <br/> |
|---|
| 642 | read in a string and interpret is as a new or changed particle data. |
|---|
| 643 | The possibilities are extensively described above. It is normally |
|---|
| 644 | used indirectly, via <code>Pythia::readString(...)</code> and |
|---|
| 645 | <code>Pythia::readFile(...)</code>. |
|---|
| 646 | <br/><code>argument</code><strong> line </strong> : |
|---|
| 647 | the string to be interpreted as an instruction. |
|---|
| 648 | |
|---|
| 649 | <br/><code>argument</code><strong> warn </strong> (<code>default = <strong>true</strong></code>) : |
|---|
| 650 | write a warning message or not whenever the instruction does not make |
|---|
| 651 | sense, e.g. if the particle does not exist in the database. |
|---|
| 652 | |
|---|
| 653 | <br/><code>argument</code><strong> os </strong> (<code>default = <strong>cout</strong></code>) : |
|---|
| 654 | stream for error printout. |
|---|
| 655 | |
|---|
| 656 | <br/><b>Note:</b> the method returns false if it fails to |
|---|
| 657 | make sense out of the input string. |
|---|
| 658 | |
|---|
| 659 | |
|---|
| 660 | <a name="method9"></a> |
|---|
| 661 | <p/><strong>void ParticleData::listAll(ostream& os = cout) </strong> <br/> |
|---|
| 662 | |
|---|
| 663 | <strong>void ParticleData::listChanged(ostream& os = cout) </strong> <br/> |
|---|
| 664 | |
|---|
| 665 | <strong>void ParticleData::listChangedAndRes(ostream& os = cout) </strong> <br/> |
|---|
| 666 | |
|---|
| 667 | <strong>void ParticleData::list(bool changedOnly = false, bool changedRes = true, ostream& os = cout) </strong> <br/> |
|---|
| 668 | methods intended to present a listing of particle data in a readable |
|---|
| 669 | format. The first three are special cases of the fourth. The first |
|---|
| 670 | lists all particle data, the second only data for those particles that |
|---|
| 671 | were changed after the original creation of the particle data table. |
|---|
| 672 | Resonances are a special case since they can get their data changed |
|---|
| 673 | by being linked to an object that does the calculation of branching |
|---|
| 674 | ratios. The second method does not count such resonances as changed, |
|---|
| 675 | whereas the third does and thus lists all resonances. |
|---|
| 676 | |
|---|
| 677 | |
|---|
| 678 | <a name="method10"></a> |
|---|
| 679 | <p/><strong>void ParticleData::list(int idList, ostream& os = cout) </strong> <br/> |
|---|
| 680 | |
|---|
| 681 | <strong>void ParticleData::list(vector<int> idList, ostream& os = cout) </strong> <br/> |
|---|
| 682 | list particle data for one single particle, with the identity code as |
|---|
| 683 | input, or for a set of particles, with an input vector of identity codes. |
|---|
| 684 | |
|---|
| 685 | |
|---|
| 686 | <a name="method11"></a> |
|---|
| 687 | <p/><strong>void ParticleData::checkTable(ostream& os = cout) </strong> <br/> |
|---|
| 688 | |
|---|
| 689 | <strong>void ParticleData::checkTable(int verbosity,ostream& os = cout) </strong> <br/> |
|---|
| 690 | check that the particle decay table makes sense, especially for decays. |
|---|
| 691 | <br/><code>argument</code><strong> verbosity </strong> : level of checks. 0 is only mininal, |
|---|
| 692 | e.g. if a particle has no open decay channels. 1, which is the level |
|---|
| 693 | of the first method, provides warning if any individual channel is |
|---|
| 694 | closed, except for resonances. 2 also prints the |
|---|
| 695 | branching-ratio-averaged threshold mass. 11 and 12 are like 1 and 2, |
|---|
| 696 | but also include resonances in the detailed checks. |
|---|
| 697 | |
|---|
| 698 | |
|---|
| 699 | |
|---|
| 700 | <a name="method12"></a> |
|---|
| 701 | <p/><strong>void ParticleData::addParticle(int id, string name = " ", int spinType = 0, int chargeType = 0, int colType = 0, double m0 = 0., double mWidth = 0., double mMin = 0., double mMax = 0., double tau0 = 0.) </strong> <br/> |
|---|
| 702 | |
|---|
| 703 | <strong>void ParticleData::addParticle(int id, string name, string antiName, int spinType = 0, int chargeType = 0, int colType = 0, double m0 = 0., double mWidth = 0., double mMin = 0., double mMax = 0., double tau0 = 0.) </strong> <br/> |
|---|
| 704 | add a particle to the decay table; in the first form a partcle which is |
|---|
| 705 | its own antiparticle, in the second where a separate antiparticle exists. |
|---|
| 706 | |
|---|
| 707 | |
|---|
| 708 | <a name="method13"></a> |
|---|
| 709 | <p/><strong>void ParticleData::setAll(int id, string name, string antiName, int spinType = 0, int chargeType = 0, int colType = 0, double m0 = 0., double mWidth = 0., double mMin = 0., double mMax = 0.,double tau0 = 0.) </strong> <br/> |
|---|
| 710 | change all the properties of the particle associated with a given |
|---|
| 711 | identity code. |
|---|
| 712 | |
|---|
| 713 | |
|---|
| 714 | <a name="method14"></a> |
|---|
| 715 | <p/><strong>bool ParticleData::isParticle(int id) </strong> <br/> |
|---|
| 716 | query whether the particle data table contains the particle of the |
|---|
| 717 | identity code. |
|---|
| 718 | |
|---|
| 719 | |
|---|
| 720 | <a name="method15"></a> |
|---|
| 721 | <p/><strong>int ParticleData::nextId(int id) </strong> <br/> |
|---|
| 722 | return the identity code of the sequentially next particle stored in table. |
|---|
| 723 | |
|---|
| 724 | |
|---|
| 725 | <a name="method16"></a> |
|---|
| 726 | <p/><strong>bool ParticleData::hasAnti(int id) </strong> <br/> |
|---|
| 727 | bool whether a distinct antiparticle exists or not. Is true if an |
|---|
| 728 | antiparticle name has been set (and is different from |
|---|
| 729 | <code>void</code>). |
|---|
| 730 | |
|---|
| 731 | |
|---|
| 732 | <a name="method17"></a> |
|---|
| 733 | <p/><strong>void ParticleData::name(int id, string name) </strong> <br/> |
|---|
| 734 | |
|---|
| 735 | <strong>void ParticleData::antiName(int id, string antiName) </strong> <br/> |
|---|
| 736 | |
|---|
| 737 | <strong>void ParticleData::names(int id, string name, string antiName) </strong> <br/> |
|---|
| 738 | |
|---|
| 739 | <strong>string ParticleData::name(int id) </strong> <br/> |
|---|
| 740 | particle and antiparticle names are stored separately, the sign of |
|---|
| 741 | <code>id</code> determines which of the two is returned, with |
|---|
| 742 | <code>void</code> used to indicate the absence of an antiparticle. |
|---|
| 743 | |
|---|
| 744 | |
|---|
| 745 | <a name="method18"></a> |
|---|
| 746 | <p/><strong>void ParticleData::spinType(int id, int spinType) </strong> <br/> |
|---|
| 747 | |
|---|
| 748 | <strong>int ParticleData::spinType(int id) </strong> <br/> |
|---|
| 749 | the spin type, of the form <i>2 s + 1</i>, with special code 0 |
|---|
| 750 | for entries of unknown or indeterminate spin. |
|---|
| 751 | |
|---|
| 752 | |
|---|
| 753 | <a name="method19"></a> |
|---|
| 754 | <p/><strong>void ParticleData::chargeType(int id, int chargeType) </strong> <br/> |
|---|
| 755 | |
|---|
| 756 | <strong>int ParticleData::chargeType(int id) </strong> <br/> |
|---|
| 757 | three times the charge (to make it an integer), taking into account |
|---|
| 758 | the sign of <code>id</code>. |
|---|
| 759 | |
|---|
| 760 | |
|---|
| 761 | <a name="method20"></a> |
|---|
| 762 | <p/><strong>double ParticleData::charge(int id) </strong> <br/> |
|---|
| 763 | the electrical charge of a particle, equal to |
|---|
| 764 | <code>chargeType(id)/3</code>. |
|---|
| 765 | |
|---|
| 766 | |
|---|
| 767 | <a name="method21"></a> |
|---|
| 768 | <p/><strong>void ParticleData::colType(int id, int colType) </strong> <br/> |
|---|
| 769 | |
|---|
| 770 | <strong>int ParticleData::colType(int id) </strong> <br/> |
|---|
| 771 | the colour type, with 0 uncoloured, 1 triplet, -1 antitriplet and 2 |
|---|
| 772 | octet, taking into account the sign of <code>id</code>. |
|---|
| 773 | |
|---|
| 774 | |
|---|
| 775 | <a name="method22"></a> |
|---|
| 776 | <p/><strong>void ParticleData::m0(int id, double m0) </strong> <br/> |
|---|
| 777 | |
|---|
| 778 | <strong>double ParticleData::m0(int id) </strong> <br/> |
|---|
| 779 | the nominal mass <i>m_0</i> (in GeV). |
|---|
| 780 | |
|---|
| 781 | |
|---|
| 782 | <a name="method23"></a> |
|---|
| 783 | <p/><strong>void ParticleData::mWidth(int id, double mWidth) </strong> <br/> |
|---|
| 784 | |
|---|
| 785 | <strong>double ParticleData::mWidth(int id) </strong> <br/> |
|---|
| 786 | the width <i>Gamma</i> of the Breit-Wigner distribution (in GeV). |
|---|
| 787 | |
|---|
| 788 | |
|---|
| 789 | <a name="method24"></a> |
|---|
| 790 | <p/><strong>void ParticleData::mMin(int id, double mMin) </strong> <br/> |
|---|
| 791 | |
|---|
| 792 | <strong>double ParticleData::mMin(int id) </strong> <br/> |
|---|
| 793 | the lower limit of the allowed mass range generated by the Breit-Wigner |
|---|
| 794 | (in GeV). Has no meaning for particles without width, and would |
|---|
| 795 | typically be 0 there. |
|---|
| 796 | |
|---|
| 797 | |
|---|
| 798 | <a name="method25"></a> |
|---|
| 799 | <p/><strong>void ParticleData::mMax(int id, double mMax) </strong> <br/> |
|---|
| 800 | |
|---|
| 801 | <strong>double ParticleData::mMax(int id) </strong> <br/> |
|---|
| 802 | the upper limit of the allowed mass range generated by the Breit-Wigner |
|---|
| 803 | (in GeV). If <i>mMax < mMin</i> then no upper limit is imposed. |
|---|
| 804 | Has no meaning for particles without width, and would typically |
|---|
| 805 | be 0 there. |
|---|
| 806 | |
|---|
| 807 | |
|---|
| 808 | <a name="method26"></a> |
|---|
| 809 | <p/><strong>double ParticleData::m0Min(int id) </strong> <br/> |
|---|
| 810 | similar to <code>mMin()</code> above, except that for particles with |
|---|
| 811 | no width the <code>m0(id)</code> value is returned. |
|---|
| 812 | |
|---|
| 813 | |
|---|
| 814 | <a name="method27"></a> |
|---|
| 815 | <p/><strong>double ParticleData::m0Max(int id) </strong> <br/> |
|---|
| 816 | similar to <code>mMax()</code> above, except that for particles with |
|---|
| 817 | no width the <code>m0(id)</code> value is returned. |
|---|
| 818 | |
|---|
| 819 | |
|---|
| 820 | <a name="method28"></a> |
|---|
| 821 | <p/><strong>void ParticleData::tau0(int id, double tau0) </strong> <br/> |
|---|
| 822 | |
|---|
| 823 | <strong>double ParticleData::tau0(int id) </strong> <br/> |
|---|
| 824 | the nominal proper lifetime <i>tau_0</i> (in mm/c). |
|---|
| 825 | |
|---|
| 826 | |
|---|
| 827 | <a name="method29"></a> |
|---|
| 828 | <p/><strong>void ParticleData::isResonance(int id, bool isResonance) </strong> <br/> |
|---|
| 829 | |
|---|
| 830 | <strong>bool ParticleData::isResonance(int id) </strong> <br/> |
|---|
| 831 | a flag telling whether a particle species are considered as a resonance |
|---|
| 832 | or not. Here <?php $filepath = $_GET["filepath"]; |
|---|
| 833 | echo "<a href='ResonanceDecays.php?filepath=".$filepath."' target='page'>";?>"resonance"</a> |
|---|
| 834 | is used as shorthand for any massive particle |
|---|
| 835 | where the decay process should be counted as part of the hard process |
|---|
| 836 | itself, and thus be performed before showers and other event aspects |
|---|
| 837 | are added. Restrictions on allowed decay channels is also directly |
|---|
| 838 | reflected in the cross section of simulated processes, while those of |
|---|
| 839 | normal hadrons and other light particles are not. |
|---|
| 840 | In practice, it is reserved for states above the <i>b bbar</i> |
|---|
| 841 | bound systems in mass, i.e. for <i>W, Z, t</i>, Higgs states, |
|---|
| 842 | supersymmetric states and (most?) other states in any new theory. |
|---|
| 843 | All particles with <code>m0</code> above 20 GeV are by default |
|---|
| 844 | initialized to be considered as resonances. |
|---|
| 845 | |
|---|
| 846 | |
|---|
| 847 | <a name="method30"></a> |
|---|
| 848 | <p/><strong>void ParticleData::mayDecay(int id, bool mayDecay) </strong> <br/> |
|---|
| 849 | |
|---|
| 850 | <strong>bool ParticleData::mayDecay(int id) </strong> <br/> |
|---|
| 851 | a flag telling whether a particle species may decay or not, offering |
|---|
| 852 | the main user switch. Whether a given particle of this kind then actually |
|---|
| 853 | will decay also depends on it having allowed decay channels, and on |
|---|
| 854 | other flags for <?php $filepath = $_GET["filepath"]; |
|---|
| 855 | echo "<a href='ParticleDecays.php?filepath=".$filepath."' target='page'>";?>particle decays</a>. |
|---|
| 856 | All particles with <code>tau0</code> below 1000 mm are |
|---|
| 857 | by default initialized to allow decays. |
|---|
| 858 | |
|---|
| 859 | |
|---|
| 860 | <a name="method31"></a> |
|---|
| 861 | <p/><strong>void ParticleData::doExternalDecays(int id, bool doExternalDecays) </strong> <br/> |
|---|
| 862 | |
|---|
| 863 | <strong>bool ParticleData::doExternalDecay(int id) </strong> <br/> |
|---|
| 864 | a flag telling whether a particle should be handled by an external |
|---|
| 865 | decay package or not, with the latter default. Can be manipulated as |
|---|
| 866 | described on this page, but should normally not be. Instead the |
|---|
| 867 | <code><?php $filepath = $_GET["filepath"]; |
|---|
| 868 | echo "<a href='ExternalDecays.php?filepath=".$filepath."' target='page'>";?>pythia.decayPtr</a></code> |
|---|
| 869 | method should be provided with the list of relevant particles. |
|---|
| 870 | |
|---|
| 871 | |
|---|
| 872 | <a name="method32"></a> |
|---|
| 873 | <p/><strong>void ParticleData::isVisible(int id, bool isVisible) </strong> <br/> |
|---|
| 874 | |
|---|
| 875 | <strong>bool ParticleData::isVisible(int id) </strong> <br/> |
|---|
| 876 | a flag telling whether a particle species is to be considered as |
|---|
| 877 | visible in a detector or not, as used e.g. in analysis routines. |
|---|
| 878 | By default this includes neutrinos and a few BSM particles |
|---|
| 879 | (gravitino, sneutrinos, neutralinos) that have neither strong nor |
|---|
| 880 | electromagnetic charge, and are not made up of constituents that |
|---|
| 881 | have it. The value of this flag is only relevant if a particle is |
|---|
| 882 | long-lived enough actually to make it to a detector. |
|---|
| 883 | |
|---|
| 884 | |
|---|
| 885 | <a name="method33"></a> |
|---|
| 886 | <p/><strong>void ParticleData::doForceWidth(int id, bool doForceWidth) </strong> <br/> |
|---|
| 887 | |
|---|
| 888 | <strong>bool ParticleData::doForceWidth(int id) </strong> <br/> |
|---|
| 889 | a flag valid only for resonances where PYTHIA contains code to |
|---|
| 890 | calculate the width of the resonance from encoded matrix-element |
|---|
| 891 | expressions, i.e. the <i>Z^0</i>, <i>W^+-</i>, <i>t</i>, |
|---|
| 892 | <i>h^0</i>, and a few more. The normal behaviour (<code>false</code>) |
|---|
| 893 | is then that the width is calculated from the mass, but it is |
|---|
| 894 | possible to <?php $filepath = $_GET["filepath"]; |
|---|
| 895 | echo "<a href='ResonanceDecays.php?filepath=".$filepath."' target='page'>";?>force</a> the resonance |
|---|
| 896 | to retain the nominal width. Branching ratios and the running of the |
|---|
| 897 | total width are unaffected. |
|---|
| 898 | |
|---|
| 899 | |
|---|
| 900 | <a name="method34"></a> |
|---|
| 901 | <p/><strong>void ParticleData::hasChanged(int id, bool hasChanged) </strong> <br/> |
|---|
| 902 | |
|---|
| 903 | <strong>bool ParticleData::hasChanged(int id) </strong> <br/> |
|---|
| 904 | keep track of whether the data for a particle has been changed |
|---|
| 905 | in any respect between initialization and the current status. |
|---|
| 906 | Is used e.g. by the <code>listChanged</code> method to determine |
|---|
| 907 | which particles to list. |
|---|
| 908 | |
|---|
| 909 | |
|---|
| 910 | <a name="method35"></a> |
|---|
| 911 | <p/><strong>bool ParticleData::useBreitWigner(int id) </strong> <br/> |
|---|
| 912 | tells whether a particle will have a Breit-Wigner mass distribution or |
|---|
| 913 | not. Is determined by an internal logic based on the particle width and |
|---|
| 914 | on the value of the |
|---|
| 915 | <code><?php $filepath = $_GET["filepath"]; |
|---|
| 916 | echo "<a href='ParticleData.php?filepath=".$filepath."' target='page'>";?>ParticleData:modeBreitWigner</a></code> |
|---|
| 917 | switch. |
|---|
| 918 | |
|---|
| 919 | |
|---|
| 920 | <a name="method36"></a> |
|---|
| 921 | <p/><strong>double ParticleData::constituentMass(int id) </strong> <br/> |
|---|
| 922 | is the constituent mass for a quark, hardcoded as |
|---|
| 923 | <i>m_u = m_d = 0.325</i>, <i>m_s = 0.50</i>, <i>m_c = 1.60</i> |
|---|
| 924 | and <i>m_b = 5.0</i> GeV, for a diquark the sum of quark constituent |
|---|
| 925 | masses, and for everything else the same as the ordinary mass. |
|---|
| 926 | |
|---|
| 927 | |
|---|
| 928 | <a name="method37"></a> |
|---|
| 929 | <p/><strong>double ParticleData::mass(int id) </strong> <br/> |
|---|
| 930 | returns a mass distributed according to a truncated Breit-Wigner, |
|---|
| 931 | with parameters as described here. Is equal to <code>m0(id)</code> for |
|---|
| 932 | particles without width. |
|---|
| 933 | |
|---|
| 934 | |
|---|
| 935 | <a name="method38"></a> |
|---|
| 936 | <p/><strong>double ParticleData::mRun(int id, double mH) </strong> <br/> |
|---|
| 937 | calculate the running mass of species <code>id</code> when probed at a |
|---|
| 938 | hard mass scale of <code>mH</code>. Only applied to obtain the |
|---|
| 939 | running quark masses; for all other particle the normal fixed mass |
|---|
| 940 | is used. |
|---|
| 941 | |
|---|
| 942 | |
|---|
| 943 | <a name="method39"></a> |
|---|
| 944 | <p/><strong>bool ParticleData::canDecay(int id) </strong> <br/> |
|---|
| 945 | true for a particle with at least one decay channel defined. |
|---|
| 946 | |
|---|
| 947 | |
|---|
| 948 | <a name="method40"></a> |
|---|
| 949 | <p/><strong>bool ParticleData::isLepton(int id) </strong> <br/> |
|---|
| 950 | true for a lepton or an antilepton (including neutrinos). |
|---|
| 951 | |
|---|
| 952 | |
|---|
| 953 | <a name="method41"></a> |
|---|
| 954 | <p/><strong>bool ParticleData::isQuark(int id) </strong> <br/> |
|---|
| 955 | true for a quark or an antiquark. |
|---|
| 956 | |
|---|
| 957 | |
|---|
| 958 | <a name="method42"></a> |
|---|
| 959 | <p/><strong>bool ParticleData::isGluon(int id) </strong> <br/> |
|---|
| 960 | true for a gluon. |
|---|
| 961 | |
|---|
| 962 | |
|---|
| 963 | <a name="method43"></a> |
|---|
| 964 | <p/><strong>bool ParticleData::isDiquark(int id) </strong> <br/> |
|---|
| 965 | true for a diquark or antidiquark. |
|---|
| 966 | |
|---|
| 967 | |
|---|
| 968 | <a name="method44"></a> |
|---|
| 969 | <p/><strong>bool ParticleData::isParton() </strong> <br/> |
|---|
| 970 | true for a gluon, a quark or antiquark up to the b (but excluding top), |
|---|
| 971 | and a diquark or antidiquark consisting of quarks up to the b. |
|---|
| 972 | |
|---|
| 973 | |
|---|
| 974 | <a name="method45"></a> |
|---|
| 975 | <p/><strong>bool ParticleData::isHadron(int id) </strong> <br/> |
|---|
| 976 | true for a hadron (made up out of normal quarks and gluons, |
|---|
| 977 | i.e. not for R-hadrons and other exotic states). |
|---|
| 978 | |
|---|
| 979 | |
|---|
| 980 | <a name="method46"></a> |
|---|
| 981 | <p/><strong>bool ParticleData::isMeson(int id) </strong> <br/> |
|---|
| 982 | true for a meson. |
|---|
| 983 | |
|---|
| 984 | |
|---|
| 985 | <a name="method47"></a> |
|---|
| 986 | <p/><strong>bool ParticleData::isBaryon(int id) </strong> <br/> |
|---|
| 987 | true for a baryon or antibaryon. |
|---|
| 988 | |
|---|
| 989 | |
|---|
| 990 | <a name="method48"></a> |
|---|
| 991 | <p/><strong>bool ParticleData::isOctetHadron(int id) </strong> <br/> |
|---|
| 992 | true for an intermediate hadron-like state with a colour octet charge |
|---|
| 993 | as used in the colour octet model for |
|---|
| 994 | <?php $filepath = $_GET["filepath"]; |
|---|
| 995 | echo "<a href='OniaProcesses.php?filepath=".$filepath."' target='page'>";?>onia</a> production. |
|---|
| 996 | |
|---|
| 997 | |
|---|
| 998 | <a name="method49"></a> |
|---|
| 999 | <p/><strong>int ParticleData::heaviestQuark(int id) </strong> <br/> |
|---|
| 1000 | extracts the heaviest quark or antiquark, i.e. one with largest |
|---|
| 1001 | <code>id</code> number, for a hadron. |
|---|
| 1002 | |
|---|
| 1003 | |
|---|
| 1004 | <a name="method50"></a> |
|---|
| 1005 | <p/><strong>int ParticleData::baryonNumberType(int id) </strong> <br/> |
|---|
| 1006 | is 1 for a quark, 2 for a diquark, 3 for a baryon, the same with a |
|---|
| 1007 | minus sign for antiparticles, and else zero. |
|---|
| 1008 | |
|---|
| 1009 | |
|---|
| 1010 | <a name="method51"></a> |
|---|
| 1011 | <p/><strong>void ParticleData::rescaleBR(int id, double newSumBR = 1.) </strong> <br/> |
|---|
| 1012 | rescales all partial branching ratios by a common factor, such that |
|---|
| 1013 | the sum afterward becomes <code>newSumBR</code>. |
|---|
| 1014 | |
|---|
| 1015 | |
|---|
| 1016 | <a name="method52"></a> |
|---|
| 1017 | <p/><strong>void setResonancePtr(int id, ResonanceWidths* resonancePtr) </strong> <br/> |
|---|
| 1018 | set a pointer for a particle kind to a <code>ResonanceWidths</code> object. |
|---|
| 1019 | This is done, from inside <code>ParticleData::initWidths</code>, only for |
|---|
| 1020 | resonances, i.e. for particles such as <i>Z^0</i>, <i>W^+-</i>, top, |
|---|
| 1021 | Higgs, and new unstable states beyond the Standard Model. The presence |
|---|
| 1022 | of such an object will allow a more dynamic calculation of partial and |
|---|
| 1023 | total widths, as illustrated by the following methods. |
|---|
| 1024 | |
|---|
| 1025 | |
|---|
| 1026 | <a name="method53"></a> |
|---|
| 1027 | <p/><strong>void ParticleData::resInit(int id) </strong> <br/> |
|---|
| 1028 | initialize the treatment of a resonance. |
|---|
| 1029 | |
|---|
| 1030 | |
|---|
| 1031 | <a name="method54"></a> |
|---|
| 1032 | <p/><strong>double ParticleData::resWidth(int id, double mHat, int idInFlav = 0, bool openOnly = false, bool setBR = false) </strong> <br/> |
|---|
| 1033 | calculate the total with for a resonance of a given current mass, |
|---|
| 1034 | optionally including coupling to incoming flavour state (consider |
|---|
| 1035 | the <i>gamma*/Z^0</i> combination), optionally excluding decay |
|---|
| 1036 | channels that have been closed by the user, and optionally storing |
|---|
| 1037 | the results in the normal decay table. |
|---|
| 1038 | |
|---|
| 1039 | |
|---|
| 1040 | <a name="method55"></a> |
|---|
| 1041 | <p/><strong>double ParticleData::resWidthOpen(int id, double mHat, int idInFlav = 0) </strong> <br/> |
|---|
| 1042 | special case of <code>resWidth</code>, where only open channels are |
|---|
| 1043 | included, but results are not stored in the normal decay table. |
|---|
| 1044 | |
|---|
| 1045 | |
|---|
| 1046 | <a name="method56"></a> |
|---|
| 1047 | <p/><strong>double ParticleData::resWidthStore(int id, double mHat, int idInFlav = 0) </strong> <br/> |
|---|
| 1048 | special case of <code>resWidth</code>, where only open channels are |
|---|
| 1049 | included, and results are stored in the normal decay table. |
|---|
| 1050 | |
|---|
| 1051 | |
|---|
| 1052 | <a name="method57"></a> |
|---|
| 1053 | <p/><strong>double ParticleData::resOpenFrac(int id1, int id2 = 0, int id3 = 0) </strong> <br/> |
|---|
| 1054 | calculate the fraction of the full branching ratio that is left |
|---|
| 1055 | open by the user choice of allowed decay channels. Can be applied |
|---|
| 1056 | to a final state with up to three resonances. Since the procedure |
|---|
| 1057 | is multiplicative, it would be easy to generalize also to more. |
|---|
| 1058 | |
|---|
| 1059 | |
|---|
| 1060 | <a name="method58"></a> |
|---|
| 1061 | <p/><strong>double ParticleData::resWidthRescaleFactor(int id) </strong> <br/> |
|---|
| 1062 | the factor used to rescale all partial widths in case the total |
|---|
| 1063 | width is being forced to a specific value by the user. |
|---|
| 1064 | |
|---|
| 1065 | |
|---|
| 1066 | <a name="method59"></a> |
|---|
| 1067 | <p/><strong>double ParticleData::resWidthChan(int id,double mHat, int idAbs1 = 0, int idAbs2 = 0) </strong> <br/> |
|---|
| 1068 | special case to calculate one final-state width; currently only used |
|---|
| 1069 | for Higgs decay to <i>q qbar</i>, <i>g g</i> or |
|---|
| 1070 | <i>gamma gamma</i>. |
|---|
| 1071 | |
|---|
| 1072 | |
|---|
| 1073 | <a name="method60"></a> |
|---|
| 1074 | <p/><strong>ParticleDataEntry* ParticleData::particleDataEntryPtr(int id) </strong> <br/> |
|---|
| 1075 | returns a pointer to the <code>ParticleDataEntry</code> object. |
|---|
| 1076 | The methods in the next section can then be used to manipulate |
|---|
| 1077 | this object. |
|---|
| 1078 | |
|---|
| 1079 | |
|---|
| 1080 | <h3>The ParticleDataEntry methods</h3> |
|---|
| 1081 | |
|---|
| 1082 | Most of the methods that can be applied to a single |
|---|
| 1083 | <code>ParticleDataEntry</code> object are almost identical with |
|---|
| 1084 | those used above for the <code>ParticleData</code>, except |
|---|
| 1085 | that the <code>id</code> argument is no longer needed to find |
|---|
| 1086 | the right entry in the table. By and large, this makes direct |
|---|
| 1087 | access to the <code>ParticleDataEntry</code> methods superfluous. |
|---|
| 1088 | There are a few methods that are unique to each class, however. |
|---|
| 1089 | Furthermore, to avoid some naming ambiguities, many methods that |
|---|
| 1090 | set values begin with <code>set</code>. |
|---|
| 1091 | |
|---|
| 1092 | <a name="method61"></a> |
|---|
| 1093 | <p/><strong>ParticleDataEntry::ParticleDataEntry(int id = 0, string name = " ", int spinType = 0, int chargeType = 0, int colType = 0, double m0 = 0., double mWidth = 0., double mMin = 0., double mMax = 0., double tau0 = 0.) </strong> <br/> |
|---|
| 1094 | |
|---|
| 1095 | <strong>ParticleDataEntry::ParticleDataEntry(int id, string name, string antiName, int spinType = 0, int chargeType = 0, int colType = 0, double m0 = 0., double mWidth = 0., double mMin = 0., double mMax = 0., double tau0 = 0.) </strong> <br/> |
|---|
| 1096 | there are two alternative constructors, that both expect the |
|---|
| 1097 | properties of a particle as input. The first assumes that there |
|---|
| 1098 | is only one particle, thet latter that there is a |
|---|
| 1099 | particle-antiparticle pair (but if the antiparticle name is |
|---|
| 1100 | <code>void</code> one reverts back to the particle-only case). |
|---|
| 1101 | |
|---|
| 1102 | |
|---|
| 1103 | <a name="method62"></a> |
|---|
| 1104 | <p/><strong>ParticleDataEntry::~ParticleDataEntry </strong> <br/> |
|---|
| 1105 | the destructor is needed to delete any <code>ResonanceWidths</code> |
|---|
| 1106 | objects that have been created and linked to the respective particle. |
|---|
| 1107 | |
|---|
| 1108 | |
|---|
| 1109 | <a name="method63"></a> |
|---|
| 1110 | <p/><strong>void ParticleDataEntry::setDefaults() </strong> <br/> |
|---|
| 1111 | initialize some particle flags with default values, e.g. whether |
|---|
| 1112 | a particle is a resonance, may decay, or is visible. Is called from the |
|---|
| 1113 | constructors and from <code>setAll</code>. |
|---|
| 1114 | |
|---|
| 1115 | |
|---|
| 1116 | <a name="method64"></a> |
|---|
| 1117 | <p/><strong>void ParticleDataEntry::initPtr(ParticleData* particleDataPtrIn) </strong> <br/> |
|---|
| 1118 | initialize pointer back to the whole database (so that masses of |
|---|
| 1119 | decay products can be accessed, e.g.). |
|---|
| 1120 | |
|---|
| 1121 | |
|---|
| 1122 | <a name="method65"></a> |
|---|
| 1123 | <p/><strong>void ParticleDataEntry::setAll( string name, string antiName, int spinType = 0, int chargeType = 0, int colType = 0, double m0 = 0., double mWidth = 0., double mMin = 0., double mMax = 0.,double tau0 = 0.) </strong> <br/> |
|---|
| 1124 | change all the properties of the particle associated with a given |
|---|
| 1125 | identity code. |
|---|
| 1126 | |
|---|
| 1127 | |
|---|
| 1128 | <a name="method66"></a> |
|---|
| 1129 | <p/><strong>int ParticleDataEntry::id() </strong> <br/> |
|---|
| 1130 | the PDG identity code. |
|---|
| 1131 | |
|---|
| 1132 | |
|---|
| 1133 | <a name="method67"></a> |
|---|
| 1134 | <p/><strong>bool ParticleDataEntry::hasAnti() </strong> <br/> |
|---|
| 1135 | tell whether a separate antiparticle exists. |
|---|
| 1136 | |
|---|
| 1137 | |
|---|
| 1138 | <a name="method68"></a> |
|---|
| 1139 | <p/><strong>void ParticleDataEntry::setName(string name) </strong> <br/> |
|---|
| 1140 | |
|---|
| 1141 | <strong>void ParticleDataEntry::setAntiName(string antiName) </strong> <br/> |
|---|
| 1142 | |
|---|
| 1143 | <strong>void ParticleDataEntry::setNames(string name,string antiName) </strong> <br/> |
|---|
| 1144 | |
|---|
| 1145 | <strong>string ParticleDataEntry::name(int id = 1) </strong> <br/> |
|---|
| 1146 | set or get the particle or antiparticle name. Only the sign of |
|---|
| 1147 | <code>id</code> is needed to distinguish particle/antiparticle. |
|---|
| 1148 | |
|---|
| 1149 | |
|---|
| 1150 | <a name="method69"></a> |
|---|
| 1151 | <p/><strong>void ParticleDataEntry::setSpinType(int spinType) </strong> <br/> |
|---|
| 1152 | |
|---|
| 1153 | <strong>int ParticleDataEntry::spinType() </strong> <br/> |
|---|
| 1154 | set or get the particle spin type, i.e. <i>2 s + 1</i>, or 0 in some |
|---|
| 1155 | special cases. |
|---|
| 1156 | |
|---|
| 1157 | |
|---|
| 1158 | <a name="method70"></a> |
|---|
| 1159 | <p/><strong>void ParticleDataEntry::setChargeType(int chargeType) </strong> <br/> |
|---|
| 1160 | |
|---|
| 1161 | <strong>int ParticleDataEntry::chargeType(int id = 1) </strong> <br/> |
|---|
| 1162 | |
|---|
| 1163 | <strong>double ParticleDataEntry::charge(int id = 1) </strong> <br/> |
|---|
| 1164 | set or get the particle charge type, i.e. three times the charge, |
|---|
| 1165 | or the charge itself. Only the sign of <code>id</code> is needed |
|---|
| 1166 | to distinguish particle/antiparticle. |
|---|
| 1167 | |
|---|
| 1168 | |
|---|
| 1169 | <a name="method71"></a> |
|---|
| 1170 | <p/><strong>void ParticleDataEntry::setColType(int colType) </strong> <br/> |
|---|
| 1171 | |
|---|
| 1172 | <strong>int ParticleDataEntry::colType(int id = 1) </strong> <br/> |
|---|
| 1173 | set or get the particle colour type, 0 for singlet, 1 for triplet, |
|---|
| 1174 | -1 for antitriplet, 2 for octet. Only the sign of <code>id</code> |
|---|
| 1175 | is needed to distinguish particle/antiparticle. |
|---|
| 1176 | |
|---|
| 1177 | |
|---|
| 1178 | <a name="method72"></a> |
|---|
| 1179 | <p/><strong>void ParticleDataEntry::setM0(double m0) </strong> <br/> |
|---|
| 1180 | |
|---|
| 1181 | <strong>double ParticleDataEntry::m0() </strong> <br/> |
|---|
| 1182 | the nominal mass <i>m_0</i> (in GeV). |
|---|
| 1183 | |
|---|
| 1184 | |
|---|
| 1185 | <a name="method73"></a> |
|---|
| 1186 | <p/><strong>void ParticleDataEntry::setMWidth(double mWidth) </strong> <br/> |
|---|
| 1187 | |
|---|
| 1188 | <strong>double ParticleDataEntry::mWidth() </strong> <br/> |
|---|
| 1189 | the width <i>Gamma</i> of the Breit-Wigner distribution (in GeV). |
|---|
| 1190 | |
|---|
| 1191 | |
|---|
| 1192 | <a name="method74"></a> |
|---|
| 1193 | <p/><strong>void ParticleDataEntry::setMMin(double mMin) </strong> <br/> |
|---|
| 1194 | |
|---|
| 1195 | <strong>double ParticleDataEntry::mMin() </strong> <br/> |
|---|
| 1196 | the lower limit of the allowed mass range generated by the Breit-Wigner |
|---|
| 1197 | (in GeV). Has no meaning for particles without width, and would |
|---|
| 1198 | typically be 0 there. |
|---|
| 1199 | |
|---|
| 1200 | |
|---|
| 1201 | <a name="method75"></a> |
|---|
| 1202 | <p/><strong>void ParticleDataEntry::setMMax(double mMax) </strong> <br/> |
|---|
| 1203 | |
|---|
| 1204 | <strong>double ParticleDataEntry::mMax() </strong> <br/> |
|---|
| 1205 | the upper limit of the allowed mass range generated by the Breit-Wigner |
|---|
| 1206 | (in GeV). If <i>mMax < mMin</i> then no upper limit is imposed. |
|---|
| 1207 | Has no meaning for particles without width, and would typically |
|---|
| 1208 | be 0 there. |
|---|
| 1209 | |
|---|
| 1210 | |
|---|
| 1211 | <a name="method76"></a> |
|---|
| 1212 | <p/><strong>double ParticleDataEntry::m0Min() </strong> <br/> |
|---|
| 1213 | similar to <code>mMin()</code> above, except that for particles with |
|---|
| 1214 | no width the <code>m0(id)</code> value is returned. |
|---|
| 1215 | |
|---|
| 1216 | |
|---|
| 1217 | <a name="method77"></a> |
|---|
| 1218 | <p/><strong>double ParticleDataEntry::m0Max() </strong> <br/> |
|---|
| 1219 | similar to <code>mMax()</code> above, except that for particles with |
|---|
| 1220 | no width the <code>m0(id)</code> value is returned. |
|---|
| 1221 | |
|---|
| 1222 | |
|---|
| 1223 | <a name="method78"></a> |
|---|
| 1224 | <p/><strong>void ParticleDataEntry::setTau0(double tau0) </strong> <br/> |
|---|
| 1225 | |
|---|
| 1226 | <strong>double ParticleDataEntry::tau0() </strong> <br/> |
|---|
| 1227 | the nominal proper lifetime <i>tau_0</i> (in mm/c). |
|---|
| 1228 | |
|---|
| 1229 | |
|---|
| 1230 | <a name="method79"></a> |
|---|
| 1231 | <p/><strong>void ParticleDataEntry::setIsResonance(bool isResonance) </strong> <br/> |
|---|
| 1232 | |
|---|
| 1233 | <strong>bool ParticleDataEntry::isResonance() </strong> <br/> |
|---|
| 1234 | a flag telling whether a particle species are considered as a resonance |
|---|
| 1235 | or not. Here <?php $filepath = $_GET["filepath"]; |
|---|
| 1236 | echo "<a href='ResonanceDecays.php?filepath=".$filepath."' target='page'>";?>"resonance"</a> |
|---|
| 1237 | is used as shorthand for any massive particle |
|---|
| 1238 | where the decay process should be counted as part of the hard process |
|---|
| 1239 | itself, and thus be performed before showers and other event aspects |
|---|
| 1240 | are added. Restrictions on allowed decay channels is also directly |
|---|
| 1241 | reflected in the cross section of simulated processes, while those of |
|---|
| 1242 | normal hadrons and other light particles are not. |
|---|
| 1243 | In practice, it is reserved for states above the <i>b bbar</i> |
|---|
| 1244 | bound systems in mass, i.e. for <i>W, Z, t</i>, Higgs states, |
|---|
| 1245 | supersymmetric states and (most?) other states in any new theory. |
|---|
| 1246 | All particles with <code>m0</code> above 20 GeV are by default |
|---|
| 1247 | initialized to be considered as resonances. |
|---|
| 1248 | |
|---|
| 1249 | |
|---|
| 1250 | <a name="method80"></a> |
|---|
| 1251 | <p/><strong>void ParticleDataEntry::setMayDecay(bool mayDecay) </strong> <br/> |
|---|
| 1252 | |
|---|
| 1253 | <strong>bool ParticleDataEntry::mayDecay() </strong> <br/> |
|---|
| 1254 | a flag telling whether a particle species may decay or not, offering |
|---|
| 1255 | the main user switch. Whether a given particle of this kind then actually |
|---|
| 1256 | will decay also depends on it having allowed decay channels, and on |
|---|
| 1257 | other flags for <?php $filepath = $_GET["filepath"]; |
|---|
| 1258 | echo "<a href='ParticleDecays.php?filepath=".$filepath."' target='page'>";?>particle decays</a>. |
|---|
| 1259 | All particles with <code>tau0</code> below 1000 mm are |
|---|
| 1260 | by default initialized to allow decays. |
|---|
| 1261 | |
|---|
| 1262 | |
|---|
| 1263 | <a name="method81"></a> |
|---|
| 1264 | <p/><strong>void ParticleDataEntry::setDoExternalDecays(bool doExternalDecays) </strong> <br/> |
|---|
| 1265 | |
|---|
| 1266 | <strong>bool ParticleDataEntry::doExternalDecay() </strong> <br/> |
|---|
| 1267 | a flag telling whether a particle should be handled by an external |
|---|
| 1268 | decay package or not, with the latter default. Can be manipulated as |
|---|
| 1269 | described on this page, but should normally not be. Instead the |
|---|
| 1270 | <code><?php $filepath = $_GET["filepath"]; |
|---|
| 1271 | echo "<a href='ExternalDecays.php?filepath=".$filepath."' target='page'>";?>pythia.decayPtr</a></code> |
|---|
| 1272 | method should be provided with the list of relevant particles. |
|---|
| 1273 | |
|---|
| 1274 | |
|---|
| 1275 | <a name="method82"></a> |
|---|
| 1276 | <p/><strong>void ParticleDataEntry::setIsVisible(bool isVisible) </strong> <br/> |
|---|
| 1277 | |
|---|
| 1278 | <strong>bool ParticleDataEntry::isVisible() </strong> <br/> |
|---|
| 1279 | a flag telling whether a particle species is to be considered as |
|---|
| 1280 | visible in a detector or not, as used e.g. in analysis routines. |
|---|
| 1281 | By default this includes neutrinos and a few BSM particles |
|---|
| 1282 | (gravitino, sneutrinos, neutralinos) that have neither strong nor |
|---|
| 1283 | electromagnetic charge, and are not made up of constituents that |
|---|
| 1284 | have it. The value of this flag is only relevant if a particle is |
|---|
| 1285 | long-lived enough actually to make it to a detector. |
|---|
| 1286 | |
|---|
| 1287 | |
|---|
| 1288 | <a name="method83"></a> |
|---|
| 1289 | <p/><strong>void ParticleDataEntry::setDoForceWidth(bool doForceWidth) </strong> <br/> |
|---|
| 1290 | |
|---|
| 1291 | <strong>bool ParticleDataEntry::doForceWidth() </strong> <br/> |
|---|
| 1292 | a flag valid only for resonances where PYTHIA contains code to |
|---|
| 1293 | calculate the width of the resonance from encoded matrix-element |
|---|
| 1294 | expressions, i.e. the <i>Z^0</i>, <i>W^+-</i>, <i>t</i>, |
|---|
| 1295 | <i>h^0</i>, and a few more. The normal behaviour (<code>false</code>) |
|---|
| 1296 | is then that the width is calculated from the mass, but it is |
|---|
| 1297 | possible to <?php $filepath = $_GET["filepath"]; |
|---|
| 1298 | echo "<a href='ResonanceDecays.php?filepath=".$filepath."' target='page'>";?>force</a> the resonance |
|---|
| 1299 | to retain the nominal width. Branching ratios and the running of the |
|---|
| 1300 | total width are unaffected. |
|---|
| 1301 | |
|---|
| 1302 | |
|---|
| 1303 | <a name="method84"></a> |
|---|
| 1304 | <p/><strong>void ParticleDataEntry::setHasChanged(bool hasChanged) </strong> <br/> |
|---|
| 1305 | |
|---|
| 1306 | <a name="method85"></a> |
|---|
| 1307 | <p/><strong>void ParticleDataEntry::hasChanged(bool hasChanged) </strong> <br/> |
|---|
| 1308 | keep track of whether the data for a particle has been changed |
|---|
| 1309 | in any respect between initialization and the current status. |
|---|
| 1310 | Is used e.g. by the <code>ParticleData::listChanged</code> method |
|---|
| 1311 | to determine which particles to list. |
|---|
| 1312 | |
|---|
| 1313 | |
|---|
| 1314 | <a name="method86"></a> |
|---|
| 1315 | <p/><strong>void ParticleDataEntry::initBWmass() </strong> <br/> |
|---|
| 1316 | Prepare the Breit-Wigner mass selection by precalculating |
|---|
| 1317 | frequently-used expressions. |
|---|
| 1318 | |
|---|
| 1319 | |
|---|
| 1320 | <a name="method87"></a> |
|---|
| 1321 | <p/><strong>double ParticleDataEntry::constituentMass() </strong> <br/> |
|---|
| 1322 | is the constituent mass for a quark, hardcoded as |
|---|
| 1323 | <i>m_u = m_d = 0.325</i>, <i>m_s = 0.50</i>, <i>m_c = 1.60</i> |
|---|
| 1324 | and <i>m_b = 5.0</i> GeV, for a diquark the sum of quark constituent |
|---|
| 1325 | masses, and for everything else the same as the ordinary mass. |
|---|
| 1326 | |
|---|
| 1327 | |
|---|
| 1328 | <a name="method88"></a> |
|---|
| 1329 | <p/><strong>double ParticleDataEntry::mass() </strong> <br/> |
|---|
| 1330 | give the mass of a particle, either at the nominal value |
|---|
| 1331 | or picked according to a (linear or quadratic) Breit-Wigner. |
|---|
| 1332 | |
|---|
| 1333 | |
|---|
| 1334 | <a name="method89"></a> |
|---|
| 1335 | <p/><strong>double ParticleDataEntry::mRun(double mH) </strong> <br/> |
|---|
| 1336 | calculate the running quark mass at a hard scale <code>mH</code>. |
|---|
| 1337 | For other particles the on-shell mass is given. |
|---|
| 1338 | |
|---|
| 1339 | |
|---|
| 1340 | <a name="method90"></a> |
|---|
| 1341 | <p/><strong>bool ParticleDataEntry::useBreitWigner() </strong> <br/> |
|---|
| 1342 | tells whether a particle will have a Breit-Wigner mass distribution or |
|---|
| 1343 | not. Is determined by an internal logic based on the particle width and |
|---|
| 1344 | on the value of the <code><?php $filepath = $_GET["filepath"]; |
|---|
| 1345 | echo "<a href='ParticleData.php?filepath=".$filepath."' target='page'>";?> |
|---|
| 1346 | ParticleData:modeBreitWigner</a></code> switch. |
|---|
| 1347 | |
|---|
| 1348 | |
|---|
| 1349 | <a name="method91"></a> |
|---|
| 1350 | <p/><strong>bool ParticleDataEntry::canDecay(int id) </strong> <br/> |
|---|
| 1351 | true for a particle with at least one decay channel defined. |
|---|
| 1352 | |
|---|
| 1353 | |
|---|
| 1354 | <a name="method92"></a> |
|---|
| 1355 | <p/><strong>bool ParticleDataEntry::isLepton() </strong> <br/> |
|---|
| 1356 | true for a lepton or an antilepton (including neutrinos). |
|---|
| 1357 | |
|---|
| 1358 | |
|---|
| 1359 | <a name="method93"></a> |
|---|
| 1360 | <p/><strong>bool ParticleDataEntry::isQuark() </strong> <br/> |
|---|
| 1361 | true for a quark or an antiquark. |
|---|
| 1362 | |
|---|
| 1363 | |
|---|
| 1364 | <a name="method94"></a> |
|---|
| 1365 | <p/><strong>bool ParticleDataEntry::isGluon() </strong> <br/> |
|---|
| 1366 | true for a gluon. |
|---|
| 1367 | |
|---|
| 1368 | |
|---|
| 1369 | <a name="method95"></a> |
|---|
| 1370 | <p/><strong>bool ParticleDataEntry::isDiquark() </strong> <br/> |
|---|
| 1371 | true for a diquark or antidiquark. |
|---|
| 1372 | |
|---|
| 1373 | |
|---|
| 1374 | <a name="method96"></a> |
|---|
| 1375 | <p/><strong>bool ParticleDataEntry::isParton() </strong> <br/> |
|---|
| 1376 | true for a gluon, a quark or antiquark up to the b (but excluding top), |
|---|
| 1377 | and a diquark or antidiquark consisting of quarks up to the b. |
|---|
| 1378 | |
|---|
| 1379 | |
|---|
| 1380 | <a name="method97"></a> |
|---|
| 1381 | <p/><strong>bool ParticleDataEntry::isHadron() </strong> <br/> |
|---|
| 1382 | true for a hadron (made up out of normal quarks and gluons, |
|---|
| 1383 | i.e. not for R-hadrons and other exotic states). |
|---|
| 1384 | |
|---|
| 1385 | |
|---|
| 1386 | <a name="method98"></a> |
|---|
| 1387 | <p/><strong>bool ParticleDataEntry::isMeson() </strong> <br/> |
|---|
| 1388 | true for a meson. |
|---|
| 1389 | |
|---|
| 1390 | |
|---|
| 1391 | <a name="method99"></a> |
|---|
| 1392 | <p/><strong>bool ParticleDataEntry::isBaryon() </strong> <br/> |
|---|
| 1393 | true for a baryon or antibaryon. |
|---|
| 1394 | |
|---|
| 1395 | |
|---|
| 1396 | <a name="method100"></a> |
|---|
| 1397 | <p/><strong>bool ParticleDataEntry::isOctetHadron() </strong> <br/> |
|---|
| 1398 | true for an intermediate hadron-like state with a colour octet charge |
|---|
| 1399 | as used in the colour octet model for |
|---|
| 1400 | <?php $filepath = $_GET["filepath"]; |
|---|
| 1401 | echo "<a href='OniaProcesses.php?filepath=".$filepath."' target='page'>";?>onia</a> production. |
|---|
| 1402 | |
|---|
| 1403 | |
|---|
| 1404 | <a name="method101"></a> |
|---|
| 1405 | <p/><strong>int ParticleDataEntry::heaviestQuark(int id) </strong> <br/> |
|---|
| 1406 | extracts the heaviest quark or antiquark, i.e. one with largest |
|---|
| 1407 | <code>id</code> number, for a hadron. Only the sign of the input |
|---|
| 1408 | argument is relevant. |
|---|
| 1409 | |
|---|
| 1410 | |
|---|
| 1411 | <a name="method102"></a> |
|---|
| 1412 | <p/><strong>int ParticleDataEntry::baryonNumberType(int id) </strong> <br/> |
|---|
| 1413 | is 1 for a quark, 2 for a diquark, 3 for a baryon, the same with a |
|---|
| 1414 | minus sign for antiparticles, and else zero. Only the sign of the |
|---|
| 1415 | input argument is relevant. |
|---|
| 1416 | |
|---|
| 1417 | |
|---|
| 1418 | <a name="method103"></a> |
|---|
| 1419 | <p/><strong>void ParticleDataEntry::clearChannels() </strong> <br/> |
|---|
| 1420 | resets to an empty decay table. |
|---|
| 1421 | |
|---|
| 1422 | |
|---|
| 1423 | <a name="method104"></a> |
|---|
| 1424 | <p/><strong>void ParticleDataEntry::addChannel(int onMode = 0, double bRatio = 0., int meMode = 0, int prod0 = 0, int prod1 = 0,int prod2 = 0, int prod3 = 0, int prod4 = 0, int prod5 = 0, int prod6 = 0, int prod7 = 0,) </strong> <br/> |
|---|
| 1425 | adds a decay channel with up to 8 products. |
|---|
| 1426 | |
|---|
| 1427 | |
|---|
| 1428 | <a name="method105"></a> |
|---|
| 1429 | <p/><strong>int ParticleDataEntry::sizeChannels() </strong> <br/> |
|---|
| 1430 | returns the number of decay channels for a particle. |
|---|
| 1431 | |
|---|
| 1432 | |
|---|
| 1433 | <a name="method106"></a> |
|---|
| 1434 | <p/><strong>DecayChannel& ParticleDataEntry::channel(int i) </strong> <br/> |
|---|
| 1435 | |
|---|
| 1436 | <strong>const DecayChannel& ParticleDataEntry::channel(int i) </strong> <br/> |
|---|
| 1437 | gain access to a specified channel in the decay table. |
|---|
| 1438 | |
|---|
| 1439 | |
|---|
| 1440 | <a name="method107"></a> |
|---|
| 1441 | <p/><strong>void ParticleDataEntry::rescaleBR(double newSumBR = 1.) </strong> <br/> |
|---|
| 1442 | rescales all partial branching ratios by a common factor, such that |
|---|
| 1443 | the sum afterward becomes <code>newSumBR</code>. |
|---|
| 1444 | |
|---|
| 1445 | |
|---|
| 1446 | <a name="method108"></a> |
|---|
| 1447 | <p/><strong>bool ParticleDataEntry::preparePick(int idSgn, double mHat = 0., int idInFlav = 0) </strong> <br/> |
|---|
| 1448 | prepare to pick a decay channel. |
|---|
| 1449 | |
|---|
| 1450 | |
|---|
| 1451 | <a name="method109"></a> |
|---|
| 1452 | <p/><strong>DecayChannel& ParticleDataEntry::pickChannel() </strong> <br/> |
|---|
| 1453 | pick a decay channel according to branching ratios from |
|---|
| 1454 | <code>preparePick</code>. |
|---|
| 1455 | |
|---|
| 1456 | |
|---|
| 1457 | <a name="method110"></a> |
|---|
| 1458 | <p/><strong>void ParticleDataEntry::setResonancePtr(ResonanceWidths* resonancePtr) </strong> <br/> |
|---|
| 1459 | |
|---|
| 1460 | <strong>ResonanceWidths* ParticleDataEntry::getResonancePtr() </strong> <br/> |
|---|
| 1461 | set or get a pointer to an object that can be used for dynamic calculation |
|---|
| 1462 | of partial and total resonance widths. Here a resonance is a particle |
|---|
| 1463 | such as top, <i>Z^0</i>, <i>W^+-</i>, Higgs, and new unstable states |
|---|
| 1464 | beyond the Standard Model. |
|---|
| 1465 | |
|---|
| 1466 | |
|---|
| 1467 | <a name="method111"></a> |
|---|
| 1468 | <p/><strong>void ParticleDataEntry::resInit(Info* infoPtrIn, Settings* settingsPtrIn, ParticleData* particleDataPtrIn, CoupSM* coupSMPtrIn) </strong> <br/> |
|---|
| 1469 | initialize the treatment of a resonance. |
|---|
| 1470 | |
|---|
| 1471 | |
|---|
| 1472 | <a name="method112"></a> |
|---|
| 1473 | <p/><strong>double ParticleDataEntry::resWidth(int idSgn,double mHat, int idInFlav = 0, bool openOnly = false, bool setBR = false) </strong> <br/> |
|---|
| 1474 | calculate the total with for a resonance of a given current mass, |
|---|
| 1475 | optionally including coupling to incoming flavour state (consider |
|---|
| 1476 | the <i>gamma*/Z^0</i> combination), optionally excluding decay |
|---|
| 1477 | channels that have been closed by the user, and optionally storing |
|---|
| 1478 | the results in the normal decay table. For the first argument only |
|---|
| 1479 | the sign is relevant. |
|---|
| 1480 | |
|---|
| 1481 | |
|---|
| 1482 | <a name="method113"></a> |
|---|
| 1483 | <p/><strong>double ParticleDataEntry::resWidthOpen(int idSgn,double mHat, int idInFlav = 0) </strong> <br/> |
|---|
| 1484 | special case of <code>resWidth</code>, where only open channels are |
|---|
| 1485 | included, but results are not stored in the normal decay table. |
|---|
| 1486 | |
|---|
| 1487 | |
|---|
| 1488 | <a name="method114"></a> |
|---|
| 1489 | <p/><strong>double ParticleDataEntry::resWidthStore(int idSgn,double mHat, int idInFlav = 0) </strong> <br/> |
|---|
| 1490 | special case of <code>resWidth</code>, where only open channels are |
|---|
| 1491 | included, and results are stored in the normal decay table. |
|---|
| 1492 | |
|---|
| 1493 | |
|---|
| 1494 | <a name="method115"></a> |
|---|
| 1495 | <p/><strong>double ParticleDataEntry::resOpenFrac(int idSgn) </strong> <br/> |
|---|
| 1496 | calculate the fraction of the full branching ratio that is left |
|---|
| 1497 | open by the user choice of allowed decay channels. |
|---|
| 1498 | |
|---|
| 1499 | |
|---|
| 1500 | <a name="method116"></a> |
|---|
| 1501 | <p/><strong>double ParticleDataEntry::resWidthRescaleFactor() </strong> <br/> |
|---|
| 1502 | the factor used to rescale all partial widths in case the total |
|---|
| 1503 | width is being forced to a specific value by the user. |
|---|
| 1504 | |
|---|
| 1505 | |
|---|
| 1506 | <a name="method117"></a> |
|---|
| 1507 | <p/><strong>double ParticleDataEntry::resWidthChan(double mHat, int idAbs1 = 0, int idAbs2 = 0) </strong> <br/> |
|---|
| 1508 | special case to calculate one final-state width; currently only used |
|---|
| 1509 | for Higgs decay to <i>q qbar</i>, <i>g g</i> or |
|---|
| 1510 | <i>gamma gamma</i>. |
|---|
| 1511 | |
|---|
| 1512 | |
|---|
| 1513 | <h3>The DecayChannel methods</h3> |
|---|
| 1514 | |
|---|
| 1515 | The properties stored in an individual decay channel can be set or get |
|---|
| 1516 | by the methods in this section. |
|---|
| 1517 | |
|---|
| 1518 | <a name="method118"></a> |
|---|
| 1519 | <p/><strong>DecayChannel::DecayChannel(int onMode = 0, double bRatio = 0., int meMode = 0, int prod0 = 0, int prod1 = 0, int prod2 = 0, int prod3 = 0, int prod4 = 0, int prod5 = 0, int prod6 = 0, int prod7 = 0) </strong> <br/> |
|---|
| 1520 | the constructor for a decay channel. Internal. |
|---|
| 1521 | |
|---|
| 1522 | |
|---|
| 1523 | <a name="method119"></a> |
|---|
| 1524 | <p/><strong>void DecayChannel::onMode(int onMode) </strong> <br/> |
|---|
| 1525 | |
|---|
| 1526 | <strong>int DecayChannel::onMode() </strong> <br/> |
|---|
| 1527 | set or get the <code>onMode</code> of a decay channel,<br/> |
|---|
| 1528 | 0 if a channel is off,<br/> |
|---|
| 1529 | 1 if on,<br/> |
|---|
| 1530 | 2 if on for a particle but off for an antiparticle,<br/> |
|---|
| 1531 | 3 if on for an antiparticle but off for a particle.<br/> |
|---|
| 1532 | If a particle is its own antiparticle then 2 is on and 3 off |
|---|
| 1533 | but, of course, for such particles it is much simpler and safer |
|---|
| 1534 | to use only 1 and 0.<br/> |
|---|
| 1535 | The 2 and 3 options can be used e.g. to encode CP violation in |
|---|
| 1536 | B decays, or to let the <i>W</i>'s in a <i>q qbar -> W^+ W^-</i> |
|---|
| 1537 | process decay in different channels. |
|---|
| 1538 | |
|---|
| 1539 | |
|---|
| 1540 | <a name="method120"></a> |
|---|
| 1541 | <p/><strong>void DecayChannel::bRatio(double bRatio, bool countAsChanged = true) </strong> <br/> |
|---|
| 1542 | |
|---|
| 1543 | <strong>double DecayChannel::bRatio() </strong> <br/> |
|---|
| 1544 | set or get the branching ratio of the channel. Second argument only |
|---|
| 1545 | for internal use. |
|---|
| 1546 | |
|---|
| 1547 | |
|---|
| 1548 | <a name="method121"></a> |
|---|
| 1549 | <p/><strong>void DecayChannel::rescaleBR(double fac) </strong> <br/> |
|---|
| 1550 | multiply the current branching ratio by <code>fac</code>. |
|---|
| 1551 | |
|---|
| 1552 | |
|---|
| 1553 | <a name="method122"></a> |
|---|
| 1554 | <p/><strong>void DecayChannel::meMode(int meMode) </strong> <br/> |
|---|
| 1555 | |
|---|
| 1556 | <strong>int DecayChannel::meMode() </strong> <br/> |
|---|
| 1557 | set or get the mode of processing this channel, possibly with matrix |
|---|
| 1558 | elements (see the <?php $filepath = $_GET["filepath"]; |
|---|
| 1559 | echo "<a href='ParticleDecays.php?filepath=".$filepath."' target='page'>";?>particle decays</a> |
|---|
| 1560 | description). |
|---|
| 1561 | |
|---|
| 1562 | |
|---|
| 1563 | <a name="method123"></a> |
|---|
| 1564 | <p/><strong>void DecayChannel::multiplicity(int multiplicity) </strong> <br/> |
|---|
| 1565 | |
|---|
| 1566 | <strong>int DecayChannel::multiplicity() </strong> <br/> |
|---|
| 1567 | set or get the number of decay products in a channel, at most 8. |
|---|
| 1568 | (Is normally not to be set by hand, since it is automatically |
|---|
| 1569 | updated whenever the products list is changed.) |
|---|
| 1570 | |
|---|
| 1571 | |
|---|
| 1572 | <a name="method124"></a> |
|---|
| 1573 | <p/><strong>void DecayChannel::product(int i, int product) </strong> <br/> |
|---|
| 1574 | |
|---|
| 1575 | <strong>int DecayChannel::product(int i) </strong> <br/> |
|---|
| 1576 | set or get a list of the decay products, 8 products 0 <= i < 8, |
|---|
| 1577 | with trailing unused ones set to 0. |
|---|
| 1578 | |
|---|
| 1579 | |
|---|
| 1580 | <a name="method125"></a> |
|---|
| 1581 | <p/><strong>void DecayChannel::setHasChanged(bool hasChanged) </strong> <br/> |
|---|
| 1582 | |
|---|
| 1583 | <strong>bool DecayChannel::hasChanged() </strong> <br/> |
|---|
| 1584 | used for internal purposes, to know which decay modes have been changed. |
|---|
| 1585 | |
|---|
| 1586 | |
|---|
| 1587 | <a name="method126"></a> |
|---|
| 1588 | <p/><strong>bool DecayChannel::contains(int id1) </strong> <br/> |
|---|
| 1589 | |
|---|
| 1590 | <strong>bool DecayChannel::contains(int id1, int id2) </strong> <br/> |
|---|
| 1591 | |
|---|
| 1592 | <strong>bool DecayChannel::contains(int id1, int id2, int id3) </strong> <br/> |
|---|
| 1593 | find if the decay product list contains the one, two or three particle |
|---|
| 1594 | identities provided. If the same code is repeated then so must it be in |
|---|
| 1595 | the products list. Matching also requires correct sign. |
|---|
| 1596 | |
|---|
| 1597 | |
|---|
| 1598 | <a name="method127"></a> |
|---|
| 1599 | <p/><strong>void DecayChannel::currentBR(double currentBR) </strong> <br/> |
|---|
| 1600 | |
|---|
| 1601 | <strong>double DecayChannel::currentBR() </strong> <br/> |
|---|
| 1602 | set or get the current branching ratio, taking into account on/off |
|---|
| 1603 | switches and dynamic width for resonances. For internal use. |
|---|
| 1604 | |
|---|
| 1605 | |
|---|
| 1606 | <a name="method128"></a> |
|---|
| 1607 | <p/><strong>void DecayChannel::onShellWidth(double onShellWidth) </strong> <br/> |
|---|
| 1608 | |
|---|
| 1609 | <strong>double DecayChannel::onShellWidth() </strong> <br/> |
|---|
| 1610 | set or get the current partial width of the channel; intended for |
|---|
| 1611 | resonances where the widhts are recalculated based on the current |
|---|
| 1612 | resonance mass. For internal use. |
|---|
| 1613 | |
|---|
| 1614 | |
|---|
| 1615 | <a name="method129"></a> |
|---|
| 1616 | <p/><strong>void DecayChannel::onShellWidthFactor(double factor) </strong> <br/> |
|---|
| 1617 | multiply the current partial width by <code>factor</code>. |
|---|
| 1618 | |
|---|
| 1619 | |
|---|
| 1620 | <a name="method130"></a> |
|---|
| 1621 | <p/><strong>void DecayChannel::openSec(int idSgn, double openSecIn) </strong> <br/> |
|---|
| 1622 | |
|---|
| 1623 | <strong>double DecayChannel::openSec(nt idSgn) </strong> <br/> |
|---|
| 1624 | set or get the fraction of secondary open widths, separately for |
|---|
| 1625 | positive and negative particles. For internal use. |
|---|
| 1626 | |
|---|
| 1627 | |
|---|
| 1628 | </body> |
|---|
| 1629 | </html> |
|---|
| 1630 | |
|---|
| 1631 | <!-- Copyright (C) 2012 Torbjorn Sjostrand --> |
|---|
![(please configure the [header_logo] section in trac.ini)](/HiSusy/chrome/site/your_project_logo.png){kind=logo}
