Subject:
L1 unpacker
From:
Marco Verzocchi <mverzocc@fnal.gov>
Date:
Wed, 04 May 2005 18:10:37 -0500
To:
Mike Hildreth <mikeh@fnal.gov>, Emanuela Barberis <barberis@fnal.gov>, Hal Evans <evans@nevis.columbia.edu>

Hi,
 Ok, Nikos wanted to have a meeting, which is partly what
we've discussed today....

 The code for the current L1 calorimeter unpacker is in
the l3funpack_l1cal packages in the L3UnpackL1Cal
class (look at the Unpack method). The code, as I had said,
is really trivial (it fills two arrays of 1280 numbers, the
ieta/iphi--->index mapping is defined in the header file).
The description of the data words is in this web page
(scroll down to "Detailed Data Format"):
http://www.pa.msu.edu/hep/d0/ftp/l1/cal_trig/readout/data_to_l2_cal_pp.txt

 Unfortunately I have removed from the code anything
which was doing an hexadecimal dump of the data,
which was great to understand how the data was
organized... Really with a documentation like this,
it should take 1 day of work to write the unpacker...

 This is for the TAB. The GAB will be a little more
complicated. But not much more.... If Nayeem has to
work on this and the decision is made to avoid IOGEN,
then he should probably insert back an hexadecimal dump
my code and be able to do the decoding of the L1CAL
information by hand looking at the screen. Then he could
move on and do the same thing for L1CAL2B.

 By the way, if he changes the code of this package,
then the online code is done, and one could simply
copy the code somewhere else (or put the code in
a separate package which is to be used from both
L3 and offline)....

 Cheers
            Marco

PS I would like to keep the TAB unpacker and the
    GAB unpacker separate....