Main Page | Class Hierarchy | Alphabetical List | Class List | File List | Class Members | File Members | Related Pages

Release notes


Notes for V5.7.0 of LDF

Wed Sep 28 11:51:48 2005 - E. Charles


Notes for V5.6.3 of LDF

Sun Aug 14 14:08:15 2005 - R. Claus


Notes for V5.6.2 of LDF

Fri Apr 15 10:08:52 2005 - R. Claus


Notes for V5.6.1 of LDF

Fri Apr 01 16:08:11 2005 - R. Claus


Notes for V5.6.0 of LDF

Tue Mar 29 09:03:58 2005 - R. Claus


Notes for V5.5.1 of LDF

Tue Mar 15 11:00:00 2005 - J. Panetta


Notes for V5.5.0 of LDF

Wed Feb 23 15:30:00 2005 - J. Panetta


Notes for V5.4.1 of LDF

Mon Feb 14 17:45:00 2005 - J. Panetta


Notes for V5.4.0 of LDF

Mon Dec 13 16:24:41 2004 - R. Claus & J. Panetta


Notes for V5.3.0 of LDF

Thu Nov 18 11:00:00 2004 - J. Panetta


Notes for V5.2.0 of LDF

Tue Oct 25 14:15:16 2004 - R. Claus


Notes for V5.1.2 of LDF

Tue Aug 31 18:14:35 2004 - R. Claus


Notes for V5.1.1 of LDF

Mon Aug 02 20:15:36 2004 - R. Claus


Notes for V5.1.0 of LDF

Thu Jul 08 14:32:42 2004 - R. Claus & J. Panetta


Notes for V5.0.3 of LDF

Tue Tue Jun 01 18:59:21 2004 - R. Claus & J. Panetta


Notes for V5.0.2 of LDF

Tue May 04 16:09:41 2004 - R. Claus & J. Panetta


Notes for V5.0.1 of LDF

Fri Apr 23 16:11:05 2004 - R. Claus & J. Panetta


Notes for V5.0.0 of LDF

Wed Apr 14 13:29:41 2004 - R. Claus


Notes for V4.1.0 of LDF

Mon Apr 12 20:19:29 2004 - R. Claus

To do:


Notes for V4.0.1 of LDF

Wed Apr 07 20:11:23 2004 - R. Claus


Notes for V4.0.0 of LDF

Tue Feb 10 18:25:16 PST 2004 - R. Claus

Still to be done:


Notes for V3.3.0 tag of EBF

Wed Mar 17 14:14:00 PST 2004 - J Panetta

In preparation for V4 release, jhp-040206 is being tagged as V3.3.0 for the ACD group.


Notes for jhp-040206 tag of EBF

Fri Feb 6 17:33:00 PST 2004 - J Panetta

Added AEMcontributionIterator to iterate over the AEM contribution of the event without user coding.

Provided pure virtual function callbacks:

for the user to implement.


Notes for V3.2.2 of EBF

Thu Jan 22 15:19:00 PST 2004 - J Panetta

Modified bits in aemBuf() to match defining comment (hitMap == acceptMap)

Fixed parsing of AEM header and ordering of AEM pha values as per AEM primer, section 3.2.1 Ver 2.6. Closing LATTE Issue #37

Updated comments on location of AEM data definition


Notes for V3.2.0 of EBF

Mon Dec 15 14:05:43 PST 2003 - J Panetta

Added Linux support for EBF. See README for build instructions


Notes for V3.1.7 of EBF

Mon Dec 1 15:26:15 PST 2003 - J Panetta

Added DIAGcontributionIterator and ERRcontributionIterator to iterate over the diagnostic component of the TEM contribution and the error component respectively. Added a TKRdiagnostic object to reference into the bitfield defined in the TEM primer.

TKRdiagnostic provides the function hooks:

DIAGcontributionIterator provides the following function hooks:

and callbacks:

The callbacks can be implemented by the user if the data is needed. By default, they are implemented as null functions.

ERRcontributionIterator provides the following function hooks:

and callbacks:

As above, these callbacks may be implemented by the user if the data is needed. By default, they are implemented as null functions.

Example code for the use of these iterators is contained in the files test/EBFdump.cpp (C++) and in EBFdumper.py (python).


Notes for V3.1.6 of EBF

Thu Oct 23 2003 - J Panetta

Changed compiler flag _WIN32_STATIC to _WIN32_EBF_STATIC at request of offline. [libApiExport.h]


Notes for V3.1.5 of the EBF package

Tue Oct 15 15:16:20 2003 - J Panetta

Added support for statically linked EBF under Windows (Offline request). Add the compiler flag _WIN32_STATIC to activate. [libApiExport.h]

Fixed a counting error in the calculation of the end-of-contribution. [TEMcontributionIterator.h]

Minor mods to setupEBF.sh and setupEBF.bat.

Forgot to add the sln file for EBF/test. [EBFdump.sln]


Notes for V3.1.4 of the EBF package

Sun Aug 31 18:17:40 2003 - R. Claus

Added support for two extra longwords added to the end of the GEM contribution. These contain the results from reading the PPC timebase register at the point that the event is first recognised by Online software in the SBC. This register counts at 16 MHz (60 ns ticks) on the MVME2306 SBCs currently supported by Online. Beware that the counting rate is implementation dependent when using PPC SBCs other than the MVME2306. See EBF/EBFdumper.py and EBF/test/EBFdump.cpp for examples on how to access this data.

Note for posterity: we observe that the minimum event spacing is about 200 uS, presumibly occuring when several events are stacked up in the various buffers (TEM and LAT COMM card) thus causing the readout software to work at the maximum rate.


Notes for V3.1.3 of the EBF package

Tue Aug 26 13:17:33 2003 - R. Claus

Changed the TKRcontributionIterator::strip() virtual function interface to provide layerEnd instead of layer. Affected files are TKRcontributionIterator.h, EBFdumper.py, EBFdump.cpp. Fixed various syntax problems to prevent some compilers from issuing warnings.


Notes for V3.1.2 of the EBF package

Wed Aug 20 10:19:00 2003 - J. Panetta

Fixed two problems in EBFdump.cpp. -#) replaced getch() with getchar(). -#) Fixed a variable out of scope problem that gcc caught and VC++ didn't.


Notes for V3.1.0 of the EBF package.

Thu Aug 06 18:07:20 2003 - J. Panetta

Added CALcontributionIterator to EBF library to remove iteration over the CAL data from the user's hands. Provided pure virtual function log(unsigned tower, unsigned layer, CALlog theLog) for the user to implement. Modified CALlog.h to return a CALlogEnd object in place of an unsigned.

Added offsets to the end of {CAL,TKR,diag,err} data to TEMcontributionIterator. A portion of this functionality was in TKRcontributionIterator, but the diag and err data are part of the TEM contribution.

Implemented the parsing of diagnostics and errors in EBFdump.cpp. This was done a little differently from the python version, taking advantage of #defines to transparently swap bytes when needed.

Added a cleanup() method to TEMcontributionIterator. This method looks in the area between the last useful TEM data and the end of the contribution and checks whether it is both: a) less than one cell away; b) all zeroes. This checks for an error in the TEM hardware where multiples of the last TOT are written to the event stream.

Moved the dump() methods of My{TKR,CAL}contribution in the example files (EBFdump.cpp, EBFdumper.py) to the Iterators. This reverses a dependency of the contribution on the iterator.

Until a SIP error is dealt with, the cleanup(), diagnostic() and error() methods of the LATcomponentIterator class are required to be implemented in user python code. These methods are allowed to be dummies.

This release is consistent with existing data files.


Notes for v3.0.0 of the EBF package.

Wed Jul 09 22:43:02 2003 - R. Claus

Changed the tracker iterator callback method signatures from the "electronics space" notation of v2.0.x to "detector space" notation. This is almost the same as it was for v01-00-00 except "layerEnd" is now correctly calculated. LayerEnd = layer * 2 + (1 bit indicating whether the value was read from the low or the high end of the MCM). LayerEnd is provided to the TOT virtual method where the side the TOT was read from is interesting. Layer is provided to the strip virtual method where the side the hit was read from is not interesting.

Provided geometry remapping private methods in TKRcontributionIterator.h to handle the nonstandard geometry of the first TKR Minitower. The code must be recompiled to handle different geometries. Since the data from the first minitower has already been taken and thus tagged with a particular format version number, and monte carlo data files have been generated with this same format version number, the code can't distinguish which files have which geometries. It's not clear what to do about this.

In anticipation that FSW will only one copy of the summary word, contribution signatures were changed to access the summary word through the EBFevent interface. All contributions should have been able to find the event header anyway. The contribution summary words can still be accessed through the contribution classes, but this may change in the future.

The known problem of v2.0.1 turned out to indeed be a TEM hardware error that has subsequently been fixed in the firmware.

This release is consistent with existing data files.


for v2.0.1 of the EBF package.

Thu May 08 19:54:38 2003 - R. Claus

Found that there was an alignment problem when decoding the Tracker TOTs and fixed it. One set of the error pathologies that didn't decode correctly in v2.0.0 now do. The remaining known pathology that doesn't decode correctly looks to be due to a TEM hardware error. A replicated TOT and subsequent padding appears where an error contribution is expected.

Known problems:


Notes for v2.0.0 of the EBF package.

Thu May 08 12:19:47 2003 - R. Claus

Changed the tracker iterator callback method signatures so that users don't have to decode layer-end into CC and RC numbers. If in the future the definition of the accepts mask changes, the change can be hidden in the EBF code so that user code does not have to change. I haven't yet updated all my Python test code to cope with these changes.

Also added the ability to dump text files using EBFdump.py. The text files contain hex dumps of an event buffer.

Known problems:


Notes for v1.0.0 of the EBF package.

Wed Mar 19 19:11:37 2003 - R. Claus

This package contains a set of C++ classes for navigating the second version of Event Builder Format (EBF) event data. It also includes code necessary for exposing these C++ classes to Python (the sip files).

The major difference between the current version (v01-00-00) of the EBF package and the previous release (v00-00-00) is that the EBF data as described by Mike Huffer's LAT Inter-module Communications document (LAT-TD-00606) is now augmented with an type/identity value and encapsulated in a "LATdatagram". The datagram has it's own type/identity value, but is of interest because it is extendable. This means that besides an EBF contribution, there may be other contributions to an "event". None are currently defined.

The type/identity value (LATidentity.h) is used to give each transmissible object a "type". Associated with the type is an identifier that is typically used as a version number of the type. A piece of software can then recognize whether it is equiped to deal with the data with which it is presented. It could either decide to bail out if it isn't or dynamically load a library that can.

The EBF format itself has changed from the previous release somewhat in that a couple of extra fields have been added to EBFcontribution and the units of the length field are now in LATp cells rather than bytes. The EBFcontribution::length() method still returns units of bytes, i.e., the change is backwardly compatible.

A program called cvtData-NoneTo1 is provided in the EBF/test directory to convert the data format v00-00-00 handles to the data format that v01-00-00 handles.

What is still needed:

C++ usage:

Create a class derived from LATcomponentIterator, filling in those virtual functions appropriate to your application. Those you don't need can be omitted, since they are defaulted.

See EBFdump.cpp in the test directory. Read from the bottom up.

Python usage:

See eventFormat.py in the test directory.


Notes for v0.0.0 of the EBF package.

Thu Feb 20 14:59:55 2003 - R. Claus

This package contains a set of C++ classes for navigating Event Builder Format (EBF) event data. It also includes code necessary for exposing these C++ classes to Python (the sip files).

What is still needed:


Generated on Thu Sep 29 12:13:47 2005 for LDF v05-07-00 by doxygen 1.3.9.1