sPHENIX tracking discussion

[Christof Roland <christof.roland AT cern.ch>]

Hi Joe,

On 30. Mar 2022, at 17:50, Osborn, Joe <osbornjd AT ornl.gov> wrote:

Hi Christof,

Is there any reason to not change the cluster cleaner cut to an ADC cut of 600 right now, based on these plots (rather than the 0.01 rphi error cut now)?

Sure, this was just to make sure we can drop the error storage from the cluster and still have enough info to reject badly defined clusters. 

Looks like adc is all we need, I will set the cluster cleaner to something between 600 and 1000 and we should be good to go.

Alternatively, it might be interesting to see what the effect is on the resolution if you change the cluster cleaner to take any cluster with ADC>600 and just blow the uncertainties up rather than just removing it from the pa ttern recognition completely. 

This is more or less the plan. I will go back to the residual valuation trees and see how to encorporate a adc dependence in the error parametrization. 

Adding the proper weights in the clusters should fix the effect we see. 

Cheers

   Christof

---------------------------

Joe Osborn, Ph.D.

Associate Research Scientist

Oak Ridge National Laboratory

osbornjd AT ornl.gov

(859)-433-8738

---

From: Christof Roland <christof.roland AT cern.ch>
Sent: Wednesday, March 30, 2022 11:23 AM
To: Osborn, Joe <osbornjd AT ornl.gov>
Cc: Tony Frawley <frawley AT fsunuc.physics.fsu.edu>; Hugo Pereira Da Costa via sPHENIX-tracking-l <sphenix-tracking-l AT lists.bnl.gov>
Subject: Re: [EXTERNAL] Tuning of cluster cleaning parameters

 

Ok, 

here are the first results for the update of the cluster cleaner. 

The cut in adc seems to do as well, if not better than a cut in rphi cluster error. 

See plots attached below. 

We may hve to retune the errors for high adc or use a different selection 

of clusters for pattern recognition and track fitting. 

cheers

   Christof 

On 29. Mar 2022, at 17:11, Osborn, Joe <osbornjd AT ornl.gov> wrote:

Hi Christof,

 

I just do

 

ntp_gtrack->Draw(“pt/gpt:gpt>>gr(40,0,40,400,0.5,1.5)”,”quality<10”,”colz”);

gr->FitSlicesY();

TH1 *width = (TH1*)gDirectory->Get(“gr_2”);

 

To get the resolution. If there are a lot of files I just chain them together with hadd, if you want me to do it I can but it’s not anything fancy.

 

Joe

 

---------------------------

 

Joe Osborn, Ph.D.

Associate Research Scientist

Oak Ridge National Laboratory

osbornjd AT ornl.gov

(859)-433-8738

 

 

From: Christof Roland <christof.roland AT cern.ch>
Date: Tuesday, March 29, 2022 at 10:42 AM
To: Christof Roland <christof.roland AT cern.ch>
Cc: Osborn, Joe <osbornjd AT ornl.gov>, Hugo Pereira Da Costa via sPHENIX-tracking-l <sphenix-tracking-l AT lists.bnl.gov>
Subject: [EXTERNAL] Tuning of cluster cleaning parameters

Hi Joe,

to tune the cut on cluster ADC for the tuning of the cluster cleaner I have a fewe more evaluator files
for whih I would like to know the momentum resolution. Is your momentum resolution plotting macro
is easy enough to use would you mind sharing it? If not could you plot the resolutions for the following files:

/phenix/u/bogui/data/MacrosFileSize/macros/detectors/sPHENIX/TracksPu50/
TrackingPara4_1_1*.root
TrackingPara5_1_1*.root
TrackingPara6_1_1*.root
TrackingPara7_1_1*.root

Thanks a lot

   Christof