dubious spacepoint finding
The space point finding seems to be generating incorrect doublet space points in some cases.
I have attached an example plot, the blue dots are points on a track and the red dots are not on a track. If the dot is filled it is a triplet and if it is not filled then it is a doublet.
The formatting of the details is as follows:
+ C: plane channel is_used npe
SP: 27.077350, -147.853421
+ C: 0 201.0 True 2.46755852843
+ C: 2 87.0 True 9.06126914661
+ C: 1 110.0 False 9.64406779661
As you can see the combination was done incorrectly and the one real hit was combined with a noise hit, followed by another real hit being unassigned to a space point.
Updated by Overton, Edward almost 7 years ago
I wrote a new doublet finding algorithm for MAUS, which sorts by npe and improves things.
Using the bin/user/scifi/efficiency.py code:
File #_Recon_Events TkUS_5pt TkUS_3-5_pt TkDS_5pt TkDS_3-5pt
07691_new.root 70676 0.98274 1.00000 0.91512 0.99751
07691_orig.root 70676 0.95301 1.00000 0.90299 0.99733
As you can see the upstream 5pt efficiency is increased by 3% and the downstream is 1.3%.