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