Particle Codes(粒子的编码).pdfVIP

next up previous contents Next: The Event Record Up: The Event Record Previous: The Event Record Contents Particle Codes The Particle Data Group particle code [PDG88 ,PDG92 ,PDG00] is used consistently throughout the program. Almost all known discrepancies between earlier versions of the PDG standard and the PYTHIA usage have now been resolved. The one known exception is the (very uncertain) classification of , with also affected as a consequence. There is also a possible point of confusion in the technicolor sector between and . The latter is retained for historical reasons, whereas the former was introduced for consistency in models of top-color-assisted technicolor. The PDG standard, with the local PYTHIA extensions, is referred to as the KF particle code. This code you have to be thoroughly familiar with. It is described below. The KF code is not convenient for a direct storing of masses, decay data, or other particle properties, since the KF codes are so spread out. Instead a compressed code KC between 1 and 500 is used here. A particle and its antiparticle are mapped to the same KC code, but else the mapping is unique. Normally this code is only used at very specific places in the program, not visible to the user. If need be, the correspondence can always be obtained by using the function PYCOMP, i.e. KC = PYCOMP(KF). This mapping is not hardcoded, but can be changed by user intervention, e.g. by introducing new particles with the PYUPDA facility. It is therefore not intended that you should ever want or need to know any KC codes at all. It may be useful to know, however, that for codes smaller than 80, KF and KC agree. Normally a user would never do the inverse mapping, but we note that this is stored as KF = KCHG(KC,4), making use of the KCHG array in the PYDAT2 common block. Of course, the sign of a particle could never be recovered by this inverse operation. The particle names print