We have not kept up with releases of the Online EBF library. We have been using 2.0.1. Release v3.0.0 was made on July 9. The big change was in the tracker interface. Starting with v3.0.0 strip data is presented in detetector space (tower, layer, etc.) rather than electronics space. In 3.1.0 a new class was added to aid in parsing CAL data. Both releases require change to client code.
The new tracker interface will not correctly identify minitower data, but will handle data from the full EM or simulated LAT data. Assuming future prototypes follow the rules, the v3.xx EBF library will parse their data correctly as well. Unless there is a hue and cry, I will assume that interest in minitower data will decline sharply as full EM data becomes available (just beginning to now). minitower data can still be read with those GlastRelease versions using the v2.0.1 EBF library.
Some small changes had to be made to v3.1 to get it to compile on Linux. One or two haven't yet made it into the official Online version. Also the changed tracker interface involved a loss of one piece of information: which end (high or low) a given strip was read out on. However this was done as a conscious choice; a slight change to the interface will reinstate it.
For now I have a private copy of the library which has all changes needed for Linux compilation and has the high/low information for strips. ebfReader has been modified to use the new interface. It and EbfConverter build properly and the test program output is not obviously wrong, but it needs to be examined more closely, particularly with input from the full EM. We are not making use of the enhanced CAL interface; perhaps we should be. Also there is a certain amount of streamlining to be done in ebfReader and EbfConverter before tagging.
Last modified: