1 EVE - Event Visualization Environment
2 =====================================
5 1. small application kernel;
6 2. graphics classes with editors and OpenGL renderers;
7 3. CINT scripts that extract data, fill graphics classes and register
8 them to the application.
10 This is an early release ... expect problems and be sure that what you
11 need is not supported.
17 1. Initialize ALICE environment.
19 2. Spawn 'alieve' executable and invoke the alieve_init.C macro, for example:
21 To load first event from current directory:
22 # alieve alieve_init.C
23 To load 5th event from directory /data/my-pp-run:
24 # alieve 'alieve_init.C("/data/my-pp-run", 5)'
27 root[0] .L alieve_init.C
28 root[1] alieve_init("/somedir")
30 3. Use GUI or CINT command-line to invoke further visualization macros.
32 4. To navigate the events use macros 'event_next.C' and 'event_prev.C'.
33 These are equivalent to the command-line invocations:
34 root[x] Alieve::gEvent->NextEvent()
36 root[x] Alieve::gEvent->PrevEvent()
37 The general form to go to event via its number is:
38 root[x] Alieve::gEvent->GotoEvent(<event-number>)
40 See files in EVE/alice-macros/. For specific uses these should be
41 edited to suit your needs.
47 EVE is split into two modules: REVE (ROOT part, not dependent on
48 AliROOT) and ALIEVE (ALICE specific part). For the time being both
49 modules are kept in AliROOT CVS.
51 Alieve/ and Reve/ -- sources
53 macros/ -- macros for bootstraping and internal steering
54 alice-macros/ -- macros for ALICE visualization
55 alica-data/ -- data files used by ALICE macros
56 test-macros/ -- macros for tests of specific features; usually one needs
59 bin/, Makefile and make_base.inc are used for stand-alone build of the