sphenix-tracking-l AT lists.bnl.gov
Subject: sPHENIX tracking discussion
List archive
Re: [Sphenix-tracking-l] Cluster resolution for Hijing embedded tracks
- From: John Haggerty <haggerty AT bnl.gov>
- To: "sphenix-tracking-l AT lists.bnl.gov" <sphenix-tracking-l AT lists.bnl.gov>
- Cc: sphenix-tpc-l AT lists.bnl.gov
- Subject: Re: [Sphenix-tracking-l] Cluster resolution for Hijing embedded tracks
- Date: Fri, 26 May 2017 13:25:35 -0400
Tony and all those hard-working tracking developers,
I couldn't call in today but a couple of questions.
Does it bother anyone else how linear resolution in pT looks? You can usually see the multiple scattering term flattening the resolution at low pT, but this looks absolutely linear (and fits to 0.47% + 0.12%*pT). Maybe those thin inner layers reduce the effects of multiple scattering somehow?
Also, could I ask someone to verify the consistency of the electronic channel count between the CDR, the BOE for the TPC electronics, and the simulation? I think we all agree on 40 samples in radius, but it's easy to get tripped up on that kind of thing when someone asks questions. The numerology is scattered around a bit, too, we may want to fix that (but maybe not before the Document Review).
And I'd say it's way better than "Not so bad," Tony.
On 5/26/17 12:53 PM, Frawley, Anthony wrote:
Hi All,
Following up on Christof's request at the tracking meeting this morning, I extracted the cluster resolutions for clusters matched to tracks embedded in Hijing events. Here are the RMS numbers for reconstructed cluster position minus truth cluster position:
Clusters matched to Hijing embedded pion tracks:
r-phi resolution: MAPS = 4.5 microns INTT = 28.3 microns TPC = 128 microns
Z resolution: MAPS = 4.7 microns INTT = 4745 microns TPC = 151 microns
Clusters matched to standalone 100 pion event tracks:
r-phi resolution: MAPS = 4.5 microns INTT = 27.4 microns TPC = 126 microns
Z resolution: MAPS = 4.8 microns INTT = 4800 microns TPC = 159 microns
Note that it is important that these are clusters matched to tracks. That means that the tracker has already rejected clusters it does not like.
Bottom line: Not much change for clusters associated with Hijing embedded tracks.
Cheers
Tony
_______________________________________________
sPHENIX-tracking-l mailing list
sPHENIX-tracking-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/sphenix-tracking-l
--
John Haggerty
email: haggerty AT bnl.gov
cell: 631 741 3358
-
[Sphenix-tracking-l] Cluster resolution for Hijing embedded tracks,
Frawley, Anthony, 05/26/2017
- Re: [Sphenix-tracking-l] Cluster resolution for Hijing embedded tracks, John Haggerty, 05/26/2017
-
Re: [Sphenix-tracking-l] Cluster resolution for Hijing embedded tracks,
Xin Dong, 05/26/2017
- Re: [Sphenix-tracking-l] Cluster resolution for Hijing embedded tracks, Frawley, Anthony, 05/26/2017
- Re: [Sphenix-tracking-l] Cluster resolution for Hijing embedded tracks, Christof Roland, 05/27/2017
Archive powered by MHonArc 2.6.24.