Hit Flags

              
               Catagorize the clusters with a flag. All flags<4 are
               good. A Flag==2 is a deconvoluted hit. All flags are multiples
               of 2 so the user can check for all the reasons a hit was flag
               a certain way. When hits are catagorized we never judge solely
               on peakADc or integrated charge as this is a bias. See
               CatagorizeCluster() for details on how we clasify clusters. 
               An additional cut is made for noisy anodes or timebuckets 
               if there are more than 4 hits/event on them. 
 
               Finally this code deconvolutes some clusters. At present we are 
               quite conservative in which clusters we deconvolute. There has
               to be a clear valley between peaks in a cluster for hits to be
               deconvoluted. Look at PEAK_TO_VALLEY in isValidPeak() for more 
               details.
 
             Flags:    0 = standard good

                       2 = deconvoluted
                       4 = more than 4 hits on eithe this anodes or time bucket 
                             for this event
                       8 = 1 pixel cluster with ADC<1 (could reuse this for something else)
                      16 = undershoot on wrong side
                      32 = topological cut. Based on num pixels, and charge
                      64 = topological cut based on relative widths in anode and time dir. Gets
                             rid of tracks comming in at very shallow angles. You might want to
                             rethink this one for special physics studies.
                      128 = A hit which was deconvoluted.