1 / 9

Testing the T-tracker Straw Clustering Code and Stereo Hit Finding

Testing the T-tracker Straw Clustering Code and Stereo Hit Finding. Clustering Code Recently implemented by Hans Wenzel ( MakeStrawCluster_pluggin.cc ) StrawClusters are now a MU2E class Stereo Hits are NOT a MU2E class. Code currently in development (see ReadStrawCluster_pluggin.cc ) .

amalie
Download Presentation

Testing the T-tracker Straw Clustering Code and Stereo Hit Finding

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. Testing the T-tracker Straw Clustering Code and Stereo Hit Finding Clustering Code Recently implemented by Hans Wenzel (MakeStrawCluster_pluggin.cc) StrawClusters are now a MU2E class Stereo Hits are NOT a MU2E class. Code currently in development (see ReadStrawCluster_pluggin.cc) . Why is this important ? Our approach: Stereo Hits are starting seeds to send to a helical trajectory fitter. We need to know the efficiency for finding stereo hits, among other things. Stereo Hits are formed by clusters (more later). In the future, we will add (correlated or random) noise straw hits to access the rate of false stereo hits. Hans Wenzel, Hogan Nguyen, Jan 19th, 2011

  2. Straw Clustering Code Implemented by Hans Wenzel. Clustering finds clumps of neighboring straws (above threshold) within a Panel

  3. Signal Electrons Generated Cos (Polar Angle) = 0.5 NO NOISE HITS Number of Straws (above threshold) per Cluster The number of isolated straw hits (n=1) = 25%

  4. 3 mm distance between wires For normal trajectories, rate of singlets = 1 mm/ 3 mm = 33% We find 25% rate of singlets (independent of hit threshold). Trajectory generated is 30 degreesfrom normal. Higher efficiency probably due to non-normal track angles. 0.5 mm 0.5 mm

  5. Later should generalize Stereo Hit finding to within ONE STATION (= 2 devices) Currently, finding Stereo Hits ONLY WITHIN ONE Device Device Station = 2 devices back-to-back

  6. Number of Clusters Found PerDevice (0-35) at least 2 are required to form a “Stereo Hit” Rate is too low

  7. Number of Stereo Hits Found PerDevice(0-35) Rate is too low

  8. Number of STEREO Hits Found Per Event at least 3 needed to fit to a circle (48% efficiency)

  9. Clustering and Stereo Hit finding seems to work • This strategy yields too low efficiency for finding Stereo Hits. But it • is a good start. • Stereo hit finding should extend to a station (rather than a device) • Can access later if stereo hit finding should include three-cluster • intersections (currently only 2 are used)

More Related