/[PAMELA software]/yoda/README
ViewVC logotype

Annotation of /yoda/README

Parent Directory Parent Directory | Revision Log Revision Log

Revision 6.0 - (hide annotations) (download)
Tue Feb 7 17:10:40 2006 UTC (19 years, 8 months ago) by kusanagi
Branch: MAIN
CVS Tags: YODA6_0/00
Changes since 5.1: +0 -0 lines 
Several new features in this revision:
a) all the packets are conform to the Mass Memory Format specifications (http://people.roma2.infn.it/~cpu/Mass_Memory_Format.html)
b) unpacking either using the old files structure OR the new one file unpacking.
c) parametrized root files compression factor
d) deleting of the following packet: TofTest, TrkTest, TrkEvent.
e) the Tracker routines now work without the use of temp files.

The point a) allow Yoda to unpack in the root file all the packets generated by the CPU. According to the MassMemoryFormat; that is three possible data are available:

1) almost explicit structure of the packet (like for Log, Tracker, Mcmd, etc....);
2) dummy data collection structure (InitHeader, InitTrailer, CalibHeader, CalibTrailer);
3) just the data of the packet (almost all Alarm and Init procedures). The class regarding this packets have only one parameters, a TArrayC class, which contain the data-block included in the packet (tat is the data below the packet Header).

The point b) has been implemented as a consequence of an agreement about a more compact structure of the unpacked data. Up to now the structure of each unpacked data consisted of a folder, named after the packet type, and three files: xxx.Header.root, xxx.NamePacket.root, xxx.Registry.root.
Starting from this release YODA, by default will unpack the data in a unique root file. The structure of this file will consist of:
- several TTree(s) named after the packet type;
- into each TTree are foreseen three TBranche(s):
    - 'Header'  (the old xxx.Header.root file)
    - 'NameOfThePacket' (the old xxx.Event.root file or the xxx.Event.DETECTOR.root)
    - 'Registry' (the old xxx.Registry.root file)

Anyway is still possible, but deprecated, to unpack using the old structure, passing to the "yoda" command the optional parameter "-multifile"

The point c) has been implemented because is well know that writing time in a TTree is as much fast as much lower is the compression factor for the root file; anyway for a PAMELA dat file, a compression equal to 0 will generate a root file which will be more than two times the original size. To modify the compression parameter just add the optional parameter "-c [0-9]" to the yoda command line.
1 kusanagi 2.5 Install procedure 2.x - Nagni 15 February 2005
2 kusanagi 1.1
3     To install YODA:
4    
5     1) check that you have installed ROOT and your enviroment have defined
6    
7     #-----YODA's Environment-----------------------
8     # this variable define where YODA will write the managed files
9     export YODA_DATA= YourPathToStoreUnpackedFiles
10     #-----YODA's Environment-----------------------
11    
12     #-----Cern's ROOT Environment-----------------------
13     export ROOTSYS=/usr/share/root
14     export PATH=$ROOTSYS/bin:$PATH
15     export LD_LIBRARY_PATH=$ROOTSYS/lib
16     #-----Cern's ROOT Environment-----------------------
17    
18     2) check that you have installed
19 kusanagi 1.3 ---->log4cxx (jakarta logger for c++ programs)
20 kusanagi 1.1 ---->g77 (GNU FORTRAN Compiler)
21     ---->LIBTOOL (compiler utility)
22    
23     3) create a directory (say YOUR_YODA) and copy the source into it
24    
25 kusanagi 5.1 4) execute the following commands (please customize the ./configure line according to your system)
26 kusanagi 1.1
27     $ cd $YODA_ROOT
28 kusanagi 2.1 $ autoheader
29 kusanagi 1.2 $ libtoolize (eventually "libtoolize --force")
30 kusanagi 5.1 $ export CFLAGS="-g -O4"
31     $ export FFLAGS="-g -O0 -keepC"
32     $ export CXXFLAGS="-g -O4"
33 kusanagi 1.1 $ aclocal
34     $ automake -a
35     $ autoconf
36 kusanagi 5.1 $ ./configure --prefix=/path/where/you/want/to/install --with-log4cxx=/opt/log4cxx --enable-gprof=no
37     $ make
38 kusanagi 1.1
39     that a look at the configure options
40     $ ./configure --help
41    
42     $ ./configure
43    
44 kusanagi 2.3 $ make
45 kusanagi 1.1
46 kusanagi 2.3 then became ROOT user to install YODA
47 kusanagi 1.1
48 kusanagi 2.3 $ make install
49 kusanagi 1.1
50 kusanagi 2.5 if everthing has been correct typing
51    
52     $ yoda
53    
54     the program should reply something like below
55    
56     You have forgotten the file name.
57     Try '--help' for more information.
58    
59    
60    
61 kusanagi 1.1
62 kusanagi 2.2 ------>NOTE 1<------
63     On the source code is supplied also a tipical configuratin file for the Log4cxx tool.
64 kusanagi 2.4 The file is named log4cxx.conf and is designed to be put into the YODA_DATA directory.
65     Notice that to set the output detail level you have to modify the log4cxx.conf
66     according to your needs.
67 kusanagi 1.1
68 kusanagi 2.3 ------>NOTE 2<------
69     Because of major changes in ROOT, Trees produced with a version of ROOT greater than 4.01/02
70 kusanagi 2.4 cannot be read by older ROOT versions.
71    
72     ------>NOTE 3<------
73 kusanagi 5.1 If you are doing an upgrading is highly recomended to uninstall your previous version.
  ViewVC Help
Powered by ViewVC 1.1.23