Revised 31 Oct, 2000

                                Muons in TMB
                                ------------

Minimum requirements for a Muon candidate: 

(1) GTrack((pT>1.5 GeV) + 1 of (Cal, A, BC) 
    where A and BC denote at least 1 hit (wire or scint) inside and 
    outside toroid, respectively
(2) BC segment + vertex + Cal 
(3) A  segment + vertex + Cal(tight) + gap in central tracking

Note: we assume that the TMB maker is run together with an event analysis,
to determine e.g. vertex pointed to by most high pT objects, etc.


For each muon candidate:

bits   what                     comment

16*20                         ! Global track parameters+error matrix
16     qpTlocal               ! charge*pT from the muon system (MuoTrack)
16     BCbend                 ! bend coor. at the toroid midplane from BC
16     BCbendslope            ! slope in bend view from BC
 8     BCnonbend              ! nonbend coor. at the toroid midplane from BC
 8     BCnonbendslope         ! slope in nonbend view from BC
                             
16     Abend                  ! bend coor. at the toroid midplane from A
16     Abendslope             ! slope in bend view from A
 8     Anonbend               ! nonbend coor. at the toroid midplane from A
 8     Anonbendslope          ! nonbend slope at the toroid midplane from A
                              ! parents 
 8     parent GTrack 
 8     parent vertex 
 8     parent GTrack 2nd best 
 8     parent vertex 2nd best
                              ! Track quality
32     quality                ! points to odd vertex, thin toroid,
                              ! part of J/psi or Z, 
                              ! hits on opposite side...(to be defined) 
                           
40     layers with hits in fit! SMT+CFT | Cal had | A | B/C (wr and sc)
                              !   22    |  5      | 5 |  8  
40     layers with expected  hits   ! as above 
16     #hits inside 3sigma    | A | B | C
                              | 6 | 5 | 5  (truncated to fit this format) 
 8     chi2                   ! global fit
 8     chi2local              ! chi2 for MuoTrack fit or matched segment
32     3 scint times          ! 1 ns bins
 8     "velocity"+flag 
                              ! Isolation (using tracks)
 8     nTracksdR              ! number of tracks at dR<0.5 around muon
 8     pTracksdR              ! total momentum of above
                              ! MTC: Calorimeter energy, isolation, zvertex
 8     ETRACK_HIT             ! Energy in  cells supposed to be hit
                              ! precision=0.1 GeV, truncated at 5 GeV
 8     ETRACK_BEST            ! Energy in  cells along the best track in road
                              ! about the candidate (=ETRACK Run I)
 8     ELAST                  ! energy in last layer (for punchthrough)
 8     E33                    ! Energy in a 3 X 3 tower around the candidate
                              ! precision=0.5 GeV, truncated at 10 GeV
 8     E55                    ! Energy in a 5 X 5 tower
 8     zvertexMTC+error       ! precision=20 cm
                              ! Trigger info 
16     L2                     ! see below
64     L3                     | qpt,eta,phi,times,velocity,cal confirm
                   ! see http://www-d0.fnal.gov/~balm/muon/L3MuonThumbnail.htm

128 bytes/object, ~300 bytes/event

Note on L1:
Reserve 32 bits per event  filled with the full list of triger decisions
sent to the Trigger Framework. That will allow calculating trigger efficienies
from the TMB. 

Note on the L2 word (from MSB to LSB):
Qt|Qt|pT|pT|pT|eta|eta|eta|eta|phi|phi|phi|Chg|BC|A|L1|

This information is extracted from the alpha pre-processor output. 
(L2 muon candidate)
The three LSbits  represent what types of objects were matched into 
this candidate;   L1 , A-stub , BC-stub.
Charge: as seen by L2 if there is a match A+BC, as seen by L1 otherwise
Phi     is measured in octants   (0-7)
Eta     range (-2,+2)  in units of  0.25  (0-15)
pT      is measured in units of 2 GeV,  truncated at 14  
        as seen by L2 if there is a match A+BC,
             as seen by L1 (threshold) otherwise
Qt  two bits for timing quality;    0 - early      (as assigned by L2)
                                    1 - prompt
                                    2 - slow
                                    3 - late
Instead of two bits for times, which can be extracted from the offline 
fields, these two bits can be used as track quality for the A-stubs 
(loose, med, tight) or BC-stubs (ibid)
 as seen by L1 otherwise