bin: p=3-6, pt=0.0-0.2
*******************************************************************************

# in general
------------

- mostly tracks that cross VT1 and the end corner, miss VT2 or have only few points there 
( -> very often a/p=0%) and cross MTPCL/R mostly in the left/right corner; also VT1 only 
 tracks - if py is big enough to miss VT2 and MTPC; npoints ca. 11-125
--> As already sometimes reported: In case we want to cut on the ratio of points/potential points 
 I would suggest to ask for a minimum of potential points (e.g.20), otherwise we would remove 
 good tracks that just cross a corner of VT2/MTPC with only a few potential points and often 
 no found points.

- no 'wrongside' tracks entered the 'wrong' VT because of the low pt

- for split tracks the merging between VT1 and MTPC failed
  or there were only a few points in VT1

- lost points are in the MTPC on the upper or lower border (end of the track), or in the corner 
   of VT2 - except for track 66, positives
  sometimes a few lost points are somewhere in the middle of a MTPC track (these tracks are not
   reported as 'lost points tracks'
  note: for track 80, positives and 14, negatives there are 0 potential points, but in reality 
   there are some found!

*******************************************************************************

# positives (99 tracks)
-----------------------

iflag 3     : 22(ok),23,44                               : 3% of all tracks
iflag 4     : 24,25,47,49(ok),75(ok?),77(ok?),87,97      : 8.1% 
split       : 2,45,50(?),70                              : 4%
lost points : 3,5,7,9,11,66,70,78,80                     : 9.1%
decay happened? (but still good track!) : 6,16,26,37,48,50(?)
  \--> have only points in VT1 but none in MTPC even if they should
MTPC only   : 25(iflag 4),73(iflag 0)

- sometimes there are two numbers attached to the blue track?! (see 19,21,71,76)
  ... or I don't see where the second number belongs to...

- comments to iflag 3 tracks:
  track 22 looks ok, b=(1.39 1.49)
  track 23 looks like split muon, b=(10.74 19.09)
  track 44 has big bx, but there is some merging of tracks in VT1! (two tracks too close?)
 
- comments to iflag 4 tracks:
  track 24 looks like split muon, b=(5.88 18.44)
  track 25 maybe a decay product since it has only points in MTPCL,
            but can be fitted to the vertex
  track 47 looks like split muon, b=(-55.89 -29.09)
  track 49 looks ok, b=(0.61 1.01)
  track 75 not so bad, but split and relativly big by, b=(-0.36 -6.30)
  track 77 not so bad, by relativly big: b=(0.70 -5.02)
  track 87 looks like muon in VT2, b=(-130.54 -9.27)
  track 97 looks like split muon, b=(-24.42 18.87)

- track 36 looks strange! maybe there are two tracks too close...
  look at: 
  call "plot" 'ppbc/pos_p=3-6_pt=0.0-0.2' '-500' '-200' '-20' '70' 36 0

*******************************************************************************

# negatives (99 tracks)
-----------------------

iflag 3     : 7(ok)                                      : 1%
iflag 4     : 8(ok?),21,26,46,48,49,65(ok?),97(ok?)      : 8.1%
split       : 51,57,73                                   : 3%
lost points : 7,14(?),20,27,62,76,85,88,89,98            : 10.1%
decay happened? (but still good track!) : 51,67,87,92
  \--> have only points in VT1/VT2 but none in MTPC even if they should
MTPC only   : 97(iflag 4)

- comments to iflag 3 tracks:
  track 7: looks ok!, b=(1.26 1.26)

- comments to iflag 4 tracks:
  track 8: eventually ok, by relativly big: b=(0.63 -3.81)
  track 21: muon b=(38.28 -26.51)
  track 26: muon b=(-13.10 -29.98)
  track 46: muon b=(54.34 -10.84)
  track 48: split muon b=(71.95 16.26) 
  track 49: split muon b=(72.56 15.48)
  track 65: eventually ok, relativly big bx: b=(-3.51 -0.88) 
  track 97: MTPC only but fitted to the vertex, crosses only the corners of the VTPCs 
             (but no lost points there), b=(0.03 0.12)