1 / 21

CC update – m momentum resolution

CC update – m momentum resolution. D. A. Petyt April 2004. Software news: Converted code to read Sue’s ntuples. Allows use of Chris’s analysis framework (including event display) Using ntuple files generated by Chris (Feb ’04) This talk:

kyran
Download Presentation

CC update – m momentum resolution

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CC update – m momentum resolution D. A. Petyt April 2004 • Software news: • Converted code to read Sue’s ntuples. Allows use of Chris’s analysis framework (including event display) • Using ntuple files generated by Chris (Feb ’04) • This talk: • Compare PID results using new ntuples to that presented at previous phone meeting • Look at SR muon momentum resolution

  2. Reco. efficiency – new ntuple 0<y<0.25 0.25<y<0.5 0.5<y<0.75 0.75<y<1.0 CC NC Reconstructed event must contain at least 1 track

  3. Reco. effic. – old ntuple Track finding efficiency much higher for NC in old file. Why?

  4. Recoselection effic - new

  5. Recoselection effic - old

  6. PID performance NEW OLD • These curves combine both reconstruction and selection efficiencies, although the effect of the trigger is not accounted for • NEW file seems somewhat better at higher En

  7. SR muon momentum resolution Contained events - range Truth Reconstructed Truth (10% smearing) Resolution function shows small (2%) negative bias and long +/- tails. Momentum resolution ~7%.

  8. reco truth Track hits Tracking failure in v-z view

  9. Select clean tracks: low y events only Apply cuts: mc_y<0.2; trk_plane_n>20; trk_end radius>40cm Truth Reconstructed Tails are reduced (high-side tail eliminated) and resolution improved, but bias is still present

  10. Demux failure in v-z view (low-side tail)

  11. Tracking stops prematurely (-ve bias)

  12. Tracking stops prematurely (-ve bias)

  13. Contained events – q/p Truth Q/P Range Right-side plot: q/p momentum resolution. High-side tail (muon momentum overestimated) is more prominent

  14. q/p thrown off by multiple scattering?

  15. Disappearing muon?

  16. Disappearing muon – x,y,z projections

  17. Range/momentum comparison Momentum from range biased low wrt. momentum from curvature

  18. Resolution – range vs q/p Multiple scattering? In general, range measurement preferred over q/p for contained tracks.

  19. Partially-contained events m- Truth Reconstructed m+ m+ m-

  20. All events Truth Reconstructed Use range measurement for contained tracks, q/p for partially-contained.

  21. Summary & conclusions • Looked at SR muon momentum resolution for clean CEV/PCE tracks: • Obtained resolutions of ~6% for contained tracks, ~12% for partially-contained • Range measurement is biased low (~2%). I think this is probably due to the track finder stopping prematurely at the end of tracks (either because of excessive scattering or high p.h. hits) • Low-side tail evident for CEV/PCE – demux and tracking errors contribute to this. • Would be useful if someone could look at some of the rogue events in detail and see where/how the reconstruction is failing • Observed large differences in reconstruction efficiencies (especially for NC) between two reconstruction passes of the same MC file • My hunch is that this is caused by different JobModule configurations – needs looking into.

More Related