/[PAMELA software]/yoda/event/log/LogEvent.h
ViewVC logotype

Annotation of /yoda/event/log/LogEvent.h

Parent Directory Parent Directory | Revision Log Revision Log

Revision 5.1 - (hide annotations) (download)
Sat Feb 4 12:37:44 2006 UTC (18 years, 9 months ago) by kusanagi
Branch: MAIN
Changes since 5.0: +2 -2 lines
File MIME type: text/plain 
Several new features in this release:
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 1.1 /** @file
2 kusanagi 2.0 * $Source: /home/cvsmanager/yoda/event/log/LogEvent.h,v $
3 kusanagi 5.1 * $Id: LogEvent.h,v 5.0 2005/08/29 09:46:12 Maurizio Nagni Exp $
4     * $Author: Maurizio Nagni $
5 kusanagi 1.1 *
6     * Header file for the LogEvent class.
7     */
8     #ifndef LOG_EVENT_H
9     #define LOG_EVENT_H
10    
11     #include <vector>
12 kusanagi 4.5 #include "LogRecord.h"
13 kusanagi 1.1 #include <TClonesArray.h>
14     using namespace std;
15    
16     namespace pamela {
17     /**
18 kusanagi 4.1 * LogEvent data Wrapper.
19     *
20     * The LogEvent represents the "LogEvent" packet generated by the PAMELA CPU software
21     * and is a collection of several logs generated during PAMELA operations
22     * and recorded in the CPU RAM between two storing operations.
23 kusanagi 1.1 */
24     class LogEvent: public pamela::SubPacket {
25     private:
26 kusanagi 4.1
27 kusanagi 1.1 static TClonesArray *fgRecords;
28     public:
29     /**
30 kusanagi 4.1 * The Compilation Timestamp of the PAMELA CPU software.
31 kusanagi 1.1 */
32 kusanagi 2.1 UINT32 COMPILATION_TIMESTAMP;
33 kusanagi 4.1
34     /**
35     * Contain multiple instances of pamela::LogRecord type.
36     */
37 kusanagi 1.1 TClonesArray* Records;
38    
39     LogEvent(void);
40     ~LogEvent(void);
41    
42     ClassDef(LogEvent, 1)
43     };
44     }
45    
46     #endif /* LOG_EVENT_H */
47    
  ViewVC Help
Powered by ViewVC 1.1.23