class HTofDigitizer: public HReconstructor

_HADES_CLASS_DESCRIPTION


  HTofDigitizer digitizes data, puts output values into
  raw data category. The input data are read from the HGeantTof
  category. After calculating TOF of and Charge etc the output
  is stored in the HTofRawSim category.



HGeantTof

|

HTofUnpacker     |         |  HTofDigitizer
(embedding mode)   |      -- |
|                      |     /   ------------------
----------------------     /             |
|              /       ----------------
-------------      /       |  HTofRawSimTmp |
| HTofRawSim  |----         | non persistent | (embedding mode,
-------------               ----------------   sim data)
sim (sim mode)      \              /
or real (embedding)  \            /

HTofHitFSim

       |
  ----------------
  | HTofHitSimTmp  | (embedding mode
   | non persistent |  sim data )
     ----------------



| HTofHitSim  | sim (sim mode) or
-------------  sim and real data
(embedding)



  In the case of TRACK EMBEDDING of simulated tracks into
  experimental data the real data are written by the HTofUnpacker into
  HTofRawSim category. In embedding mode the digitizer will write his
  output to HTofRawSimTmp to merge real and sim data on hit level
  (keep calibrations constistent).
  The embedding mode is recognized automatically by analyzing the
  gHades->getEmbeddingMode() flag.
            Mode ==0 means no embedding
                 ==1 realistic embedding (first real or sim hit makes the game)
                 ==2 keep GEANT tracks   (as 1, but GEANT track numbers will always
                     win against real data. besides the tracknumber the output will
                     be the same as in 1)

 In HTofRawSim the track number which created the left/right hit will be
 stored. For real data the number will be equal to gHades->getEmbeddingRealTrackId().
 For the suppression of secondaries produced in the TOF itself there are
 several configuration possibilities:
 They can be switched via setStoreFirstTrack(Int_t flag):
     flag ==  0 realistic (secondaries included)
              1 primary particle is stored
              2 (default) the first track number entering the tof in SAME SECTOR is stored
              3 as 2 but condition on SAME SECTOR && MOD
              4 as 2 but SAME SECTOR && MOD && ROD

 To make the influence of the above selections easily visible
 in the output HTofRawSim a debug mode can be switched with
 void   setDebug(Bool_t flag). In this case the track numbers
 affected by the criteria 1-4 will have negative track numbers
 (multiples of -200). The multiplication factor gives the number
 of steps from the start point to the stored track (chain of
 secondaries). In case 1 it is always -200 if a particle has not
 been a primary one. With void setOutputFile(TString outname)
 an internal Ntuple can be written out with HGeantTof infos
 of the original hit and the changed one.

 For comparison of the new digitizer (after implemantation of
 embedding) and old digitizer (stored 2 fastest tracks instead
 of left/right track) the old execute function can be
 run by using void   setUseOld(Bool_t flag).

 The pointer to the TofDigitizer can be retrieved via
 static HTofDigitizer* getTofDigtizer(). This function
 returns NULL if the Digitizer has not been created yet!