Log of /yoda/event/RegistryEvent.h
Parent Directory
| 
Revision Log
Revision
6.1 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Mon Mar 27 08:42:15 2006 UTC
(18 years, 8 months ago)
by
kusanagi
Branch:
MAIN
CVS Tags:
YODA6_1/00,
YODA6_2/00,
YODA6_2/01
Changes since
6.0: +8 -2 lines
Diff to
previous 6.0
Added IDRun parameter; this is the unique ID of the RUN from which this data cames from. Even if this ID cames from the production database it can be considered decoupled from the database. It is used when many RUNs are collected in a single file.
Revision
6.0 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Tue Feb 7 17:11:07 2006 UTC
(18 years, 9 months ago)
by
kusanagi
Branch:
MAIN
CVS Tags:
YODA6_0/00
Changes since
5.4: +1 -1 lines
Diff to
previous 5.4
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.
Revision
5.3 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Tue Feb 7 08:42:43 2006 UTC
(18 years, 9 months ago)
by
kusanagi
Branch:
MAIN
Changes since
5.2: +12 -4 lines
Diff to
previous 5.2
Added a field "TString originFile" in case multiple data are collected from several unpacked/Level2 root files using the "Data & Registry" TBranches structure.
Revision
5.2 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Sat Feb 4 12:37:43 2006 UTC
(18 years, 10 months ago)
by
kusanagi
Branch:
MAIN
Changes since
5.1: +2 -2 lines
Diff to
previous 5.1
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.
Revision
5.0 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Mon Aug 29 09:45:48 2005 UTC
(19 years, 3 months ago)
by
kusanagi
Branch:
MAIN
CVS Tags:
YODA5_0/00,
YODA5_0/01
Changes since
4.1: +2 -2 lines
Diff to
previous 4.1
Starting form this version:
1) includes are defined with relative (not absolute) path respect to the YODA aplication
2) RegistryEvent class is foreseen to contain post-unpack data.
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
select a symbolic revision name using the selection box, or choose
'Use Text Field' and enter a numeric revision.
