In 10000 bb in/un events we found 44 KKpi G decays after cuts of a 200MeV mother mass window, 900MeV mother PT and 250MeV daughter PT, of which 3 were R & R and should appear in the tuple. In fact 2 appear in the tuple, both assigned background category 0. 6731 events were put into the tuple, which contained 515654 entries. The run took 33 minutes.

The next run took 41 minutes, with a correction to the counting sequence. 4 decays were found, of which 3 were R & R, and all of these were accepted by CombineParticles and DecayTreeTuple.

The bb unstripped sample contained 282 R & R decays of 2398 total in 417108 events.

Ran over in 8 jobs: R & R ; MC decays; Events.

33;319; 56666 | 21 ;180; 32302 | 44; 446; 74545 | 44; 266; 45800 | 42 ;350 ; 63147 | 39; 264 54179 | 41; 320; 53664 | 28 ; 223; 36805

The same PT cuts were applied at options file level. Running over the whole dataset (~6 hours) yielded 217 signal events in the tuple of the 282 originally found, which will probably be reduced to between 60 and 80 by the cuts. There were a large number of background events, necessitating more preliminary cuts before cut optimisation can be carried out.

Ran over phys-v2-lumi2 minimum bias sample. Book-keeping claims 980028 events available. Found 8 reconstructible & reconstructed decays AFTER processing, maybe 10 before. Actually ran over 99737+99759+99766+99721+99751= 498734 events.

• The histogram below shows the results from a bb unstripped sample with optimised cuts applied. The trigger is not included.

• BBuNoMassCut.jpg:
  

* The histogram below shows the results from a bb unstripped sample with optimised cuts applied. The trigger is included. The bins are wider to reduce the influence of statistical fluctuations.

• triggerwithwiderbins.gif:
  
• This is a Dalitz plot for the decay with data taken from a signal sample.
• dalitz1.gif: