/[PAMELA software]/yoda/techmodel/TmtcReader.cpp
ViewVC logotype

Log of /yoda/techmodel/TmtcReader.cpp

Parent Directory Parent Directory | Revision Log Revision Log


Links to HEAD: (view) (download) (annotate)
Links to YODA6_3/02: (view) (download) (annotate)
Sticky Tag:

Revision 6.3 - (view) (download) (annotate) - [select for diffs]
Tue May 30 19:10:03 2006 UTC (18 years, 6 months ago) by kusanagi
Branch: MAIN
CVS Tags: YODA6_3/00, YODA6_3/01, YODA6_3/02, YODA6_3/03, YODA6_3/04, YODA6_3/05, YODA6_3/06, YODA6_3/07, YODA6_3/08, YODA6_3/09, YODA6_3/10
Changes since 6.2: +2 -2 lines
Diff to previous 6.2
Major update.
All the packet officially produced by PAMELA are implemented and unpacked.
The RegistryEvent Packet has been removed and put into another library.
New version, releasd by D.Campana, of tofunpack.


Revision 6.2 - (view) (download) (annotate) - [select for diffs]
Tue May 30 19:10:02 2006 UTC (18 years, 6 months ago) by kusanagi
Branch: MAIN
Changes since 6.1: +3 -13 lines
Diff to previous 6.1
Major update.
All the packet officially produced by PAMELA are implemented and unpacked.
The RegistryEvent Packet has been removed and put into another library.
New version, releasd by D.Campana, of tofunpack.


Revision 6.1 - (view) (download) (annotate) - [select for diffs]
Tue Mar 21 21:49:07 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 -4 lines
Diff to previous 6.0
Update: adding the index ' k ', the index of the stored records is indipendent from the index ' i ' relative to the records read.
In this way if a record have a wrong CRC, the ' i ' index increase but the ' k ' dont.


Revision 6.0 - (view) (download) (annotate) - [select for diffs]
Tue Feb 7 17:11:10 2006 UTC (18 years, 10 months ago) by kusanagi
Branch: MAIN
CVS Tags: YODA6_0/00
Changes since 5.1: +3 -3 lines
Diff to previous 5.1
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.1 - (view) (download) (annotate) - [select for diffs]
Sat Feb 4 12:37:45 2006 UTC (18 years, 10 months ago) by kusanagi
Branch: MAIN
Changes since 5.0: +3 -3 lines
Diff to previous 5.0
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:46:13 2005 UTC (19 years, 3 months ago) by kusanagi
Branch: MAIN
CVS Tags: YODA5_0/00, YODA5_0/01, YODA5_0/02
Changes since 4.4: +2 -2 lines
Diff to previous 4.4
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.


Revision 4.4 - (view) (download) (annotate) - [select for diffs]
Mon May 23 13:53:43 2005 UTC (19 years, 6 months ago) by kusanagi
Branch: MAIN
CVS Tags: YODA4_3/02
Changes since 4.3: +3 -3 lines
Diff to previous 4.3
BugFix: wrong offset for TM_DEA_ANA (it was not 36 but 38)


Revision 4.3 - (view) (download) (annotate) - [select for diffs]
Mon May 23 11:53:48 2005 UTC (19 years, 6 months ago) by kusanagi
Branch: MAIN
CVS Tags: YODA4_3/01
Changes since 4.2: +3 -3 lines
Diff to previous 4.2
BugFix:  wrong offset of the subData reading TM_DEA_ANA. The error was introduced because
the 4 more thermistores bytes were not added to this offset.

before: rec->TM_DEA_ANA[j] = subData[30+j]
now: rec->TM_DEA_ANA[j] = subData[36+j]


Revision 4.2 - (view) (download) (annotate) - [select for diffs]
Mon May 16 15:36:33 2005 UTC (19 years, 6 months ago) by kusanagi
Branch: MAIN
CVS Tags: YODA4_3/00
Changes since 4.1: +3 -3 lines
Diff to previous 4.1
As lack in the CPU software 4 thermistores were missing.
Consequently the loop to read the TM_TH_ANA data has been set to 16 instead of the previous 12.


Revision 4.1 - (view) (download) (annotate) - [select for diffs]
Mon Mar 7 16:29:55 2005 UTC (19 years, 9 months ago) by kusanagi
Branch: MAIN
CVS Tags: YODA4_0/01, YODA4_0/02, YODA4_0/03, YODA4_0/04, YODA4_1/00, YODA4_2/00, YODA4_2/01, YODA4_2/03, yodaPreTermistores2_0/00, yodaPreTermistors2_1/00
Branch point for: PreThermistores2
Changes since 4.0: +4 -4 lines
Diff to previous 4.0
Parameter TM_TH_ANA was filled uncorrectly


Revision 4.0 - (view) (download) (annotate) - [select for diffs]
Sun Mar 6 04:33:02 2005 UTC (19 years, 9 months ago) by kusanagi
Branch: MAIN
Changes since 3.0: +2 -2 lines
Diff to previous 3.0
Stable version 4.0 - 6 March 2005 - Maurizio Nagni


Revision 3.0 - (view) (download) (annotate) - [select for diffs]
Fri Mar 4 15:54:11 2005 UTC (19 years, 9 months ago) by kusanagi
Branch: MAIN
Changes since 2.7: +2 -2 lines
Diff to previous 2.7
Error proof version.
Implemented all detectors packets plus all the main telemetries packets.
Missing all the Init and Alarm packets.
Disabled CRC control on VarDump, ArrDump, TabDump for CPU debugging needs
(the data formats seems correct even if CRC get wrong)


Revision 2.7 - (view) (download) (annotate) - [select for diffs]
Tue Feb 8 12:34:19 2005 UTC (19 years, 10 months ago) by kusanagi
Branch: MAIN
Changes since 2.6: +3 -3 lines
Diff to previous 2.6
Fix: there was a compilation warning about a missing "new line" at the end of the code


Revision 2.6 - (view) (download) (annotate) - [select for diffs]
Wed Dec 22 11:38:35 2004 UTC (19 years, 11 months ago) by kusanagi
Branch: MAIN
Changes since 2.5: +5 -5 lines
Diff to previous 2.5
Fixed EventReader file scan bugs


Revision 2.5 - (view) (download) (annotate) - [select for diffs]
Mon Dec 20 14:15:13 2004 UTC (19 years, 11 months ago) by kusanagi
Branch: MAIN
Changes since 2.4: +2 -23 lines
Diff to previous 2.4
*** empty log message ***


Revision 2.4 - (view) (download) (annotate) - [select for diffs]
Fri Dec 17 18:02:37 2004 UTC (19 years, 11 months ago) by kusanagi
Branch: MAIN
Changes since 2.3: +5 -5 lines
Diff to previous 2.3
*** empty log message ***


Revision 2.3 - (view) (download) (annotate) - [select for diffs]
Fri Dec 17 12:46:20 2004 UTC (19 years, 11 months ago) by kusanagi
Branch: MAIN
Changes since 2.2: +12 -13 lines
Diff to previous 2.2
*** empty log message ***


Revision 2.2 - (view) (download) (annotate) - [select for diffs]
Thu Dec 9 08:48:41 2004 UTC (20 years ago) by kusanagi
Branch: MAIN
Changes since 2.1: +4 -4 lines
Diff to previous 2.1
Fixed bug of Stack overflow in case of Log CRCError
Added S4Init & S4Alarm packets


Revision 2.1 - (view) (download) (annotate) - [select for diffs]
Fri Dec 3 22:08:01 2004 UTC (20 years ago) by kusanagi
Branch: MAIN
Changes since 2.0: +5 -10 lines
Diff to previous 2.0
Finally added a real group of Exception classes
Re-strucuted all the log systems (for better performances on unpacking)
Minor changes following the packets changes


Revision 2.0 - (view) (download) (annotate) - [select for diffs]
Tue Sep 21 20:50:54 2004 UTC (20 years, 2 months ago) by kusanagi
Branch: MAIN
Changes since 1.4: +2 -2 lines
Diff to previous 1.4
Major release


Revision 1.4 - (view) (download) (annotate) - [select for diffs]
Tue Sep 21 20:24:33 2004 UTC (20 years, 2 months ago) by kusanagi
Branch: MAIN
Changes since 1.3: +11 -13 lines
Diff to previous 1.3
Commit toward log4cxx plus new packets types Reader


Revision 1.3 - (view) (download) (annotate) - [select for diffs]
Tue Aug 24 16:01:57 2004 UTC (20 years, 3 months ago) by kusanagi
Branch: MAIN
Changes since 1.2: +2 -3 lines
Diff to previous 1.2
substituted some free() instructions changing them with the more proper delete []


Revision 1.2 - (view) (download) (annotate) - [select for diffs]
Sat Jul 17 20:03:38 2004 UTC (20 years, 4 months ago) by kusanagi
Branch: MAIN
Changes since 1.1: +27 -22 lines
Diff to previous 1.1
*** empty log message ***


Revision 1.1 - (view) (download) (annotate) - [select for diffs]
Tue Jul 6 12:20:23 2004 UTC (20 years, 5 months ago) by kusanagi
Branch: MAIN
Initial revision


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.

  Diffs between and
  Type of Diff should be a

Sort log by:

  ViewVC Help
Powered by ViewVC 1.1.23