1. With larger statistics, explore nature of tracks that 1)Are found by Xkal but missed by TRTSeeded 2)Are found by TRTSeeded but missed by Xkal Here are some statististics… In 1000 multimuon events, there are 7415 tracks that, by my criteria, should be findable by TRTSeed tracking. These are evenly spread in pt from 2 to 50 GeV, and in eta from –2.0 to 2.0. Of these, Xkal finds 7375 (99.5% efficient) TRTSeeded finds 6753 (91% efficient)

2. There are 652 tracks found by Xkal that were missed by TRTSeeded tracking. Here are the pt and eta distributions of those tracks.

4. There are 30 tracks that are found by TRTSeeded tracking that were missed by Xkal. These tended to come in clumps for events in which no tracks were found by Xkal. This surprises me and I don’t understand it, but it sounds a little buggy. (11/2/07: I have tracked this to events whose collision points are at large |z|; there must be a cut in Xkal) Here are the pt and eta distributions of these tracks.

7. Here’s the overall curvature pull distribution for all TRTSeeded tracks, for all eta and pt. I should break this up into pt and eta bins eventually.

8. Here’s the curvature pull distribution for TRTSeeded tracks, separately for low ( 1,2) abs(  ). There’s not much difference between low and high abs(  ) – there’s a small negative bias for high abs(  ), but it’s not too pronounced.

9. Here’s the dip angle (cot(  )) pull distribution for TRTSeeded tracks, separately for low ( 1,2) abs(  ). There’s a large bias in the dip angle pull for smaller abs(  ). Also, the pull RMSs are smaller than for the other parameters, and smaller for lower abs(  ). The difference may just be tails (I haven’t tried a gaussian fit)

10. Here’s the z0 pull distribution for TRTSeeded tracks, separately for low ( 1,2) abs(  ). There is a small bias for high abs(  ), but a significant bias for small abs(  ).

11. So, there is a tendency for TRT tracks to be lost for eta = 0 and eta > 1, but you’ll need to judge if this is what you expected or not. The pulls are also a bit broad, but not too bad. I need to look into events for which Xkal reconstructs no tracks. This represents about 1/10 of the statistics available within Castor.