]>
Commit | Line | Data |
---|---|---|
5ad4eb21 | 1 | <chapter name="Phase Space Cuts"> |
2 | ||
3 | <h2>Phase Space Cuts</h2> | |
4 | ||
5 | <code>PhaseSpace</code> is base class for all hard-process phase-space | |
6 | generators, either generic <ei>2 -> 1</ei> or <ei>2 -> 2</ei> ones, | |
7 | or specialized ones like for elastic and diffractive scattering. | |
8 | ||
9 | <p/> | |
10 | In it, it is possible to constrain the kinematics of most processes. | |
11 | (Exceptions are "soft physics", i.e. minimum bias, elastic and | |
12 | diffractive processes. The Coulomb singularity for elastic scatterings, | |
13 | if simulated, is <aloc href="TotalCrossSections">handled separately</aloc>.) | |
14 | These constraints apply in the rest frame of the hard subprocess, and | |
15 | topologies normally would be changed e.g. by subsequent showering | |
16 | activity. The cross section of a process is adjusted to only | |
17 | correspond to the allowed phase space. | |
18 | ||
19 | <p/> | |
20 | The more particles in the final state, the more cuts could be applied. | |
21 | Here we have tried to remain with the useful minimum, however. More | |
22 | generic possibilities could be handled by the | |
23 | <aloc href="UserHooks">user hooks</aloc> facility. | |
24 | ||
25 | <h3>Cuts in all processes</h3> | |
26 | ||
27 | <parm name="PhaseSpace:mHatMin" default="4." min="0."> | |
28 | The minimum invariant mass. | |
29 | </parm> | |
30 | ||
31 | <parm name="PhaseSpace:mHatMax" default="-1."> | |
32 | The maximum invariant mass. | |
33 | A value below <code>mHatMin</code> means there is no upper limit. | |
34 | </parm> | |
35 | ||
36 | <h3>Cuts in <ei>2 -> 1</ei> processes</h3> | |
37 | ||
38 | When a resonance <code>id</code> is produced, the | |
39 | <aloc href="ParticleDataScheme"><code>mMin(id)</code>and | |
40 | <code>mMax(id)</code></aloc> methods restrict the allowed mass range | |
41 | of this resonance. Therefore the allowed range is chosen to be the | |
42 | overlap of this range and the <code>mHatMin</code> to | |
43 | <code>mHatMax</code> range above. Most resonances by default have no | |
44 | upper mass limit, so effects mainly concern the lower limit. | |
45 | Should there be no overlap between the two ranges then the process | |
46 | will be switched off. | |
47 | ||
48 | <h3>Cuts in <ei>2 -> 2</ei> processes</h3> | |
49 | ||
50 | <parm name="PhaseSpace:pTHatMin" default="0." min="0."> | |
51 | The minimum invariant <ei>pT</ei>. | |
52 | </parm> | |
53 | ||
54 | <parm name="PhaseSpace:pTHatMax" default="-1."> | |
55 | The maximum invariant <ei>pT</ei>. | |
56 | A value below <code>pTHatMin</code> means there is no upper limit. | |
57 | </parm> | |
58 | ||
59 | <parm name="PhaseSpace:pTHatMinDiverge" default="1." min="0.5"> | |
60 | Extra <ei>pT</ei> cut to avoid the divergences of some processes | |
61 | in the limit <ei>pT -> 0</ei>. Specifically, if either or both | |
62 | produced particles have a mass below <code>pTHatMinDiverge</code> | |
63 | then <ei>pT</ei> is limited from below by the larger of | |
64 | <code>pTHatMin</code> and <code>pTHatMinDiverge</code>. | |
65 | </parm> | |
66 | ||
67 | <flag name="PhaseSpace:useBreitWigners" default="on"> | |
68 | Allows masses to be selected according to Breit-Wigner shapes in | |
69 | <ei>2 -> 2</ei> processes, whenever particles have been declared | |
70 | with a nonvanishing width above the threshold below. In those cases | |
71 | also the limits below will be used for the mass selection. For | |
72 | <ei>2 -> 1</ei> processes the Breit-Wigner shape is part of the | |
73 | cross section itself, and therefore always included. | |
74 | </flag> | |
75 | ||
76 | <parm name="PhaseSpace:minWidthBreitWigners" default="0.01" min="1e-6"> | |
77 | The minimum width a resonance must have for the mass to be dynamically | |
78 | selected according to a Breit-Wigner shape, within the limits set below. | |
79 | Only applies when <code>useBreitWigners</code> is on; else the nominal | |
80 | mass value is always used. | |
81 | </parm> | |
82 | ||
83 | <p/> | |
84 | For a particle with a Breit-Wigner shape selected, according to the | |
85 | rules above and to the rules of the particle species itself, the | |
86 | <aloc href="ParticleDataScheme"><code>mMin(id)</code> | |
87 | and <code>mMax(id)</code></aloc> methods restrict the allowed mass range | |
88 | of the particle, just like for the <ei>2 -> 1 </ei> processes. | |
89 | ||
90 | <h3>Cuts in <ei>2 -> 3</ei> processes</h3> | |
91 | ||
92 | Currently no further cuts have been introduced for <ei>2 -> 3</ei> | |
93 | processes than those already available for <ei>2 -> 2</ei> ones. | |
94 | A <ei>2 -> 3</ei> process in principle would allow to define a | |
95 | separate <ei>pT</ei> range for each of the three particles (with some | |
96 | correlations), but for now all three are restricted exactly the | |
97 | same way by <code>pTHatMin</code> and <code>pTHatMax</code>. | |
98 | As above, Breit-Wigner mass ranges can be restricted. | |
99 | ||
100 | <h3>Documentation</h3> | |
101 | ||
102 | <flag name="PhaseSpace:showSearch" default="off"> | |
103 | Possibility to print information on the search for phase-space | |
104 | coefficients that (in a multichannel approach) provides an analytical | |
105 | upper envelope of the differential cross section, and the | |
106 | corresponding upper estimate of the cross section. Of interest | |
107 | for crosschecks by expert users only. | |
108 | </flag> | |
109 | ||
110 | <flag name="PhaseSpace:showViolation" default="off"> | |
111 | Possibility to print information whenever the assumed maximum | |
112 | differential cross section of a process is violated, i.e. when | |
113 | the initial maximization procedure did not find the true maximum. | |
114 | Also, should negative cross sections occur, print whenever a more | |
115 | negative value is encountered. | |
116 | </flag> | |
117 | ||
118 | </chapter> | |
119 | ||
120 | <!-- Copyright (C) 2008 Torbjorn Sjostrand --> |