SLAC PEP-II
BABAR
SLAC<->RAL
Babar logo
HEPIC E,S & H Databases PDG HEP preprints
Organization Detector Computing Physics Documentation
Personnel Glossary Sitemap Search Hypernews
Unwrap page!
Det. Search
Who's who?
Meetings
FAQ
Images
Archive
Systems
Performance
Intern. region
Vertex Tracker
Drift chamber
DIRC
Calorimeter
IFR
LST
Magnet
Electronics
Trigger
Operations
Run Coordination
Contact Experts
Shift Takers Info
Operations Manual
Electronic Logbook
Ops Hypernews
Shift Signup
Check this page for HTML 4.01 Transitional compliance with the
W3C Validator
(More checks...)
Structure of the TimeBuffer with results of MC simulation for the  L1 trigger tests.
 
  1. Introduction
  2. General Structure
  3. Specific TSF, ZPD Objects


1. Introduction
Below the format of the files produced by L1 simulation is given.
All objects are collected in TimeBuffers (see L1SimUtils/L1SimTimeBuffer.hh). The objects could be of different types which are given in Specific TSF, ZPD Objects section.

The file with 100 generic BBbar events could be found at :
    /nfs/bbr-nfs03/detector/trg/olya/MCoutput/BBbar_900100_sep01.zpdtb.txt
and file with 100 generic tau-tau events is :
    /nfs/bbr-nfs03/detector/trg/olya/MCoutput/tau_generic_900400_sep01.zpdtb.txt

The files could  be produced by L1ZpdAnal/L1ZpdIterf or L1SimTest programs.
The files could be read by converter L1SimTools/L1SimConvApp.



2. General Structure

The files have ascii format, therefore could be read by eye.  The file has a header (comment), followed by number of events.
Each events has a several TimeBuffers . Each TimeBuffer has a several sets of objects, each set correspond to one tick of the certain clock. Each set contains objects of the type described in Specific TSF, ZPD Objects. All sets of one TimeBuffer contains same kind of objects.

  • Each line started with '#' is a comment;
  • Each event is identified as
    • Event   <N>
    where <N> is an event number;
  • Each line started with '@' is a description of the following TimeBuffer;
  • Each TimeBuffer is identified as
    • @TimeBuffer-<Name>
      FirstTick <N1>  <N2> size <L1>
    where <Name> is the name of the structure in TimeBuffer (related to the objects in TimeBuffer);
    <N1> is a number of first tick in TimeBuffer and <N2> is a clock type of tick (Expect <N2>=4 for ZPD)
    <L1> is number of sets  which follows the TimeBuffer definition.
    The tick of the set <J> (<J>=0,<L>-1)   is   <N1>+<J>;
  • Each set in TimeBuffer is identified as
    • <Name2>  <L2>
    where <Name2> is name of the objects in the structure (related but not necessarily equal to <Name>),
    <L2> is a number of the objects in the set;
  • There is no obvious end of the TimeBuffer if you read it by eye, except  an empty line, beginning of new TimeBuffer or beginning of new Event.




3. Specific TSF, ZPD Objects
  1.  TSF Hits
  2.  TSF Unstretched Segments
  3.  TSF Stretched Segments
  4.  ZPD Input Segment (L1DczHdwSeg, NL1DZpdInputSeg)
  5.  ZPD Seed Track (L1DczHdwSeedTrk)
  6.  ZPD Fitted Track (L1DczHdwFitTrk)
TSF hits
The structure containing  TSF hits is called  L1DczDctHit
The set is called NDctHit or NL1DTsfHitobjects, depending on the program which created them.
The object format is :
tick  speed  wire Layer
For details see L1DctData/L1DTsfHit.hh  or L1DczTest/L1DczTrigHit.hh

TSF Unstretched segments
The structure containing  unstretched TSF  segments is called L1DczUnstretchedSeg
The set is called NDczSeg or NL1DTsfSimDigi objects, depending on the program which created them.
The object format is :

address  superLayer  superCell  wire  tick  speed
For details see L1DctData/L1DTsfSimDigi.hh  or L1DczTest/L1DczSeg.hh

Note: that  L1DTsfSimDigi returns wire number relative to super cell while L1DczSeg returns unique wire number.
 

TSF Stretched segments
The structure containing  stretched TSF  segments is called L1DczStretchedSeg.
The format is exactly the same as for  TSF Unstretched Segments .

Note:
The speed of this TimeBuffer  must be 8. The TimeBuffer written by L1DczTest has this value wrongly assigned to 4.
The speed of the TimeBuffer written by L1SimTest is correct.

ZPD Input Segment
The structure containing ZPD Input Segments is called L1DczHdwSeg,
The set is called NHdwSegor NL1DZpdInputSeg objects, depending on the program which created them.
The object format is :

mask  superLayer  sector  whichOf3  cell  phi  phiError
For details see L1DctData/L1DZpdInputSeg.hh  or L1ZpdAnal/L1ZpdOrderedHdwSeg.hh

ZPD Seed Track
The structure containing ZPD Seed Tracks is called L1DczSeedTrk,
The set is called NHdwSeedTrkor NL1DZpdSeedTrk objects, depending on the program which created them.
The object format is :

mask  seedType  sector  whichOf3  curvature  tanLambda
-->followed by 10 lines with
        superLayer   hitFlag   phi  phiError
For details see L1DctData/L1DZpdSeedTrk.hh  or L1ZpdAnal/L1ZpdOrderedHdwSeedTrk.hh

ZPD Fitted Track
The structure containing ZPD Seed Tracks is called L1DczFitTrk,
The set is called NHdwFitTrkor NL1DZpdFitTrk objects, depending on the program which created them.
The object format is :

mask  seedType  sector  whichOf3  curvature  tanLambda   z0  z0Err  hitMap
For details see L1DctData/L1DZpdFitTrk.hh  or L1ZpdAnal/L1ZpdOrderedHdwFitTrk.hh
 
 



 Wed Apr 23 14:40:30 PDT 2003 Olga Igonkina