sphenix-tracking-l AT lists.bnl.gov
Subject: sPHENIX tracking discussion
List archive
Re: [Sphenix-tracking-l] Problem with distortion+correction in matching code
- From: "Pereira Da Costa, Hugo Denis Antonio" <hugo.pereira-da-costa AT lanl.gov>
- To: "Pereira Da Costa, Hugo Denis Antonio" <hugo.pereira-da-costa AT lanl.gov>, Anthony Frawley <afrawley AT fsu.edu>, "sphenix-tracking-l AT lists.bnl.gov" <sphenix-tracking-l AT lists.bnl.gov>, Joe Osborn <osbornjd91 AT gmail.com>
- Subject: Re: [Sphenix-tracking-l] Problem with distortion+correction in matching code
- Date: Thu, 14 Mar 2024 20:24:00 +0000
Quick follow-up: updating get_phi inside the SiliconTpc matching only marginally improve things. But in the meanwhile I figured that the seed parameters published by KFProp (e.g. m_slope for instance, used to calculate eta) also do not account for distortion corrections (while KFProp does, internally). This is because of the way the seed parameters are calculated inside PHSimpleKFProp::publishSeeds, (line 1200 or so), using _cluster_map, rather than the distortion corrected global positions …
I’ll look into this in more details
Hugo
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
Yes, I’ll check with local implementation that this fixes the issue I see. I agree that things get complicated in the pp case.
From: Anthony Frawley <afrawley AT fsu.edu>
Hi Hugo,
Good catch! I missed that completely. The solution is a bit complicated though. The z positions, and thus the distortion corrections, are unknown until we have the bunch crossing - which is determined by the track matching. So your solution would work only for triggered event reconstruction, where we can assume that the bunch crossing is zero.
For pp running, the current track seed model does not work well. I think the best solution will be to store the phi and eta of the tracklet in the track seed, rather than calculate it on the fly. That way, the preliminary distortion correction module, which runs before the track matching, can recalculate phi and eta with preliminary distortion corrections included. Then the track matching process does not need to know about clusters at all, it relies only on the best available track seed parameters.
I have something else going on this afternoon, I will look at it tonight.
In the meantime, you could apply your fix locally, and see how it works for the triggered case.
Thanks Tony
From: Pereira Da Costa, Hugo Denis Antonio <hugo.pereira-da-costa AT lanl.gov>
Hi all, in particular Tony, Joe |
-
[Sphenix-tracking-l] Problem with distortion+correction in matching code,
Pereira Da Costa, Hugo Denis Antonio, 03/14/2024
-
Re: [Sphenix-tracking-l] Problem with distortion+correction in matching code,
Anthony Frawley, 03/14/2024
-
Re: [Sphenix-tracking-l] Problem with distortion+correction in matching code,
Pereira Da Costa, Hugo Denis Antonio, 03/14/2024
-
Re: [Sphenix-tracking-l] Problem with distortion+correction in matching code,
Pereira Da Costa, Hugo Denis Antonio, 03/14/2024
-
Re: [Sphenix-tracking-l] Problem with distortion+correction in matching code,
Pereira Da Costa, Hugo Denis Antonio, 03/14/2024
- Re: [Sphenix-tracking-l] Problem with distortion+correction in matching code, Anthony Frawley, 03/14/2024
-
Re: [Sphenix-tracking-l] Problem with distortion+correction in matching code,
Pereira Da Costa, Hugo Denis Antonio, 03/14/2024
-
Re: [Sphenix-tracking-l] Problem with distortion+correction in matching code,
Pereira Da Costa, Hugo Denis Antonio, 03/14/2024
-
Re: [Sphenix-tracking-l] Problem with distortion+correction in matching code,
Pereira Da Costa, Hugo Denis Antonio, 03/14/2024
-
Re: [Sphenix-tracking-l] Problem with distortion+correction in matching code,
Anthony Frawley, 03/14/2024
Archive powered by MHonArc 2.6.24.