source: HiSusy/trunk/Pythia8/pythia8170/phpdoc/RIVETusage.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: 3.5 KB
Line 
1<html>
2<head>
3<title>RIVET usage</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>
10function stopRKey(evt) {
11var evt = (evt) ? evt : ((event) ? event : null);
12var node = (evt.target) ? evt.target :((evt.srcElement) ? evt.srcElement : null);
13if ((evt.keyCode == 13) && (node.type=="text"))
14{return false;}
15}
16
17document.onkeypress = stopRKey;
18</script>
19<?php
20if($_POST['saved'] == 1) {
21if($_POST['filepath'] != "files/") {
22echo "<font color='red'>SETTINGS SAVED TO FILE</font><br/><br/>"; }
23else {
24echo "<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='RIVETusage.php'>
29
30<h2>RIVET usage</h2>
31
32<a href="http://projects.hepforge.org/rivet/">RIVET</a> is a toolkit for
33the validation of Monte Carlo event generators [<a href="Bibliography.php" target="page">Buc10</a>]. It
34contains the results of many experimental analyses, so that generator
35output can easily be compared to data, as well as providing a framework to
36implement your own analyses.  Although using PYTHIA with RIVET is not
37officially supported, some helpful hints are given below. The full RIVET
38manual is available <a href="http://arxiv.org/abs/1003.0694">online</a>.
39
40<br/><br/>
41<h3>Using PYTHIA with RIVET</h3>
42The following assumes that you already have RIVET installed. Instructions
43for this may be found
44<a href="http://projects.hepforge.org/rivet/trac/wiki/GettingStarted">
45here</a>.
46
47<br/><br/>
48Events are passed from PYTHIA to RIVET using the HepMC format. PYTHIA must
49be compiled with HepMC support, using the same version of HepMC used when
50compiling RIVET. This is setup through the PYTHIA <code>configure</code>
51script e.g.
52<pre>
53  ./configure --with-hepmc=/path/to/HepMC --with-hepmcversion=HepMC.version.number
54</pre>
55The PYTHIA library itself does not need to be recompiled.
56
57<br/><br/>
58The <code>examples/main42.cc</code> sample program can then be used to
59generate events in HepMC format (which <code>examples/main61.cc</code>
60and <code>examples/main62.cc</code> extends by allowing LHAPDF usage
61and subruns). When in the <code>examples</code> directory, the main program
62can be built and used as follows
63<pre>
64  make main42
65  ./main42 main42.cmnd main42.hepmc
66</pre>
67The first argument is the input file which provides the options for event
68generation, while the second is the output file where the HepMC events
69should be written.
70
71<br/><br/>
72This HepMC file may now be read and processed by RIVET
73<pre>
74  rivet --analysis=ANALYSIS_NAME main42.hepmc
75</pre>
76where <code>ANALYSIS_NAME</code> is a
77<a href="http://projects.hepforge.org/rivet/analyses">built-in RIVET
78analysis</a>, or one you have created yourself. The output of RIVET is in
79the form of <code>.aida</code> files, containing the histograms for the
80analysis, which can be processed further with RIVET (see the
81<a href="http://projects.hepforge.org/rivet/trac/wiki/FirstRivetRun">
82RIVET documentation</a> for more details).
83
84<br/><br/>
85The above examples requires that (potentially large) HepMC events are stored
86to disk before being read by RIVET. It is possible, instead, to pass the
87events directly to RIVET as they are produced by using a <code>FIFO</code>
88pipe. This is done with the <code>mkfifo</code> command
89<pre>
90  mkfifo my_fifo
91  ./main42.exe main42.cmnd my_fifo &
92  rivet --analysis=ANALYSIS_NAME my_fifo
93</pre>
94Note that <code>main42</code> is run in the background.
95
96</body>
97</html>
98
99<!-- Copyright (C) 2012 Torbjorn Sjostrand -->
Note: See TracBrowser for help on using the repository browser.