Context Navigation

← Previous Revision
Latest Revision
Next Revision →
Blame
Revision Log

ASecondHardProcess.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: 23.7 KB

Line
1	<html>
2	<head>
3	<title>A Second Hard Process</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='ASecondHardProcess.php'>
29
30	<h2>A Second Hard Process</h2>
31
32	When you have selected a set of hard processes for hadron beams, the
33	<?php $filepath = $_GET["filepath"];
34	echo "<a href='MultipartonInteractions.php?filepath=".$filepath."' target='page'>";?>multiparton interactions</a>
35	framework can add further interactions to build up a realistic
36	underlying event. These further interactions can come from a wide
37	variety of processes, and will occasionally be quite hard. They
38	do represent a realistic random mix, however, which means one cannot
39	predetermine what will happen. Occasionally there may be cases
40	where one wants to specify also the second hard interaction rather
41	precisely. The options on this page allow you to do precisely that.
42
43	<br/><br/><strong>SecondHard:generate</strong> <input type="radio" name="1" value="on"><strong>On</strong>
44	<input type="radio" name="1" value="off" checked="checked"><strong>Off</strong>
45	(<code>default = <strong>off</strong></code>)<br/>
46	Generate two hard scatterings in a collision between hadron beams.
47	The hardest process can be any combination of internal processes,
48	available in the normal <?php $filepath = $_GET["filepath"];
49	echo "<a href='ProcessSelection.php?filepath=".$filepath."' target='page'>";?>process
50	selection</a> machinery, or external input. Here you must further
51	specify which set of processes to allow for the second hard one, see
52	the following.
53
54
55	<h3>Process Selection</h3>
56
57	In principle the whole <?php $filepath = $_GET["filepath"];
58	echo "<a href='ProcessSelection.php?filepath=".$filepath."' target='page'>";?>process
59	selection</a> allowed for the first process could be repeated
60	for the second one. However, this would probably be overkill.
61	Therefore here a more limited set of prepackaged process collections
62	are made available, that can then be further combined at will.
63	Since the description is almost completely symmetric between the
64	first and the second process, you always have the possibility
65	to pick one of the two processes according to the complete list
66	of possibilities.
67
68	<p/>
69	Here comes the list of allowed sets of processes, to combine at will:
70
71	<br/><br/><strong>SecondHard:TwoJets</strong> <input type="radio" name="2" value="on"><strong>On</strong>
72	<input type="radio" name="2" value="off" checked="checked"><strong>Off</strong>
73	(<code>default = <strong>off</strong></code>)<br/>
74	Standard QCD <i>2 -> 2</i> processes involving gluons and
75	<i>d, u, s, c, b</i> quarks.
76
77
78	<br/><br/><strong>SecondHard:PhotonAndJet</strong> <input type="radio" name="3" value="on"><strong>On</strong>
79	<input type="radio" name="3" value="off" checked="checked"><strong>Off</strong>
80	(<code>default = <strong>off</strong></code>)<br/>
81	A prompt photon recoiling against a quark or gluon jet.
82
83	<br/><br/><strong>SecondHard:TwoPhotons</strong> <input type="radio" name="4" value="on"><strong>On</strong>
84	<input type="radio" name="4" value="off" checked="checked"><strong>Off</strong>
85	(<code>default = <strong>off</strong></code>)<br/>
86	Two prompt photons recoiling against each other.
87
88	<br/><br/><strong>SecondHard:Charmonium</strong> <input type="radio" name="5" value="on"><strong>On</strong>
89	<input type="radio" name="5" value="off" checked="checked"><strong>Off</strong>
90	(<code>default = <strong>off</strong></code>)<br/>
91	Production of charmonium via colour singlet and colour octet channels.
92
93	<br/><br/><strong>SecondHard:Bottomonium</strong> <input type="radio" name="6" value="on"><strong>On</strong>
94	<input type="radio" name="6" value="off" checked="checked"><strong>Off</strong>
95	(<code>default = <strong>off</strong></code>)<br/>
96	Production of bottomonium via colour singlet and colour octet channels.
97
98	<br/><br/><strong>SecondHard:SingleGmZ</strong> <input type="radio" name="7" value="on"><strong>On</strong>
99	<input type="radio" name="7" value="off" checked="checked"><strong>Off</strong>
100	(<code>default = <strong>off</strong></code>)<br/>
101	Scattering <i>q qbar -> gamma^*/Z^0</i>, with full interference
102	between the <i>gamma^*</i> and <i>Z^0</i>.
103
104
105	<br/><br/><strong>SecondHard:SingleW</strong> <input type="radio" name="8" value="on"><strong>On</strong>
106	<input type="radio" name="8" value="off" checked="checked"><strong>Off</strong>
107	(<code>default = <strong>off</strong></code>)<br/>
108	Scattering <i>q qbar' -> W^+-</i>.
109
110
111	<br/><br/><strong>SecondHard:GmZAndJet</strong> <input type="radio" name="9" value="on"><strong>On</strong>
112	<input type="radio" name="9" value="off" checked="checked"><strong>Off</strong>
113	(<code>default = <strong>off</strong></code>)<br/>
114	Scattering <i>q qbar -> gamma^*/Z^0 g</i> and
115	<i>q g -> gamma^*/Z^0 q</i>.
116
117
118	<br/><br/><strong>SecondHard:WAndJet</strong> <input type="radio" name="10" value="on"><strong>On</strong>
119	<input type="radio" name="10" value="off" checked="checked"><strong>Off</strong>
120	(<code>default = <strong>off</strong></code>)<br/>
121	Scattering <i>q qbar' -> W^+- g</i> and
122	<i>q g -> W^+- q'</i>.
123
124
125	<br/><br/><strong>SecondHard:TopPair</strong> <input type="radio" name="11" value="on"><strong>On</strong>
126	<input type="radio" name="11" value="off" checked="checked"><strong>Off</strong>
127	(<code>default = <strong>off</strong></code>)<br/>
128	Production of a top pair, either via QCD processes or via an
129	intermediate <i>gamma^*/Z^0</i> resonance.
130
131
132	<br/><br/><strong>SecondHard:SingleTop</strong> <input type="radio" name="12" value="on"><strong>On</strong>
133	<input type="radio" name="12" value="off" checked="checked"><strong>Off</strong>
134	(<code>default = <strong>off</strong></code>)<br/>
135	Production of a single top, either via a <i>t-</i> or
136	an <i>s-</i>channel <i>W^+-</i> resonance.
137
138
139	<p/>
140	A further process collection comes with a warning flag:
141
142	<br/><br/><strong>SecondHard:TwoBJets</strong> <input type="radio" name="13" value="on"><strong>On</strong>
143	<input type="radio" name="13" value="off" checked="checked"><strong>Off</strong>
144	(<code>default = <strong>off</strong></code>)<br/>
145	The <i>q qbar -> b bbar</i> and <i>g g -> b bbar</i> processes.
146	These are already included in the <code>TwoJets</code> sample above,
147	so it would be doublecounting to include both, but we assume there
148	may be cases where the <i>b</i> subsample will be of special interest.
149	This subsample does not include flavour-excitation or gluon-splitting
150	contributions to the <i>b</i> rate, however, so, depending
151	on the topology if interest, it may or may not be a good approximation.
152
153
154	<h3>Cuts and scales</h3>
155
156	The second hard process obeys exactly the same selection rules for
157	<?php $filepath = $_GET["filepath"];
158	echo "<a href='PhaseSpaceCuts.php?filepath=".$filepath."' target='page'>";?>phase space cuts</a> and
159	<?php $filepath = $_GET["filepath"];
160	echo "<a href='CouplingsAndScales.php?filepath=".$filepath."' target='page'>";?>couplings and scales</a>
161	as the first one does. Specifically, a <i>pTmin</i> cut for
162	<i>2 -> 2</i> processes would apply to the first and the second hard
163	process alike, and ballpark half of the time the second could be
164	generated with a larger <i>pT</i> than the first. (Exact numbers
165	depending on the relative shape of the two cross sections.) That is,
166	first and second is only used as an administrative distinction between
167	the two, not as a physics ordering one.
168
169	<p/>
170	Optionally it is possible to pick the mass and <i>pT</i>
171	<?php $filepath = $_GET["filepath"];
172	echo "<a href='PhaseSpaceCuts.php?filepath=".$filepath."' target='page'>";?>phase space cuts</a> separately for
173	the second hard interaction. The main application presumably would
174	be to allow a second process that is softer than the first, but still
175	hard. But one is also free to make the second process harder than the
176	first, if desired. So long as the two <i>pT</i> (or mass) ranges
177	overlap the ordering will not be the same in all events, however.
178
179	<h3>Cross-section calculation</h3>
180
181	As an introduction, a brief reminder of Poissonian statistics.
182	Assume a stochastic process in time, for now not necessarily a
183	high-energy physics one, where the probability for an event to occur
184	at any given time is independent of what happens at other times.
185	Then the probability for <i>n</i> events to occur in a finite
186	time interval is
187	<br/><i>
188	P_n = <n>^n exp(-<n>) / n!
189	</i><br/>
190	where <i><n></i> is the average number of events. If this
191	number is small we can approximate <i>exp(-<n>) = 1 </i>,
192	so that <i>P_1 = <n></i> and
193	<i>P_2 = <n>^2 / 2 = P_1^2 / 2</i>.
194
195	<p/>
196	Now further assume that the events actually are of two different
197	kinds <i>a</i> and <i>b</i>, occuring independently of each
198	other, such that <i><n> = <n_a> + <n_b></i>.
199	It then follows that the probability of having one event of type
200	<i>a</i> (or <i>b</i>) and nothing else is
201	<i>P_1a = <n_a></i> (or <i>P_1b = <n_b></i>).
202	From
203	<br/><i>
204	P_2 = (<n_a> + <n_b&gt)^2 / 2 = (P_1a + P_1b)^2 / 2 =
205	(P_1a^2 + 2 P_1a P_1b + P_1b^2) / 2
206	</i><br/>
207	it is easy to read off that the probability to have exactly two
208	events of kind <i>a</i> and none of <i>b</i> is
209	<i>P_2aa = P_1a^2 / 2</i> whereas that of having one <i>a</i>
210	and one <i>b</i> is <i>P_2ab = P_1a P_1b</i>. Note that the
211	former, with two identical events, contains a factor <i>1/2</i>
212	while the latter, with two different ones, does not. If viewed
213	in a time-ordered sense, the difference is that the latter can be
214	obtained two ways, either first an <i>a</i> and then a <i>b</i>
215	or else first a <i>b</i> and then an <i>a</i>.
216
217	<p/>
218	To translate this language into cross-sections for high-energy
219	events, we assume that interactions can occur at different <i>pT</i>
220	values independently of each other inside inelastic nondiffractive
221	(= "minbias") events. Then the above probabilities translate into
222	<i>P_n = sigma_n / sigma_ND</i> where <i>sigma_ND</i> is the
223	total nondiffractive cross section. Again we want to assume that
224	<i>exp(-<n>)</i> is close to unity, i.e. that the total
225	hard cross section above <i>pTmin</i> is much smaller than
226	<i>sigma_ND</i>. The hard cross section is dominated by QCD
227	jet production, and a reasonable precaution is to require a
228	<i>pTmin</i> of at least 20 GeV at LHC energies.
229	(For <i>2 -> 1</i> processes such as
230	<i>q qbar -> gamma^*/Z^0 (-> f fbar)</i> one can instead make a
231	similar cut on mass.) Then the generic equation
232	<i>P_2 = P_1^2 / 2</i> translates into
233	<i>sigma_2/sigma_ND = (sigma_1 / sigma_ND)^2 / 2</i> or
234	<i>sigma_2 = sigma_1^2 / (2 sigma_ND)</i>.
235
236	<p/>
237	Again different processes <i>a, b, c, ...</i> contribute,
238	and by the same reasoning we obtain
239	<i>sigma_2aa = sigma_1a^2 / (2 sigma_ND)</i>,
240	<i>sigma_2ab = sigma_1a sigma_1b / sigma_ND</i>,
241	and so on.
242
243	<p/>
244	There is one important correction to this picture: all collisions
245	do no occur under equal conditions. Some are more central in impact
246	parameter, others more peripheral. This leads to a further element of
247	variability: central collisions are likely to have more activity
248	than the average, peripheral less. Integrated over impact
249	parameter standard cross sections are recovered, but correlations
250	are affected by a "trigger bias" effect: if you select for events
251	with a hard process you favour events at small impact parameter
252	which have above-average activity, and therefore also increased
253	chance for further interactions. (In PYTHIA this is the origin
254	of the "pedestal effect", i.e. that events with a hard interaction
255	have more underlying activity than the level found in minimum-bias
256	events.) When you specify a matter overlap profile in the
257	multiparton-interactions scenario, such an enhancement/depletion factor
258	<i>f_impact</i> is chosen event-by-event and can be averaged
259	during the course of the run. As an example, the double Gaussian
260	form used in Tune A gives approximately
261	<i><f_impact> = 2.5</i>. The above equations therefore
262	have to be modified to
263	<i>sigma_2aa = <f_impact> sigma_1a^2 / (2 sigma_ND)</i>,
264	<i>sigma_2ab = <f_impact> sigma_1a sigma_1b / sigma_ND</i>.
265	Experimentalists often instead use the notation
266	<i>sigma_2ab = sigma_1a sigma_1b / sigma_eff</i>,
267	from which we see that PYTHIA "predicts"
268	<i>sigma_eff = sigma_ND / <f_impact></i>.
269	When the generation of multiparton interactions is switched off it is
270	not possible to calculate <i><f_impact></i> and therefore
271	it is set to unity.
272
273	<p/>
274	When this recipe is to be applied to calculate
275	actual cross sections, it is useful to distinguish three cases,
276	depending on which set of processes are selected to study for
277	the first and second interaction.
278
279	<p/>
280	(1) The processes <i>a</i> for the first interaction and
281	<i>b</i> for the second one have no overlap at all.
282	For instance, the first could be <code>TwoJets</code> and the
283	second <code>TwoPhotons</code>. In that case, the two interactions
284	can be selected independently, and cross sections tabulated
285	for each separate subprocess in the two above classes. At the
286	end of the run, the cross sections in <i>a</i> should be multiplied
287	by <i><f_impact> sigma_1b / sigma_ND</i> to bring them to
288	the correct overall level, and those in <i>b</i> by
289	<i><f_impact> sigma_1a / sigma_ND</i>.
290
291	<p/>
292	(2) Exactly the same processes <i>a</i> are selected for the
293	first and second interaction. In that case it works as above,
294	with <i>a = b</i>, and it is only necessary to multiply by an
295	additional factor <i>1/2</i>. A compensating factor of 2
296	is automatically obtained for picking two different subprocesses,
297	e.g. if <code>TwoJets</code> is selected for both interactions,
298	then the combination of the two subprocesses <i>q qbar -> g g</i>
299	and <i>g g -> g g</i> can trivially be obtained two ways.
300
301	<p/>
302	(3) The list of subprocesses partly but not completely overlap.
303	For instance, the first process is allowed to contain <i>a</i>
304	or <i>c</i> and the second <i>b</i> or <i>c</i>, where
305	there is no overlap between <i>a</i> and <i>b</i>. Then,
306	when an independent selection for the first and second interaction
307	both pick one of the subprocesses in <i>c</i>, half of those
308	events have to be thrown, and the stored cross section reduced
309	accordingly. Considering the four possible combinations of first
310	and second process, this gives a
311	<br/><i>
312	sigma'_1 = sigma_1a + sigma_1c * (sigma_2b + sigma_2c/2) /
313	(sigma_2b + sigma_2c)
314	</i><br/>
315	with the factor <i>1/2</i> for the <i>sigma_1c sigma_2c</i> term.
316	At the end of the day, this <i>sigma'_1</i> should be multiplied
317	by the normalization factor
318	<br/><i>
319	f_1norm = <f_impact> (sigma_2b + sigma_2c) / sigma_ND
320	</i><br/>
321	here without a factor <i>1/2</i> (or else it would have been
322	doublecounted). This gives the correct
323	<br/><i>
324	(sigma_2b + sigma_2c) * sigma'_1 = sigma_1a * sigma_2b
325	+ sigma_1a * sigma_2c + sigma_1c * sigma_2b + sigma_1c * sigma_2c/2
326	</i><br/>
327	The second interaction can be handled in exact analogy.
328
329	<p/>
330	For the considerations above it is assumed that the phase space cuts
331	are the same for the two processes. It is possible to set the mass and
332	transverse momentum cuts differently, however. This changes nothing
333	for processes that already are different. For two collisions of the
334	same type it is partly a matter of interpretation what is intended.
335	If we consider the case of the same process in two non-overlapping
336	phase space regions, most likely we want to consider them as
337	separate processes, in the sense that we expect a factor 2 relative
338	to Poissonian statistics from either of the two hardest processes
339	populating either of the two phase space regions. In total we are
340	therefore lead to adopt the same strategy as in case (3) above:
341	only in the overlapping part of the two allowed phase space regions
342	could two processes be identical and thus appear with a 1/2 factor,
343	elsewhere the two processes are never identical and do not
344	include the 1/2 factor. We reiterate, however, that the case of
345	partly but not completely overlapping phase space regions for one and
346	the same process is tricky, and not to be used without prior
347	deliberation.
348
349	<p/>
350	The listing obtained with the <code>pythia.statistics()</code>
351	already contain these corrections factors, i.e. cross sections
352	are for the occurence of two interactions of the specified kinds.
353	There is not a full tabulation of the matrix of all the possible
354	combinations of a specific first process together with a specific
355	second one (but the information is there for the user to do that,
356	if desired). Instead <code>pythia.statistics()</code> shows this
357	matrix projected onto the set of processes and associated cross
358	sections for the first and the second interaction, respectively.
359	Up to statistical fluctuations, these two sections of the
360	<code>pythia.statistics()</code> listing both add up to the same
361	total cross section for the event sample.
362
363	<p/>
364	There is a further special feature to be noted for this listing,
365	and that is the difference between the number of "selected" events
366	and the number of "accepted" ones. Here is how that comes about.
367	Originally the first and second process are selected completely
368	independently. The generation (in)efficiency is reflected in the
369	different number of intially tried events for the first and second
370	process, leading to the same number of selected events. While
371	acceptable on their own, the combination of the two processes may
372	be unacceptable, however. It may be that the two processes added
373	together use more energy-momentum than kinematically allowed, or,
374	even if not, are disfavoured when the PYTHIA approach to provide
375	correlated parton densities is applied. Alternatively, referring
376	to case (3) above, it may be because half of the events should
377	be thrown for identical processes. Taken together, it is these
378	effects that reduced the event number from "selected" to "accepted".
379	(A further reduction may occur if a
380	<?php $filepath = $_GET["filepath"];
381	echo "<a href='UserHooks.php?filepath=".$filepath."' target='page'>";?>user hook</a> rejects some events.)
382
383	<p/>
384	It is allowed to use external Les Houches Accord input for the
385	hardest process, and then pick an internal one for the second hardest.
386	In this case PYTHIA does not have access to your thinking concerning
387	the external process, and cannot know whether it overlaps with the
388	internal or not. (External events <i>q qbar' -> e+ nu_e</i> could
389	agree with the internal <i>W</i> ones, or be a <i>W'</i> resonance
390	in a BSM scenario, to give one example.) Therefore the combined cross
391	section is always based on the scenario (1) above. Corrections for
392	correlated parton densities are included also in this case, however.
393	That is, an external event that takes a large fraction of the incoming
394	beam momenta stands a fair chance of being rejected when it has to be
395	combined with another hard process. For this reason the "selected" and
396	"accepted" event numbers are likely to disagree.
397
398	<p/>
399	In the cross section calculation above, the <i>sigma'_1</i>
400	cross sections are based on the number of accepted events, while
401	the <i>f_1norm</i> factor is evaluated based on the cross sections
402	for selected events. That way the suppression by correlations
403	between the two processes does not get to be doublecounted.
404
405	<p/>
406	The <code>pythia.statistics()</code> listing contains two final
407	lines, indicating the summed cross sections <i>sigma_1sum</i> and
408	<i>sigma_2sum</i> for the first and second set of processes, at
409	the "selected" stage above, plus information on the <i>sigma_ND</i>
410	and <i><f_impact></i> used. The total cross section
411	generated is related to this by
412	<br/><i>
413	<f_impact> * (sigma_1sum * sigma_2sum / sigma_ND) *
414	(n_accepted / n_selected)
415	</i><br/>
416	with an additional factor of <i>1/2</i> for case 2 above.
417
418	<p/>
419	The error quoted for the cross section of a process is a combination
420	in quadrature of the error on this process alone with the error on
421	the normalization factor, including the error on
422	<i><f_impact></i>. As always it is a purely statistical one
423	and of course hides considerably bigger systematic uncertainties.
424
425	<h3>Event information</h3>
426
427	Normally the <code>process</code> event record only contains the
428	hardest interaction, but in this case also the second hardest
429	is stored there. If both of them are <i>2 -> 2</i> ones, the
430	first would be stored in lines 3 - 6 and the second in 7 - 10.
431	For both, status codes 21 - 29 would be used, as for a hardest
432	process. Any resonance decay chains would occur after the two
433	main processes, to allow normal parsing. The beams in 1 and 2
434	only appear in one copy. This structure is echoed in the
435	full <code>event</code> event record.
436
437	<p/>
438	Most of the properties accessible by the
439	<code><?php $filepath = $_GET["filepath"];
440	echo "<a href='EventInformation.php?filepath=".$filepath."' target='page'>";?>pythia.info</a></code>
441	methods refer to the first process, whether that happens to be the
442	hardest or not. The code and <i>pT</i> scale of the second process
443	are accessible by the <code>info.codeMPI(1)</code> and
444	<code>info.pTMPI(1)</code>, however.
445
446	<p/>
447	The <code>sigmaGen()</code> and <code>sigmaErr()</code> methods provide
448	the cross section and its error for the event sample as a whole,
449	combining the information from the two hard processes as described
450	above. In particular, the former should be used to give the
451	weight of the generated event sample. The statitical error estimate
452	is somewhat cruder and gives a larger value than the
453	subprocess-by-subprocess one employed in
454	<code>pythia.statistics()</code>, but this number is
455	anyway less relevant, since systematical errors are likely to dominate.
456
457	<input type="hidden" name="saved" value="1"/>
458
459	<?php
460	echo "<input type='hidden' name='filepath' value='".$_GET["filepath"]."'/>"?>
461
462	<table width="100%"><tr><td align="right"><input type="submit" value="Save Settings" /></td></tr></table>
463	</form>
464
465	<?php
466
467	if($_POST["saved"] == 1)
468	{
469	$filepath = $_POST["filepath"];
470	$handle = fopen($filepath, 'a');
471
472	if($_POST["1"] != "off")
473	{
474	$data = "SecondHard:generate = ".$_POST["1"]."\n";
475	fwrite($handle,$data);
476	}
477	if($_POST["2"] != "off")
478	{
479	$data = "SecondHard:TwoJets = ".$_POST["2"]."\n";
480	fwrite($handle,$data);
481	}
482	if($_POST["3"] != "off")
483	{
484	$data = "SecondHard:PhotonAndJet = ".$_POST["3"]."\n";
485	fwrite($handle,$data);
486	}
487	if($_POST["4"] != "off")
488	{
489	$data = "SecondHard:TwoPhotons = ".$_POST["4"]."\n";
490	fwrite($handle,$data);
491	}
492	if($_POST["5"] != "off")
493	{
494	$data = "SecondHard:Charmonium = ".$_POST["5"]."\n";
495	fwrite($handle,$data);
496	}
497	if($_POST["6"] != "off")
498	{
499	$data = "SecondHard:Bottomonium = ".$_POST["6"]."\n";
500	fwrite($handle,$data);
501	}
502	if($_POST["7"] != "off")
503	{
504	$data = "SecondHard:SingleGmZ = ".$_POST["7"]."\n";
505	fwrite($handle,$data);
506	}
507	if($_POST["8"] != "off")
508	{
509	$data = "SecondHard:SingleW = ".$_POST["8"]."\n";
510	fwrite($handle,$data);
511	}
512	if($_POST["9"] != "off")
513	{
514	$data = "SecondHard:GmZAndJet = ".$_POST["9"]."\n";
515	fwrite($handle,$data);
516	}
517	if($_POST["10"] != "off")
518	{
519	$data = "SecondHard:WAndJet = ".$_POST["10"]."\n";
520	fwrite($handle,$data);
521	}
522	if($_POST["11"] != "off")
523	{
524	$data = "SecondHard:TopPair = ".$_POST["11"]."\n";
525	fwrite($handle,$data);
526	}
527	if($_POST["12"] != "off")
528	{
529	$data = "SecondHard:SingleTop = ".$_POST["12"]."\n";
530	fwrite($handle,$data);
531	}
532	if($_POST["13"] != "off")
533	{
534	$data = "SecondHard:TwoBJets = ".$_POST["13"]."\n";
535	fwrite($handle,$data);
536	}
537	fclose($handle);
538	}
539
540	?>
541	</body>
542	</html>
543
544	<!-- Copyright (C) 2012 Torbjorn Sjostrand -->

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

Context Navigation

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

Download in other formats: