[u/mrichter/AliRoot.git] / EVE / README

EVE - Event Visualization Environment
=====================================

EVE is composed of:
1. small application kernel;
2. graphics classes with editors and OpenGL renderers;
3. CINT scripts that extract data, fill graphics classes and register
   them to the application.

This is an early release ... expect problems and be sure that what you
need is not supported.


Usage
=====

1. Initialize ALICE environment.

2. Spawn 'reve' executable and invoke the alieve_init.C macro, for example:

To load first event from current directory:
   # reve  alieve_init.C 
To load 5th event from directory /data/my-pp-run:
   # reve 'alieve_init.C("/data/my-pp-run", 5)' 
Interactively:
   # reve
   root[0] .L alieve_init.C
   root[1] alieve_init("/somedir")

3. Use GUI or CINT command-line to invoke further visualization macros.
  
See files in EVE/alice-macros/. For specific uses these should be
edited to suit your needs.


Directory structure
===================

EVE is split into two modules: REVE (ROOT part, not dependent on
AliROOT) and ALIEVE (ALICE specific part). For the time being both
modules are kept in AliROOT CVS.

Alieve/ and Reve/ -- sources

macros/		  -- macros for bootstraping and internal steering
alice-macros/	  -- macros for ALICE visualization
alica-data/	  -- data files used by ALICE macros
test-macros/      -- macros for tests of specific features; usually one needs
                     to copy and edit them

bin/, Makefile and make_base.inc are used for stand-alone build of the
packages.
Commit	Line	Data
	1	EVE - Event Visualization Environment
	2	=====================================
	3
	4	EVE is composed of:
	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.
	9
	10	This is an early release ... expect problems and be sure that what you
	11	need is not supported.
	12
	13
	14	Usage
	15	=====
	16
	17	1. Initialize ALICE environment.
	18
	19	2. Spawn 'reve' executable and invoke the alieve_init.C macro, for example:
	20
	21	To load first event from current directory:
	22	# reve alieve_init.C
	23	To load 5th event from directory /data/my-pp-run:
	24	# reve 'alieve_init.C("/data/my-pp-run", 5)'
	25	Interactively:
	26	# reve
	27	root[0] .L alieve_init.C
	28	root[1] alieve_init("/somedir")
	29
	30	3. Use GUI or CINT command-line to invoke further visualization macros.
	31
	32	See files in EVE/alice-macros/. For specific uses these should be
	33	edited to suit your needs.
	34
	35
	36	Directory structure
	37	===================
	38
	39	EVE is split into two modules: REVE (ROOT part, not dependent on
	40	AliROOT) and ALIEVE (ALICE specific part). For the time being both
	41	modules are kept in AliROOT CVS.
	42
	43	Alieve/ and Reve/ -- sources
	44
	45	macros/ -- macros for bootstraping and internal steering
	46	alice-macros/ -- macros for ALICE visualization
	47	alica-data/ -- data files used by ALICE macros
	48	test-macros/ -- macros for tests of specific features; usually one needs
	49	to copy and edit them
	50
	51	bin/, Makefile and make_base.inc are used for stand-alone build of the
	52	packages.