class HPidGeantTrackSet: public TObject

 Get iIdx-th track from list of correlated tracks that was seen in RICH

 Get iIdx-th track from list of correlated tracks that was seen in RICH-IPU

 Get iIdx-th track from list of correlated tracks that was seen in the inner MDC

 Get iIdx-th track from list of correlated tracks that was seen in the outer MDC

 Get iIdx-th track from list of correlated tracks that was seen in TOF

 Get iIdx-th track from list of correlated tracks that was seen in Shower

 Get iIdx-th track from list of correlated tracks that was seen in META

 Return HGeantKine object corresponding to iTrack from pCat.
 If the pCat is not set (NULL) catGeantKine category from gHades is used.

1. All particles which where seen in more than one detector are arranged BEFORE any particle that was seen in
   only one single subsystem. This is required because lonely hits in META have a HIGH bit (64) and would therefore
   be ranked higher than a combination of the three inner detectors. Anyway we mostly care for CORRELATIONS
   between detectors, so we bring the relevant particle indices to the front of the array.

We loop over all contributing particles

 Each track Id found in any of the hits is added once (and only once)
 to the list of correlated tracks. We store the degree of correlation right
 from the beginning in the datamembers correlatedTrackIds and correlationFlags.
 Also the geant PID, parent and process ID momentum, medium and system are
 stored in the corresponding arrays at the position corresponing to the position
 of the added particle. The common tracks are implicitly ranked by their degree of
 commonness using the following numerical code mapped to user-friendly names:

 kTrackNotSet         = 0x00,  // This object does not contain valid data
 kSeenInRICHIPU       = 0x01,  // RICH IPU has seen this trackid

 kSeenInOuterMDC      = 0x02,  // Outer Mdc has seen this trackid
 kSeenInRICH          = 0x04,  // RICH has seen this trackid
 kSeenInInnerMDC      = 0x08,  // Inner Mdc has seen this trackid

 kSeenInTOF           = 0x10,  // TOF has seen this trackid
 kSeenInShower        = 0x20,  // Shower has seen this trackid
 kSeenInMETA          = 0x40,  // One of the Meta dets has seen this trackid

 Thereby META detectors are ranked highest because there is no way to perform
 particle identification without a hit in META. The second-most important
 piece of information is the inner MDC segment because together with META data
 it allows momentum computation with KICKPLANE
 The third highest numerical code is given to the RICH ring because together with
 KICKTRACKS one can do lepton analysis if a ring is present.
 Outer MDC segments are given the lowest number because they are not essential
 for candidate searching. They only allow to apply high-resolution tracking.

 Build TLorentzVector from the momentum and the particle mass from the track at position iPos in the array

 Print all the members

 find the first track ID entering the TOF
 Used to suppress the secondaries created in the
 TOF itself.
        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

return the weight at counter-position iIdx in the array of track-weights
which contributed to the ring

Float_t     getMetaWeight(UInt_t iIdx);

Get number of tracks contributing to the detector hits

What was the strongest correlation in this set of hits? (Which is the largest set of detectors that saw the same particle)

Get information from the geant-info arrays by index