Skip to Content.
Sympa Menu

sphenix-tracking-l - Re: [Sphenix-tracking-l] Momentum resolution in TPOT

sphenix-tracking-l AT lists.bnl.gov

Subject: sPHENIX tracking discussion

List archive

Chronological Thread  
  • From: Anthony Frawley <afrawley AT fsu.edu>
  • To: Ming Liu <ming AT bnl.gov>, "sphenix-tracking-l AT lists.bnl.gov" <sphenix-tracking-l AT lists.bnl.gov>, "Pereira Da Costa, Hugo Denis Antonio" <hugo.pereira-da-costa AT lanl.gov>
  • Subject: Re: [Sphenix-tracking-l] Momentum resolution in TPOT
  • Date: Sat, 8 Oct 2022 01:43:34 +0000

Hi Ming,

I would say that connecting silicon track stubs to TPOT without using TPC clusters is flat out impossible in high occupancy.

Tony


From: sPHENIX-tracking-l <sphenix-tracking-l-bounces AT lists.bnl.gov> on behalf of Pereira Da Costa, Hugo Denis Antonio via sPHENIX-tracking-l <sphenix-tracking-l AT lists.bnl.gov>
Sent: Friday, October 7, 2022 6:03 PM
To: Ming Liu <ming AT bnl.gov>; sphenix-tracking-l AT lists.bnl.gov <sphenix-tracking-l AT lists.bnl.gov>
Subject: Re: [Sphenix-tracking-l] Momentum resolution in TPOT
 

Hi Ming, 


Track matching between TPOT and INTT/MVTX is indeed a serious issue if you don't have any help from the TPC to bridge the gap.


Also, I should stress again that the TPOT acceptance is very very small (~5% in azimuth). I am not sure what you can do  with tracks going through MVTX+INTT+TPOT, beyond helping to calibrate the TPC. 

So this study is really for bookkeeping only: the question was asked during the general meeting about what would be the momentum resolution with only MVTX/INTT and TPOT in the track fit, and here it is: significantly worse than with the TPC, as expected, but not zero either, just because of the level arm. 


Hugo



From: Ming Liu <ming AT bnl.gov>
Sent: Friday, October 7, 2022 3:45 PM
To: Pereira Da Costa, Hugo Denis Antonio; sphenix-tracking-l AT lists.bnl.gov
Subject: [EXTERNAL] Re: [Sphenix-tracking-l] Momentum resolution in TPOT
 

HI Hugo,

Very interesting results!

I guess in the AuAu collisions with high multiplicity, the track finding/connecting hits  could be of great challenge as TPOT is far away from INTT? Or this is not an issue?

 

Cheers,

Ming

 

 

-----

signature_61897647

 

Dr. Ming Xiong Liu

P-3, MS H846

Physics Division

 

Office: 505.667.7125

Mobile: 505.412.7396

Los Alamos National Laboratory

 

 

From: sPHENIX-tracking-l <sphenix-tracking-l-bounces AT lists.bnl.gov> on behalf of "Pereira Da Costa, Hugo Denis Antonio via sPHENIX-tracking-l" <sphenix-tracking-l AT lists.bnl.gov>
Reply-To: Hugo Pereira Da Costa <hugo.pereira-da-costa AT lanl.gov>
Date: Friday, October 7, 2022 at 2:55 PM
To: "sphenix-tracking-l AT lists.bnl.gov" <sphenix-tracking-l AT lists.bnl.gov>
Subject: [Sphenix-tracking-l] Momentum resolution in TPOT

 

Hi, 

 

following some discussion at the last general meeting and the last software meeting I had a look at the momentum resolution you get when fitting tracks with MVTX, INTT and TPOT only, in TPOT acceptance (which is ~ 5% of the total acceptance in phi) and ignoring the TPC clusters for the time beeing.

The results are in the slides attached first with the current (over optimistic) TPOT spacial resolution, second with more realistic values.

This assumes that the detectors are perfectly aligned, and that track matching between INTT and MVTX to TPOT works (right now relying essentially on the TPC).

 

Note: for some reason my current simulations give a slightly worse momentum resolution that what we have in the have in e.g. the QA, when using MVTX, INTT and TPC, but that does not change the conclusions dramatically.

 

Comments welcome

 

Hugo

 

/_______________________________________________ sPHENIX-tracking-l mailing list sPHENIX-tracking-l AT lists.bnl.gov https://lists.bnl.gov/mailman/listinfo/sphenix-tracking-l




Archive powered by MHonArc 2.6.24.

Top of Page