Date: Wed, 11 May 2005 11:51:31 -0400 (EDT) From: Todd Adams Subject: TAB Header info I'm wondering if the TAB header will contain information about which ieta,iphi region the TAB corresponds to. According to the documentation and hex dumps, the TAB header will be included in the L3 data. This header appears to have the same format as the L2 header documented in the Run 2a data (http://www.pa.msu.edu/hep/d0/ftp/l1/cal_trig/readout/data_to_l2_cal_pp.txt). According to this documentation, the "Data Type" gives a number which indicates the eta coverage (see end of this note). Will the Run 2b data include a similar code? This will be especially useful when only a portion of the TAB boards are included in the test runs. Any help on finding documentation is appreciated. - Todd From the L1Cal Run2a data format documentation: (3) Data Type is a byte that is programmed by TCC and fixed from event to event. From the L2 Web Documents it appears to label what crate the data comes from with decimal values 98 through 107, i.e. a different value for each one of the L1 Cal Trig racks - fiber optic links. This is good because for our own L1 use we need a "source label" built into each data source. We will use the following map of Data Types: Rack Eta Index Location Coverage Data Type -------- --------- --------- M103 +1:+4 98 M104 -4:-1 99 M105 +5:+8 100 M106 -8:-5 101 M107 +9:+12 102 M108 -12:-9 103 M109 +13:+16 104 M110 -16:-13 105 M111 +17:+20 106 M112 -20:-17 107 ===================================================================== Date: Wed, 11 May 2005 12:03:47 -0400 From: Hal Evans To: Todd Adams Subject: Re: TAB Header info Hi Todd, An "L2 Data Type" word that provides phi-coverage information in the TAB headers is currently *not* coded into the firmware. Note that each TAB covers the entire eta range - so no eta information is necessary. This could certainly be added in - but it would require the phi-coverage information to be downloaded to the boards at initialization. I'm also not sure that it would gain us very much in the initial testing phase since the phi's covered by the split TTs we will be using to write data will change frequently and in a non-regular way. Regards - Hal ===================================================================== Date: Wed, 11 May 2005 12:36:26 -0400 (EDT) From: Todd Adams To: Hal Evans Subject: Re: TAB Header info Hal, OK, but then how shall we associate a given TT in L3 with its location in ieta,iphi space? I had assumed this would be critical if we want to compare L1Cal2B info with L1Cal2A and precision readout. Is there a known mapping between VRB module/chan which can be used? If no reliable information is provided, I can unpack the available VRBs in consecutive order and fill my data structure in that order, but then the user will have to know how to map the available data to the proper location. - Todd