sPHENIX tracking discussion

[David Stewart <0ds.johnny AT gmail.com>]

Thanks, Joe. Will do,

On Mon, Nov 28, 2022 at 12:26 PM Osborn, Joseph <josborn1 AT bnl.gov> wrote:

Hi David,

To step 3, I propose to preliminarily add the requirement that the hitsetkey also be identical between truth and reco tracks.

 

I assume you mean that the hitsetkey of the truth and reco cluster are the same. That sounds correct - if the hitsetkeys aren't the same, then they won't have the same transformation in the Acts geometry.

___________________________

Joe Osborn, Ph.D

Physics Department

Brookhaven National Laboratory

josborn1 AT bnl.gov

---

From: sPHENIX-tracking-l <sphenix-tracking-l-bounces AT lists.bnl.gov> on behalf of David Stewart via sPHENIX-tracking-l <sphenix-tracking-l AT lists.bnl.gov>
Sent: Monday, November 28, 2022 11:48 AM
To: sphenix-tracking-l AT lists.bnl.gov <sphenix-tracking-l AT lists.bnl.gov>
Subject: [Sphenix-tracking-l] Question regarding cluster comparisons

 

Hi all,

In the truth to reco track matching code, the algorithm is (in part) as follows:

1. A truth track and a reco track of interest are found to be compared, based on proximity in phi/eta/pT.

2. An array, indexed by layer id, is filled with the cluster keys for both the truth and reco tracks.

3. In each layer, if there is a cluster key in both the reco and truth track, then the clusters are compared based on the {phi,z} and width of {phi,z} value for both the truth and reco track. 

To step 3, I propose to preliminarily add the requirement that the hitsetkey also be identical between truth and reco tracks. Otherwise, the local geometry won't be the same between the two and the comparison of the phi values will be incorrect. True?

thanks--

David Stewart

Postdoctoral Fellow | Department of Physics, Wayne State University

--

David Stewart

Postdoctoral Fellow | Department of Physics, Wayne State University