remoe duplicate QA initialisation and do ESD QA for same detectors as RecPoint QA
[u/mrichter/AliRoot.git] / MUON / READMEbase.txt
CommitLineData
91509ec6 1// $Id$
2
3/*! \page README_base Data definition and access
4
5Both the simulation and reconstruction use containers (called stores in the MUON jargon)
6to hold the data we're dealing with: hits, (s)digits, trigger, clusters, tracks and
7trigger tracks. All those stores share some commonalities, in particular with respect
8to how they are read/written from/to TTree. @ref AliMUONVStore "More..."
9
10
11\section base_s1 How to dump the content of Root data files
12
13To check the content of Root data files, the AliMUON*DataInterface classes
14provides the functions to produce an ASCII output on the screen
15which can be redirected on the file:
16
17for MC information, use AliMUONMCDataInterface :
18
19<pre>
20> aliroot (or root with just the loading of MUON libs, see loadlibs.C)
21root [0] AliMUONMCDataInterface mcdi("galice.root");
22root [1] mcdi.DumpKine(5); > dump.kine
23root [2] mcdi.DumpHits(5); > dump.hits
24root [3] mcdi.DumpTrackRefs(5); > dump.trackrefs
25</pre>
26
27for all other information, use AliMUONDataInterface :
28
29<pre>
30> aliroot
31root [0] AliMUONDataInterface di("galice.root");
32root [1] di.DumpDigits(5); > dump.digits
33root [2] di.DumpSDigits(5); > dump.sdigits
34root [3] di.DumpRecPoints(5); > dump.recpoints
35root [4] di.DumpTrigger(5); > dump.rectrigger
36</pre>
37
38Remind that during simulation and reconstruction two
39differents galice.root are generated: one for the generation
40(simulation) and other during the reconstruction.
41
42If you open the wrong galice.root file you could get:
43root [0] AliMUONMCDataInterface mcdi("galice.root");
44root [1] mcdi.DumpKine(5);
45W-AliRunLoader::GetEvent: Stack not found in header
46E-TFile::TFile: file ./Kinematics.root does not exist
47
48This chapter is defined in the READMEbase.txt file.
49
50\section basee_s2 Macro MUONCheckDI.C
51
52MUONCheckDI.C performs a consistency check on the methods of the
53AliMUONMCDataInterface and AliMUONDataInterface classes. There are several
54helper methods in these classes which make it easier to fetch data, which
55means there are at least two ways of fetching the data within the same class
56interface. The macro checks to see that the results given by these different
57methods are identical, as they should be.
58
59The macro also inherently exercises the AliMUONMCDataInterface and
60AliMUONDataInterface classes and should be run after any modifications to
61these classes to see if things still work. Putting it another way:
62MUONCheckDI.C is a testing facility for developers of these two classes.
63
64This chapter is defined in the READMEbase.txt file (although it describes
65also the code in the evaluation library.)
66
67*/