[Rivet-svn] r4135 - trunk/doc

blackhole at projects.hepforge.org blackhole at projects.hepforge.org
Tue Feb 12 14:50:18 GMT 2013


Author: fsiegert
Date: Tue Feb 12 14:50:17 2013
New Revision: 4135

Log:
minor updates for the manual publication

Modified:
   trunk/doc/acknowledgements.tex
   trunk/doc/gettingstarted.tex
   trunk/doc/intro.tex

Modified: trunk/doc/acknowledgements.tex
==============================================================================
--- trunk/doc/acknowledgements.tex	Sat Feb  9 11:22:51 2013	(r4134)
+++ trunk/doc/acknowledgements.tex	Tue Feb 12 14:50:17 2013	(r4135)
@@ -12,6 +12,6 @@
 \end{itemize}
 
 We also wish to thank the CERN MCplots (\url{http://mcplots.cern.ch}) team, and
-especially Anton Karneyeu, for doing the pre-release testing of the Rivet 1.5
+especially Anton Karneyeu, for doing the pre-release testing since the Rivet 1.5
 series and pointing out all the bits that we got wrong: Rivet is a much better
 system as a result!

Modified: trunk/doc/gettingstarted.tex
==============================================================================
--- trunk/doc/gettingstarted.tex	Sat Feb  9 11:22:51 2013	(r4134)
+++ trunk/doc/gettingstarted.tex	Tue Feb 12 14:50:17 2013	(r4135)
@@ -285,7 +285,9 @@
     specify that the output histogram file will be named \kbd{foo.aida}. By
     default the output file is called \kbd{Rivet.aida}.}
 
-\item \textbf{Fine-grained logging: }{\kbd{rivet fifo.hepmc -A
+\item \textbf{Fine-grained logging: }
+
+  {\kbd{rivet fifo.hepmc -A
       -l~Rivet.Analysis=DEBUG~\cmdbreak -l~Rivet.Projection=DEBUG
       -l~Rivet.Projection.FinalState=TRACE~\cmdbreak -l~NEvt=WARN}
     will analyse events as before, but will print different status

Modified: trunk/doc/intro.tex
==============================================================================
--- trunk/doc/intro.tex	Sat Feb  9 11:22:51 2013	(r4134)
+++ trunk/doc/intro.tex	Tue Feb 12 14:50:17 2013	(r4135)
@@ -1,6 +1,6 @@
 This manual is a users' guide to using the Rivet generator validation
 system. Rivet is a C++ class library, which provides the infrastructure and
-calculational tools for simulation-level analyses for high energy collider
+calculational tools for particle-level analyses for high energy collider
 experiments, enabling physicists to
 validate event generator models and tunings with minimal effort and maximum
 portability. Rivet is designed to scale effectively to large numbers of analyses
@@ -22,8 +22,8 @@
 which provide no default way to produce HepMC output, the AGILe generator
 interface library, and in particular the \kbd{agile-runmc} command which it
 provides, may be useful. For those who wish to embed their analyses in some
-larger framework, Rivet can also be run programmatically on HepMC event objects
-with no special executable being required.
+larger framework, Rivet can also be used as a library to run programmatically
+on HepMC event objects with no special executable being required.
 
 Before we get started, a declaration of intent: this manual is intended to be a
 guide to using Rivet, rather than a comprehensive and painstakingly maintained
@@ -50,12 +50,12 @@
 argument name which should be replaced by a value,
 e.g. \code{Event::applyProjection(\val{proj})}.
 
-Following the example of Donald Knuth in his books on \TeX{}, in this document
-we will indicate paragraphs of particular technicality or esoteric nature with a
-``dangerous bend''\marginpar{\bendimg\\Dangerous bend} sign. These will
-typically describe internals of Rivet of which most people will be fortunate
-enough to remain happily ignorant without adverse effects. However they may be
-of interest to detail obsessives, the inordinately curious and Rivet
-hackers. You can certainly skip them on a first reading. Similarly, you may see
-double bend signs \marginpar{\dblbendimg\\Double bend} --- the same rules apply
-for these, but even more strongly.
+% Following the example of Donald Knuth in his books on \TeX{}, in this document
+% we will indicate paragraphs of particular technicality or esoteric nature with a
+% ``dangerous bend''\marginpar{\bendimg\\Dangerous bend} sign. These will
+% typically describe internals of Rivet of which most people will be fortunate
+% enough to remain happily ignorant without adverse effects. However they may be
+% of interest to detail obsessives, the inordinately curious and Rivet
+% hackers. You can certainly skip them on a first reading. Similarly, you may see
+% double bend signs \marginpar{\dblbendimg\\Double bend} --- the same rules apply
+% for these, but even more strongly.


More information about the Rivet-svn mailing list