Skip to Content.
Sympa Menu

star-tpc-l - [[Star-tpc-l] ] nHitsMax Issue

star-tpc-l AT lists.bnl.gov

Subject: Star-tpc-l mailing list

List archive

Chronological Thread  
  • From: Zachary Sweger <zwsweger AT ucdavis.edu>
  • To: Star-tpc-l AT lists.bnl.gov
  • Cc: "Van Buren, Gene" <gene AT bnl.gov>, Yuri Fisyak <fisyak AT bnl.gov>, Mathias Labonte <mlabonte AT ucdavis.edu>
  • Subject: [[Star-tpc-l] ] nHitsMax Issue
  • Date: Thu, 18 Jul 2024 23:32:33 -0700

Hi TPC Experts, 

As we discussed this morning, the primary (DCA<3cm) track multiplicity in the test production of 3.2 GeV is lower than in P24ia. Most analyzers require that each track have nHitsFit/nHitsMax>=0.51. After our discussion this morning, I plotted nHitsFit versus nHitsMax (labeled nPossible) and I noticed that many tracks (DCA<3cm) in the test production have very large values of nHitsMax:
Screenshot 2024-07-18 at 11.18.28 PM.png

The red line shows the nHitsFit/nHitsMax=0.51 cut. Another strange thing in the right plot is the lack of tracks with nHitsFit<15. How can so many tracks have nHitsMax values greater than 72? I also tested for tracks with |eta|>2 for which we expect nHitsMax<~40 and saw many tracks still with surprisingly large nHitsMax values:
Screenshot 2024-07-18 at 11.15.08 PM.png
Were there any changes to how nHitsMax is calculated in the test production? I'm accessing this variable from the picoDsts via 
mPicoTrack->nHitsMax();

Thanks!
Zach



Archive powered by MHonArc 2.6.24.

Top of Page