New method fos accessing raw-event object directly. Needed by EMCAL for some special...

[u/mrichter/AliRoot.git] / html / howtorun.html

diff --git a/html/howtorun.html b/html/howtorun.html
index ccccfc7c24a7a60b088c63b7783bb3c471e6a8a5..ed229338f88f705b8860565c33f5c1cb7757fb56 100644 (file)
--- a/html/howtorun.html
+++ b/html/howtorun.html
@@ -40,11 +40,13 @@ COL, COLGROUP, TABLE, TBODY, TD, TR {
 
 <LI><A HREF="#A more detailed view">A more detailed view</A></LI>
 
+<LI><A HREF="#Batch processing">Batch processing</A></LI>
+
 </UL>
 
 <HR>
 
-<h3><A HREF="#Content" NAME="For the impatient">For the impatient user</A></h3>
+<h2><A HREF="#Content" NAME="For the impatient">For the impatient user</A></h2>
 
 <p> <a href="picts/menubar.gif">
 <img src="picts/menubar.gif" alt="AliRoot menu bar"
@@ -126,8 +128,7 @@ Note that some pictures may take a long time to be produced.
 
 <p> <KBD>root [ ] .q</KBD>
 
-<h3>A more detailed view</h3>
-<h3><A HREF="#Content" NAME="A more detailed view">A more detailed view</A></h3>
+<h2><A HREF="#Content" NAME="A more detailed view">A more detailed view</A></h2>
 
 <p> After startup of the <b>aliroot</b> program the simulation
 infrastructure is initialised by the <a
@@ -179,18 +180,67 @@ to be processed. If this number is negative, the run is not terminated and
 more events can be run. If this number is positive, after the indicated number
 of events the run is terminated. No more events can be run.
 
-<h3>Batch processing</h3>
+<h2><A HREF="#Content" NAME="Batch processing">Batch processing</A></h2>
 
 <p> In AliRoot there is really no difference between batch and interactive
 processing. An <a href="roothtml/examples/grun.C.html">elementary macro</a>
 to run AliRoot in batch mode is provided amongst the examples, and it can
 be used in the following way to run a 10 events run
 
-<p> <KBD> aliroot -b grun.C\(10\)</KBD>
+<p> <KBD> aliroot -b -q grun.C\(10\)</KBD>
 
 <p> Note that the backslashes are necessary to prevent the shell from
 interpreting the brackets.
 
+<p> For very large output files we strongly discourage the use of afs
+space, as it has performance penalty and it is really intended to be used
+for user and program files and not data files. Users needing access to
+large data files should use the ALICE staging facility. The procedure is
+the following:
+
+<p><ol>
+
+<li> Define a <var>STAGE_HOST</var> variable which is in our case
+<var>shiftalice</var>
+
+<p><li> In your <var>Config.C</var> macro, or in any other place where
+you open a file, instead of opening the file as
+
+<p><kbd>
+   TFile *f = new TFile("filename","option");
+</kbd>
+
+<p>use
+
+<p><kbd>
+   TFile *f = TFile::Open("rfio:filename","option");
+</kbd>
+
+<p><li>Stage a file via the command
+<p><kbd>
+   stagealloc -p alice_stage filename
+</kbd>
+
+<p>This will create in your working directory a link <var>filename</var>
+that points to the <em>real</em> file in the stage pool.
+
+<p><li>Now you can run
+
+<p><li>When done with the file, do not <kbd>rm filename</kbd>. It will
+remove the link only, the file will still be in the pool, occupying our
+precious disk space. To delete a staged file instead do
+<p><kbd>
+   stageclr -P `stageqry -p alice_stage -A filename -P`
+</kbd>
+<p>and this will do a proper job.
+</ol>
+
+<p>More information on stage can be found in the <a
+href="http://wwwinfo.cern.ch/pdp/castor/doc/public/all_man_pages.html">man pages</a> of
+the different stage commands or in the CORE <a
+href="http://wwwinfo.cern.ch/pdp/sc/coreplus.html">User Guide</a>.
+
+<br clear>
 <hr>
 <address>
           Last modified Thu Oct 07 11:33:05 1999