White-space.
[u/mrichter/AliRoot.git] / EVE / README
CommitLineData
5a5a1232 1EVE - Event Visualization Environment
2=====================================
3
4EVE is composed of:
51. small application kernel;
62. graphics classes with editors and OpenGL renderers;
73. CINT scripts that extract data, fill graphics classes and register
8 them to the application.
9
7c56a308 10The framework is still evolving ... some things might not work as expected.
5a5a1232 11
12
13Usage
14=====
15
161. Initialize ALICE environment.
17
5987168b 182. Spawn 'alieve' executable and invoke the alieve_init.C macro, for example:
5a5a1232 19
20To load first event from current directory:
5987168b 21 # alieve alieve_init.C
5a5a1232 22To load 5th event from directory /data/my-pp-run:
5987168b 23 # alieve 'alieve_init.C("/data/my-pp-run", 5)'
5a5a1232 24Interactively:
5987168b 25 # alieve
5a5a1232 26 root[0] .L alieve_init.C
27 root[1] alieve_init("/somedir")
28
293. Use GUI or CINT command-line to invoke further visualization macros.
71d91e82 30
314. To navigate the events use macros 'event_next.C' and 'event_prev.C'.
32 These are equivalent to the command-line invocations:
33 root[x] Alieve::gEvent->NextEvent()
34or
35 root[x] Alieve::gEvent->PrevEvent()
36The general form to go to event via its number is:
37 root[x] Alieve::gEvent->GotoEvent(<event-number>)
38
528fcc86 39See files in EVE/alice-macros/ from the ROOT browser that is spawned
40automatically with the application. They can be executed directly from
41the browser (by dpouble-clicking on their icon) or via standard ROOT's
42macro execution methods using '.x' and '.L'. If you want to pass the
43arguments to the macros, use '.L' as this gives you automatic tab
44completion.
45
46For specific uses you can copy them and edit them to suit your needs.
5a5a1232 47
48
49Directory structure
50===================
51
52EVE is split into two modules: REVE (ROOT part, not dependent on
53AliROOT) and ALIEVE (ALICE specific part). For the time being both
54modules are kept in AliROOT CVS.
55
56Alieve/ and Reve/ -- sources
57
58macros/ -- macros for bootstraping and internal steering
59alice-macros/ -- macros for ALICE visualization
60alica-data/ -- data files used by ALICE macros
915dabe1 61test-macros/ -- macros for tests of specific features; usually one needs
62 to copy and edit them
5a5a1232 63
64bin/, Makefile and make_base.inc are used for stand-alone build of the
65packages.
7c56a308 66
67
be55f120 68Examples
69========
70
711. Run the interface for visual scanning:
72
73alieve -mode 2 trackcount_init.C
74
75
7c56a308 76Notes
77=====
78
791. Problems with macro-execution
80--------------------------------
81
82A failed macro-execution can leave CINT in a poorly defined state that
83prevents further execution of macros. For example:
84
85 Exception Reve::Exc_t: Event::Open failed opening ALICE ESDfriend from
86 '/alice-data/coctail_10k/AliESDfriends.root'.
87
88 root [1] Error: Function MUON_geom() is not defined in current scope :0:
89 *** Interpreter error recovered ***
90 Error: G__unloadfile() File "/tmp/MUON_geom.C" not loaded :0:
91
92'gROOT->Reset()' helps in most of the cases.
be55f120 93
94This has been fixed for most cases.