Context Navigation

← Previous Revision
Latest Revision
Next Revision →
Blame
Revision Log

PhaseSpaceCuts.php @ 1

Last change on this file since 1 was 1, checked in by zerwas, 11 years ago
first import of structure, PYTHIA8 and DELPHES
File size: 24.0 KB

Line
1	<html>
2	<head>
3	<title>Phase Space Cuts</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='PhaseSpaceCuts.php'>
29
30	<h2>Phase Space Cuts</h2>
31
32	<code>PhaseSpace</code> is base class for all hard-process phase-space
33	generators, either generic <i>2 -> 1</i> or <i>2 -> 2</i> ones,
34	or specialized ones like for elastic and diffractive scattering.
35
36	<p/>
37	In it, it is possible to constrain the kinematics of most processes.
38	(Exceptions are "soft physics", i.e. minimum bias, elastic and
39	diffractive processes. The Coulomb singularity for elastic scatterings,
40	if simulated, is <?php $filepath = $_GET["filepath"];
41	echo "<a href='TotalCrossSections.php?filepath=".$filepath."' target='page'>";?>handled separately</a>.)
42	These constraints apply in the rest frame of the hard subprocess, and
43	topologies normally would be changed e.g. by subsequent showering
44	activity. The cross section of a process is adjusted to only
45	correspond to the allowed phase space.
46
47	<p/>
48	The more particles in the final state, the more cuts could be applied.
49	Here we have tried to remain with the useful minimum, however. More
50	generic possibilities could be handled by the
51	<?php $filepath = $_GET["filepath"];
52	echo "<a href='UserHooks.php?filepath=".$filepath."' target='page'>";?>user hooks</a> facility.
53
54	<h3>Cuts in all processes</h3>
55
56	<br/><br/><table><tr><td><strong>PhaseSpace:mHatMin </td><td></td><td> <input type="text" name="1" value="4." size="20"/>   (<code>default = <strong>4.</strong></code>; <code>minimum = 0.</code>)</td></tr></table>
57	The minimum invariant mass.
58
59
60	<br/><br/><table><tr><td><strong>PhaseSpace:mHatMax </td><td></td><td> <input type="text" name="2" value="-1." size="20"/>   (<code>default = <strong>-1.</strong></code>)</td></tr></table>
61	The maximum invariant mass.
62	A value below <code>mHatMin</code> means there is no upper limit.
63
64
65	<h3>Cuts in <i>2 -> 1</i> processes</h3>
66
67	When a resonance <code>id</code> is produced, the
68	<code><?php $filepath = $_GET["filepath"];
69	echo "<a href='ParticleDataScheme.php?filepath=".$filepath."' target='page'>";?>mMin(id)</a></code> and
70	<code><?php $filepath = $_GET["filepath"];
71	echo "<a href='ParticleDataScheme.php?filepath=".$filepath."' target='page'>";?>mMax(id)</a></code>
72	methods restrict the allowed mass range
73	of this resonance. Therefore the allowed range is chosen to be the
74	overlap of this range and the <code>mHatMin</code> to
75	<code>mHatMax</code> range above. Most resonances by default have no
76	upper mass limit, so effects mainly concern the lower limit.
77	Should there be no overlap between the two ranges then the process
78	will be switched off.
79
80	<h3>Cuts in <i>2 -> 2</i> processes</h3>
81
82	<br/><br/><table><tr><td><strong>PhaseSpace:pTHatMin </td><td></td><td> <input type="text" name="3" value="0." size="20"/>   (<code>default = <strong>0.</strong></code>; <code>minimum = 0.</code>)</td></tr></table>
83	The minimum invariant <i>pT</i>.
84
85
86	<br/><br/><table><tr><td><strong>PhaseSpace:pTHatMax </td><td></td><td> <input type="text" name="4" value="-1." size="20"/>   (<code>default = <strong>-1.</strong></code>)</td></tr></table>
87	The maximum invariant <i>pT</i>.
88	A value below <code>pTHatMin</code> means there is no upper limit.
89
90
91	<br/><br/><table><tr><td><strong>PhaseSpace:pTHatMinDiverge </td><td></td><td> <input type="text" name="5" value="1." size="20"/>   (<code>default = <strong>1.</strong></code>; <code>minimum = 0.5</code>)</td></tr></table>
92	Extra <i>pT</i> cut to avoid the divergences of some processes
93	in the limit <i>pT -> 0</i>. Specifically, if either or both
94	produced particles have a mass below <code>pTHatMinDiverge</code>
95	then <i>pT</i> is limited from below by the larger of
96	<code>pTHatMin</code> and <code>pTHatMinDiverge</code>.
97
98
99	<br/><br/><strong>PhaseSpace:useBreitWigners</strong> <input type="radio" name="6" value="on" checked="checked"><strong>On</strong>
100	<input type="radio" name="6" value="off"><strong>Off</strong>
101	(<code>default = <strong>on</strong></code>)<br/>
102	Allows masses to be selected according to Breit-Wigner shapes in
103	<i>2 -> 2</i> processes, whenever particles have been declared
104	with a nonvanishing width above the threshold below. In those cases
105	also the limits below will be used for the mass selection. For
106	<i>2 -> 1</i> processes the Breit-Wigner shape is part of the
107	cross section itself, and therefore always included.
108
109
110	<br/><br/><table><tr><td><strong>PhaseSpace:minWidthBreitWigners </td><td></td><td> <input type="text" name="7" value="0.01" size="20"/>   (<code>default = <strong>0.01</strong></code>; <code>minimum = 1e-6</code>)</td></tr></table>
111	The minimum width a resonance must have for the mass to be dynamically
112	selected according to a Breit-Wigner shape, within the limits set below.
113	Only applies when <code>useBreitWigners</code> is on; else the nominal
114	mass value is always used.
115
116
117	<p/>
118	For a particle with a Breit-Wigner shape selected, according to the
119	rules above and to the rules of the particle species itself, the
120	<code><?php $filepath = $_GET["filepath"];
121	echo "<a href='ParticleDataScheme.php?filepath=".$filepath."' target='page'>";?>mMin(id)</a></code> and
122	<code><?php $filepath = $_GET["filepath"];
123	echo "<a href='ParticleDataScheme.php?filepath=".$filepath."' target='page'>";?>mMax(id)</a></code>
124	methods restrict the allowed mass range of the particle, just like for
125	the <i>2 -> 1 </i> processes.
126
127	<h3>Cuts in <i>2 -> 3</i> processes</h3>
128
129	There are two main classes of <i>2 -> 3</i> processes. One is the
130	processes such as <i>WW/ZZ</i>-fusion Higgs production, i.e.
131	<i>q q -> q q H</i>, where there are no special singularities
132	associated with two partons in the final state being collinear,
133	or even for <i>pT -> 0</i>. For this class, no further cuts
134	have been introduced than those already available for <i>2 -> 2</i>
135	processes. Specifically, for now all three are restricted exactly the
136	same way by <code>pTHatMin</code> and <code>pTHatMax</code>. As above,
137	Breit-Wigner mass ranges can be restricted.
138
139	<p/>
140	The other <i>2 -> 3</i> event class is QCD processes, such as
141	<i>g g -> g g g</i>. Here the soft and collinear singularities
142	play a major role, and the phase space generation and cuts have
143	been adapted to this. For this class, an alternative set of cuts
144	is used, as outlined in the following. First of all the three
145	outgoing partons are ordered in falling <i>pT</i>, i.e.
146	<i>pT_3 > pT_4 > pT_5</i> (where the labelling 3, 4, 5 of the outgoing
147	partons is random, i.e. unrelated to the order specified in the
148	process name). The allowed ranges of <i>pT_3</i> and <i>pT_5</i>
149	can be specified, but obviously <i>pT_3max >= pT_5max</i> and
150	<i>pT_3min >= pT_5min</i>. The <i>pT_4</i> is not constrained
151	explicitly, but is constructed from the vector sum of <i>pT_3</i>
152	and <i>pT_5</i>, subject to the constraint that it has to lie
153	between the two in magnitude. While the <i>pT</i> cuts take care
154	of singularities collinear with the incoming beams, it is also
155	necessary to handle final-state singularities, when two outgoing
156	partons become collinear. This is done by requiring a minimal
157	separation in <i>R</i>, where
158	<i>R^2 = (Delta eta)^2 + (Delta phi)^2</i>.
159	Finally, a note about efficiency. The QCD <i>2 -> 3</i> phase space
160	is not set up to explicitly include <i>mHat</i> as one of the basic
161	variables. Such a cut is only done after a phase space point is already
162	selected, which means that a narrow mass choice will slow down the
163	program appreciably. Also narrow <i>pT_3</i> and <i>pT_5</i> bins
164	are likely to give inefficient generation, if it gives rise to
165	significant indirect restrictions on <i>pT_4</i>.
166
167	<br/><br/><table><tr><td><strong>PhaseSpace:pTHat3Min </td><td></td><td> <input type="text" name="8" value="10." size="20"/>   (<code>default = <strong>10.</strong></code>; <code>minimum = 0.</code>)</td></tr></table>
168	The minimum invariant <i>pT</i> of the highest-<i>pT</i> parton in
169	QCD <i>2 -> 3</i> processes.
170
171
172	<br/><br/><table><tr><td><strong>PhaseSpace:pTHat3Max </td><td></td><td> <input type="text" name="9" value="-1." size="20"/>   (<code>default = <strong>-1.</strong></code>)</td></tr></table>
173	The maximum invariant <i>pT</i> of the highest-<i>pT</i> parton in
174	QCD <i>2 -> 3</i> processes
175	A value below <code>pTHat3Min</code> means there is no upper limit.
176
177
178	<br/><br/><table><tr><td><strong>PhaseSpace:pTHat5Min </td><td></td><td> <input type="text" name="10" value="10." size="20"/>   (<code>default = <strong>10.</strong></code>; <code>minimum = 0.</code>)</td></tr></table>
179	The minimum invariant <i>pT</i> of the lowest-<i>pT</i> parton in
180	QCD <i>2 -> 3</i> processes.
181
182
183	<br/><br/><table><tr><td><strong>PhaseSpace:pTHat5Max </td><td></td><td> <input type="text" name="11" value="-1." size="20"/>   (<code>default = <strong>-1.</strong></code>)</td></tr></table>
184	The maximum invariant <i>pT</i> of the lowest-<i>pT</i> parton in
185	QCD <i>2 -> 3</i> processes
186	A value below <code>pTHat5Min</code> means there is no upper limit.
187
188
189	<br/><br/><table><tr><td><strong>PhaseSpace:RsepMin </td><td></td><td> <input type="text" name="12" value="1." size="20"/>   (<code>default = <strong>1.</strong></code>)</td></tr></table>
190	The minimum separation <i>R</i> in <i>(eta, phi)</i> space between
191	any two outgoing partons in QCD <i>2 -> 3</i> processes.
192
193
194
195	<h3>Cuts for a second hard process</h3>
196
197	If you use the machinery that allows the generation of a specified
198	<?php $filepath = $_GET["filepath"];
199	echo "<a href='ASecondHardProcess.php?filepath=".$filepath."' target='page'>";?>second hard process</a> then,
200	by default, the same phase space cuts will be used for it as listed
201	above. Optionally, however, you may use a second set of cuts, as
202	described here. In this context "first" and "second" is merely a
203	technical distinction; you are welcome e.g. to pick <i>pT</i> ranges
204	such that the second interaction always has a larger <i>pT</i> than
205	the first.
206
207	<br/><br/><strong>PhaseSpace:sameForSecond</strong> <input type="radio" name="13" value="on" checked="checked"><strong>On</strong>
208	<input type="radio" name="13" value="off"><strong>Off</strong>
209	(<code>default = <strong>on</strong></code>)<br/>
210	By default use the same cuts for a second hard process as for the
211	first. If <code>off</code> then instead use the mass and <i>pT</i>
212	cuts below, where relevant. (The other cuts above still remain the same.)
213
214
215	<br/><br/><table><tr><td><strong>PhaseSpace:mHatMinSecond </td><td></td><td> <input type="text" name="14" value="4." size="20"/>   (<code>default = <strong>4.</strong></code>; <code>minimum = 0.</code>)</td></tr></table>
216	The minimum invariant mass for a second interaction, if separate.
217
218
219	<br/><br/><table><tr><td><strong>PhaseSpace:mHatMaxSecond </td><td></td><td> <input type="text" name="15" value="-1." size="20"/>   (<code>default = <strong>-1.</strong></code>)</td></tr></table>
220	The maximum invariant mass for a second interaction, if separate.
221	A value below <code>mHatMin</code> means there is no upper limit.
222
223
224	<br/><br/><table><tr><td><strong>PhaseSpace:pTHatMinSecond </td><td></td><td> <input type="text" name="16" value="0." size="20"/>   (<code>default = <strong>0.</strong></code>; <code>minimum = 0.</code>)</td></tr></table>
225	The minimum invariant <i>pT</i> for a second interaction, if separate.
226
227
228	<br/><br/><table><tr><td><strong>PhaseSpace:pTHatMaxSecond </td><td></td><td> <input type="text" name="17" value="-1." size="20"/>   (<code>default = <strong>-1.</strong></code>)</td></tr></table>
229	The maximum invariant <i>pT</i> for a second interaction, if separate.
230	A value below <code>pTHatMin</code> means there is no upper limit.
231
232
233	<h3>Generation strategy and documentation</h3>
234
235	During the initialization stage a simplified function is found,
236	that is intended to be above the true cross-section behaviour
237	over the whole of phase space. It is chosen to be easily integrable
238	and invertible. That way a trial phase space point can be selected
239	according this simple function, and then be accepted by the ratio of
240	true to the simple function. For a good efficieny the ratio should be
241	close to unity, yet never above it. This constrains the absolute
242	normalization of the simple function. The initial search may fail to
243	find the phase space point where the true-to-simple ratio is maximal,
244	however. This then can lead to subsequent maximum violations, where the
245	ratio is above unity. Two alternative strategies are implemented to
246	handle such situations, see below.
247
248	<br/><br/><strong>PhaseSpace:showSearch</strong> <input type="radio" name="18" value="on"><strong>On</strong>
249	<input type="radio" name="18" value="off" checked="checked"><strong>Off</strong>
250	(<code>default = <strong>off</strong></code>)<br/>
251	Possibility to print information on the search for phase-space
252	coefficients that (in a multichannel approach) provides an analytical
253	upper envelope of the differential cross section, and the
254	corresponding upper estimate of the cross section. Of interest
255	for crosschecks by expert users only.
256
257
258	<br/><br/><strong>PhaseSpace:showViolation</strong> <input type="radio" name="19" value="on"><strong>On</strong>
259	<input type="radio" name="19" value="off" checked="checked"><strong>Off</strong>
260	(<code>default = <strong>off</strong></code>)<br/>
261	Possibility to print information whenever the assumed maximum
262	differential cross section of a process is violated, i.e. when
263	the initial maximization procedure did not find the true maximum.
264	Also, should negative cross sections occur, print whenever a more
265	negative value is encountered.
266
267
268	<br/><br/><strong>PhaseSpace:increaseMaximum</strong> <input type="radio" name="20" value="on"><strong>On</strong>
269	<input type="radio" name="20" value="off" checked="checked"><strong>Off</strong>
270	(<code>default = <strong>off</strong></code>)<br/>
271	Strategy for handling cases where a larger cross section is
272	obtained during the event generation than was assumed at initialization,
273	i.e. when a violation occurs.
274	<br/><b>off:</b>each event comes with a weight, which normally is unity
275	(as a consequence of the acceptance/rejection step), and is found in
276	<code><?php $filepath = $_GET["filepath"];
277	echo "<a href='EventInformation.php?filepath=".$filepath."' target='page'>";?>Info::weight()</a></code>.
278	For events which exceed the maximum instead the true-to-simple ratio
279	is stored as event weight, which then is above unity. If the user so
280	wishes this weight can then be carried along when event properties are
281	histogrammed. Since normally such violations should be rare and not
282	too much above unity one could expect most users to ignore such issues
283	be default. Should maximum violations turn out to be frequent (visible
284	in the <code><?php $filepath = $_GET["filepath"];
285	echo "<a href='EventStatistics.php?filepath=".$filepath."' target='page'>";?>Pythia::statistics()</a></code>
286	output) the option exists to use the information.
287	<br/><b>on:</b>the maximum is increased whenever it is exceeded. Thus
288	events generated after this point will be "correctly" distributed,
289	while ones generated previously obviously then have had too high a
290	relative weight. If violations occur early on and/or are small this
291	strategy should do a good job of correcting to the desired phase-space
292	distribution. This strategy may be more convenient for the normal user,
293	who would not wish to worry about event weights. It does have the
294	disadvantage that the raised maximum introduces an extra amount of
295	"history memory" to the generation sequence, so that it becomes less
296	easy to save-and-restore the <?php $filepath = $_GET["filepath"];
297	echo "<a href='RandomNumbers.php?filepath=".$filepath."' target='page'>";?>random-number
298	state</a> for debugging purposes.
299
300
301	<h3>Reweighting of <i>2 -> 2</i> processes</h3>
302
303	Events normally come with unit weight, i.e. are distributed across
304	the allowed phase space region according to the appropriate differential
305	cross sections. Sometimes it may be convenient to have an uneven
306	distribution of events. The classical example here is that many cross
307	sections drop off with transverse momentum <i>pT</i>, such that few
308	events are generated at large <i>pT</i> scales. If one wants to
309	plot the <i>pT</i> cross section, and all that comes with it, the
310	statistical error will then degrade with increasing <i>pT</i>
311	where fewer events end up.
312
313	<p/>
314	One solution is to split the full <i>pT</i> range into several
315	separate subranges, where the events of each subsample obtains a
316	different overall normalization. Specifically, if you generate a
317	comparable number of events in each <i>pT</i> bin, such that
318	larger <i>pT</i> bins are oversampled, these bins come with a
319	correspondingly reduced overall weight, that needs to be taken into
320	account when the bins are combined. The other is to have a continuously
321	increasing oversampling of events at larger <i>pT</i> scales, which
322	is compensated by a continuously decreasing weight for the event.
323
324	<p/>
325	Both of these solutions are supported. Specifically, for
326	<i>2 -> 2</i> processes, the <i>pTHat</i> scale offers a
327	convenient classification of the event. (Of course, two events
328	starting out from the same <i>pTHat</i> scale will experience
329	different parton shower evolutions, etc., and may therefore look
330	quite different at the end.) The two cuts
331	<code>PhaseSpace:pTHatMin</code> and <code>PhaseSpace:pTHatMax</code>
332	therefore offers a way to slice a <i>pT</i> range into subranges,
333	see e.g. <code>main08.cc</code>. Alternatively the
334	<?php $filepath = $_GET["filepath"];
335	echo "<a href='UserHooks.php?filepath=".$filepath."' target='page'>";?>User Hooks</a> machinery offers the
336	possibility for you to define your own reweighting of phase space
337	sampling, with a corresponding event weight, with
338	<code>UserHooks::canBiasSelection</code> and related methods.
339
340	<p/>
341	As a simplified option, we here offer the possibility to bias the
342	<i>2 -> 2</i> sampling by a power of <i>pTHat</i>, then with
343	events having a weight the inverse of this. This fast track will only
344	work under a number of strict conditions, implemented to reduce the
345	risk of abuse. (Whereas a <code>UserHooks</code> setup can be more
346	flexible.) Specifically it will work if only high-<i>pT</i>
347	<i>2 -> 2</i> processes already implemented in PYTHIA are requested,
348	notably the <code>HardQCD</code> ones. That is, you cannot mix with
349	<i>2 -> 1</i> or <i>2 -> 3</i> processes, nor with external
350	processes (notably Les Houches input) or <code>SoftQCD</code> ones,
351	and you cannot use the option to define a
352	<?php $filepath = $_GET["filepath"];
353	echo "<a href='ASecondHardProcess.php?filepath=".$filepath."' target='page'>";?>second hard process</a> in
354	the same event. Furthermore you have to be careful about the choice
355	of <code>PhaseSpace:pTHatMin</code>, since a <i>pTHat = 0</i>
356	event would come with an infinite weight.
357
358	<br/><br/><strong>PhaseSpace:bias2Selection</strong> <input type="radio" name="21" value="on"><strong>On</strong>
359	<input type="radio" name="21" value="off" checked="checked"><strong>Off</strong>
360	(<code>default = <strong>off</strong></code>)<br/>
361	Possibility to switch on a biased phase space sampling,
362	with compensatingly weighted events, for <i>2 -> 2</i> processes.
363	Can only be used under the specific conditions explained in
364	the paragraph above; under other conditions the initialization
365	will abort.
366
367
368	<br/><br/><table><tr><td><strong>PhaseSpace:bias2SelectionPow </td><td></td><td> <input type="text" name="22" value="4." size="20"/>   (<code>default = <strong>4.</strong></code>; <code>minimum = 0.</code>; <code>maximum = 10.</code>)</td></tr></table>
369	If the above flag is on, then a <i>2 -> 2</i> process at a scale
370	<i>pTHat</i> will be oversampled in phase space by an amount
371	<i>(pTHat/pTRef)^pow</i>, where you set the power <i>pow</i>
372	here. Events are assigned a compensating
373	<?php $filepath = $_GET["filepath"];
374	echo "<a href='EventInformation.php?filepath=".$filepath."' target='page'>";?>weight</a> the inverse of this,
375	i.e. <code>Info::weight()</code> will return <i>(pTRef/pTHat)^pow</i>.
376	This weight should then be used in the histogramming of event properties.
377	The final overall normalization also involves the
378	<code>Info::weightSum()</code> value.
379
380
381	<br/><br/><table><tr><td><strong>PhaseSpace:bias2SelectionRef </td><td></td><td> <input type="text" name="23" value="10." size="20"/>   (<code>default = <strong>10.</strong></code>; <code>minimum = 1.</code>)</td></tr></table>
382	The reference scale <i>pTRef</i> introduced above, such that events
383	with this <i>pTHat</i> obtain unit weight in the reweighting procedure.
384	The value of this parameter has no impact on the final result of the
385	reweighting procedure, but is only there for convenience, i.e. to
386	give "reasonably-sized" weights.
387
388
389	<input type="hidden" name="saved" value="1"/>
390
391	<?php
392	echo "<input type='hidden' name='filepath' value='".$_GET["filepath"]."'/>"?>
393
394	<table width="100%"><tr><td align="right"><input type="submit" value="Save Settings" /></td></tr></table>
395	</form>
396
397	<?php
398
399	if($_POST["saved"] == 1)
400	{
401	$filepath = $_POST["filepath"];
402	$handle = fopen($filepath, 'a');
403
404	if($_POST["1"] != "4.")
405	{
406	$data = "PhaseSpace:mHatMin = ".$_POST["1"]."\n";
407	fwrite($handle,$data);
408	}
409	if($_POST["2"] != "-1.")
410	{
411	$data = "PhaseSpace:mHatMax = ".$_POST["2"]."\n";
412	fwrite($handle,$data);
413	}
414	if($_POST["3"] != "0.")
415	{
416	$data = "PhaseSpace:pTHatMin = ".$_POST["3"]."\n";
417	fwrite($handle,$data);
418	}
419	if($_POST["4"] != "-1.")
420	{
421	$data = "PhaseSpace:pTHatMax = ".$_POST["4"]."\n";
422	fwrite($handle,$data);
423	}
424	if($_POST["5"] != "1.")
425	{
426	$data = "PhaseSpace:pTHatMinDiverge = ".$_POST["5"]."\n";
427	fwrite($handle,$data);
428	}
429	if($_POST["6"] != "on")
430	{
431	$data = "PhaseSpace:useBreitWigners = ".$_POST["6"]."\n";
432	fwrite($handle,$data);
433	}
434	if($_POST["7"] != "0.01")
435	{
436	$data = "PhaseSpace:minWidthBreitWigners = ".$_POST["7"]."\n";
437	fwrite($handle,$data);
438	}
439	if($_POST["8"] != "10.")
440	{
441	$data = "PhaseSpace:pTHat3Min = ".$_POST["8"]."\n";
442	fwrite($handle,$data);
443	}
444	if($_POST["9"] != "-1.")
445	{
446	$data = "PhaseSpace:pTHat3Max = ".$_POST["9"]."\n";
447	fwrite($handle,$data);
448	}
449	if($_POST["10"] != "10.")
450	{
451	$data = "PhaseSpace:pTHat5Min = ".$_POST["10"]."\n";
452	fwrite($handle,$data);
453	}
454	if($_POST["11"] != "-1.")
455	{
456	$data = "PhaseSpace:pTHat5Max = ".$_POST["11"]."\n";
457	fwrite($handle,$data);
458	}
459	if($_POST["12"] != "1.")
460	{
461	$data = "PhaseSpace:RsepMin = ".$_POST["12"]."\n";
462	fwrite($handle,$data);
463	}
464	if($_POST["13"] != "on")
465	{
466	$data = "PhaseSpace:sameForSecond = ".$_POST["13"]."\n";
467	fwrite($handle,$data);
468	}
469	if($_POST["14"] != "4.")
470	{
471	$data = "PhaseSpace:mHatMinSecond = ".$_POST["14"]."\n";
472	fwrite($handle,$data);
473	}
474	if($_POST["15"] != "-1.")
475	{
476	$data = "PhaseSpace:mHatMaxSecond = ".$_POST["15"]."\n";
477	fwrite($handle,$data);
478	}
479	if($_POST["16"] != "0.")
480	{
481	$data = "PhaseSpace:pTHatMinSecond = ".$_POST["16"]."\n";
482	fwrite($handle,$data);
483	}
484	if($_POST["17"] != "-1.")
485	{
486	$data = "PhaseSpace:pTHatMaxSecond = ".$_POST["17"]."\n";
487	fwrite($handle,$data);
488	}
489	if($_POST["18"] != "off")
490	{
491	$data = "PhaseSpace:showSearch = ".$_POST["18"]."\n";
492	fwrite($handle,$data);
493	}
494	if($_POST["19"] != "off")
495	{
496	$data = "PhaseSpace:showViolation = ".$_POST["19"]."\n";
497	fwrite($handle,$data);
498	}
499	if($_POST["20"] != "off")
500	{
501	$data = "PhaseSpace:increaseMaximum = ".$_POST["20"]."\n";
502	fwrite($handle,$data);
503	}
504	if($_POST["21"] != "off")
505	{
506	$data = "PhaseSpace:bias2Selection = ".$_POST["21"]."\n";
507	fwrite($handle,$data);
508	}
509	if($_POST["22"] != "4.")
510	{
511	$data = "PhaseSpace:bias2SelectionPow = ".$_POST["22"]."\n";
512	fwrite($handle,$data);
513	}
514	if($_POST["23"] != "10.")
515	{
516	$data = "PhaseSpace:bias2SelectionRef = ".$_POST["23"]."\n";
517	fwrite($handle,$data);
518	}
519	fclose($handle);
520	}
521
522	?>
523	</body>
524	</html>
525
526	<!-- Copyright (C) 2012 Torbjorn Sjostrand -->

Note: See TracBrowser for help on using the repository browser.

Context Navigation

source: HiSusy/trunk/Pythia8/pythia8170/phpdoc/PhaseSpaceCuts.php @ 1

Download in other formats: