3 /*! \page README_base Data definition and access
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..."
11 \section base_s1 How to dump the content of Root data files
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:
17 for MC information, use AliMUONMCDataInterface :
20 > aliroot (or root with just the loading of MUON libs, see loadlibs.C)
21 root [0] AliCDBManager::Instance()->SetDefaultStorage("local://$ALICE_ROOT/OCDB");
22 root [1] AliMUONMCDataInterface mcdi("galice.root");
23 root [2] mcdi.DumpKine(5); > dump.kine
24 root [3] mcdi.DumpHits(5); > dump.hits
25 root [4] mcdi.DumpTrackRefs(5); > dump.trackrefs
28 for all other information, use AliMUONDataInterface :
32 root [0] AliCDBManager::Instance()->SetDefaultStorage("local://$ALICE_ROOT/OCDB");
33 root [1] AliMUONDataInterface di("galice.root");
34 root [2] di.DumpDigits(5); > dump.digits
35 root [3] di.DumpSDigits(5); > dump.sdigits
36 root [4] di.DumpRecPoints(5); > dump.recpoints
37 root [5] di.DumpTrigger(5); > dump.rectrigger
40 Remind that during simulation and reconstruction two
41 differents galice.root are generated: one for the generation
42 (simulation) and other during the reconstruction.
44 If you open the wrong galice.root file you could get:
46 root [0] AliMUONMCDataInterface mcdi("galice.root");
47 root [1] mcdi.DumpKine(5);
48 W-AliRunLoader::GetEvent: Stack not found in header
49 E-TFile::TFile: file ./Kinematics.root does not exist
52 \section basee_s2 Macro MUONCheckDI.C
54 MUONCheckDI.C performs a consistency check on the methods of the
55 AliMUONMCDataInterface and AliMUONDataInterface classes. There are several
56 helper methods in these classes which make it easier to fetch data, which
57 means there are at least two ways of fetching the data within the same class
58 interface. The macro checks to see that the results given by these different
59 methods are identical, as they should be.
61 The macro also inherently exercises the AliMUONMCDataInterface and
62 AliMUONDataInterface classes and should be run after any modifications to
63 these classes to see if things still work. Putting it another way:
64 MUONCheckDI.C is a testing facility for developers of these two classes.
66 This chapter is defined in the READMEbase.txt file (although it describes
67 also the code in the evaluation library.)