class HMdcVertexFind: public HReconstructor

_HADES_CLASS_DESCRIPTION

 HMdcVertexFind

   Vertex finder using weighted LSM with optional Tukey weights

 To use it in a macro just add

 taskset->add(new HMdcVertexFind("name","title",input_mode,tukey)

 where

 input_mode is one of HMdcVertexFind::kSegments or HMdcVertexFind::kHits.
 In the first case HMdcSeg objecst will be used as input (recomended for
 now) while in the secon HMdcHit objects will be used

 As for 'tukey' it can be kTRUE or kFALSE depending on if Tukey weights
 should be used in the minimization. For low multiplicity environments
 like C+C I would recomend kFALSE; at least until I have found better
 parameters for the Tukey weigths minimization.

  static void setRejectEmbeddedTracks(Bool_t reject = kTRUE){rejectEmbeddedTracks = reject;}
  static void setUseEventSeqNumber   (Bool_t use    = kTRUE){useEventSeqNumber    = use;   }
  static void setSkipNoVertex        (Bool_t skip   = kTRUE){doSkipNoVertex       = skip;  }

 For the track embedding the are several configurations possible using
 the above static member functions.
 MODE:
       1. THIS IS CLEARLY THE PREFERED METHOD IF ON NEEDS TO GET SIMULATED PARTICLES
          AT EXACTLY THE SAME VERTEX AS THE REAL DATA!
          READING vertex from HGeantKine objects (sim done with real vertices)
          In this mode (useEventSeqNumber == kTRUE (default)) the event sequence number
          of the real events which have been used to create the sim tracks with
          PLUTO will be stored in the HGeantKine::userVal of the particles. If the
          current event does not match the one from GEANT the event will be skipped as
          Long_t as the numbers match again.
       2. useEventSeqNumber == kFALSE. In this mode rejectEmbeddedTracks == kTRUE (default)
          segments which keep GEANT track numbers and more than one contributing track number
          will be skipped (minimize the influence of the embedded tracks to the vertex calculation).
          Anyway the vertex will never be exactly the same as the one from the real dsts. Eventually
          everything will go out of sync with the vertex of the sim input (if used real vertex with PLUTO)
          because an additional event will skipped.
          With rejectEmbeddedTracks == kFALSE all segments will be taken into account.
       3. With doSkipNoVertex == KTRUE (default : kFALSE) events without calculated vertex will not be skipped.
          This mode has only influence if MODE 1 is not used, because here the events will be skipped.