sPHENIX tracking discussion

["Pereira Da Costa, Hugo Denis Antonio" <hugo.pereira-da-costa AT lanl.gov>]

Another one: 
Another one (this time about seeder search windows)
grep 'seeder->SetSearchWindow' `find -iname "*.c"`

./common/Trkr_Reco.C:  seeder->SetSearchWindow(1.5, 0.05);  // (z width, phi 
width)
./common/Trkr_Reco.C:  seeder->SetSearchWindow(1.5, 0.05);  // (z width, phi 
width)
./common/Trkr_Reco.C:  seeder->SetSearchWindow(1.5, 0.05);  // (z width, phi 
width)
./common/Trkr_TruthReco.C:      seeder->SetSearchWindow(1.5, 0.05);  // (z 
width, phi width)
./common/Trkr_TruthReco.C:  seeder->SetSearchWindow(1.5, 0.05);  // (z width, 
phi width)
./TrackingProduction/Fun4All_FullReconstruction.C: 
seeder->SetSearchWindow(2.,0.05); // z-width and phi-width, default in macro 
at 1.5 and 0.05
./TrackingProduction/Fun4All_FieldOnAllTrackersCalos.C: 
seeder->SetSearchWindow(2.,0.05); // z-width and phi-width, default in macro 
at 1.5 and 0.05
./TrackingProduction/Fun4All_TrackSeeding.C: 
seeder->SetSearchWindow(2.,0.05); // z-width and phi-width, default in macro 
at 1.5 and 0.05
./calibrations/tpc/TpcDVCalib/Fun4All_FieldOnAllTrackersCalos.C: 
seeder->SetSearchWindow(2.,0.05); // z-width and phi-width, default in macro 
at 1.5 and 0.05

The macro I am using locally uses 2.0 and 0.05 (I think I got that from Tony 
some time ago), as do 'some' of our macros. But the default macro now use 
1.5, 0.05
There is also a call to SetClusAdd_delta_window(3.0,0.06), found in some 
macros, but not all. 
If I remember right, these were some parameters adjusted by Tony a while ago 
to improve the number of found seed. 
My observation is that this also works for the zero-field runs. 


Hugo

-----Original Message-----
From: sphenix-tracking-l-request AT lists.bnl.gov 
<sphenix-tracking-l-request AT lists.bnl.gov> On Behalf Of "Pereira Da Costa, 
Hugo Denis Antonio"
Sent: Thursday, December 5, 2024 2:59 PM
To: Anthony Frawley via sPHENIX-tracking-l <sphenix-tracking-l AT lists.bnl.gov>
Cc: Hugo Pereira Da Costa <hugo.pereira.da.costa AT gmail.com>
Subject: [EXTERNAL] [[Sphenix-tracking-l] ] Tracking parameters

All,

So unfortunately, using the latest code from Macros, I still see very very 
few tracks mathcing to TPOT in our zero-field data, as soon as I require a 
silicon match. I might still be doing something wrong.

Now: looking at recent commit and discussing with Bade, I realized that our 
macro repository is somewhat of a mess, and makes it difficult to understand 
what we are running or talk to each other.

As an example, I looked into micromegas matching windows. There are 4 
parameters to be set there, controlled by:

     mm_match->set_rphi_search_window_lyr1();
     mm_match->set_rphi_search_window_lyr2();
     mm_match->set_z_search_window_lyr1();
     mm_match->set_z_search_window_lyr2();

Now, a simple grep into vanilla macro gives:

grep set_rphi_search_window_lyr1 `find -iname "*.C"`
./common/Trkr_Reco.C: mm_match->set_rphi_search_window_lyr1(0.2);
./common/Trkr_Reco.C: mm_match->set_rphi_search_window_lyr1(0.2);
./common/Trkr_Reco.C: mm_match->set_rphi_search_window_lyr1(0.4);
./common/Trkr_TruthReco.C: mm_match->set_rphi_search_window_lyr1(0.2);
./common/Trkr_TruthReco.C: mm_match->set_rphi_search_window_lyr1(0.2);
./common/Trkr_TruthReco.C: mm_match->set_rphi_search_window_lyr1(0.4);
./TrackingProduction/Fun4All_FullReconstruction.C: 
mm_match->set_rphi_search_window_lyr1(3.);
./TrackingProduction/Fun4All_ZFAllTrackers.C: 
mm_match->set_rphi_search_window_lyr1(0.4);
./TrackingProduction/Fun4All_FieldOnAllTrackersCalos.C: 
mm_match->set_rphi_search_window_lyr1(0.4);
./TrackingProduction/Fun4All_TrackSeeding.C: 
mm_match->set_rphi_search_window_lyr1(3.);
./calibrations/tpc/TpcDVCalib/Fun4All_FieldOnAllTrackersCalos.C: 
mm_match->set_rphi_search_window_lyr1(0.4);

So three different values, assigned at 11 different places. It is very 
difficult to know which one is used by one.

The ones commited yesterday in Fun4All_ZFAllTrackers are not the correct one.

I will move forward and make all the values consistent and consistent with 
what they should be with real pp data (3cm) and commit.

Another thing which I noticed:

in Tracking_Reco_TrackSeed_ZeroField and elsewhere (from
common/Trkr_Reco.C) there are some parameters assigned to the ca_seeder and 
simplekfprop which depend on the gas mixture in the TPC, 
G4TPC::TPC_GAS_MIXTURE

I don't know how critical those are, but as much as I can tell, this variable 
is assigned to

./common/G4_TrkrVariables.C:  std::string TPC_GAS_MIXTURE = "NeCF4";

and never overwritten.

All in all I think one of the objectives of the workfest could be to make 
sure that our tracking parameters make sense and are consistent everywhere, 
in the repository and among users. Otherwise, it makes it very difficult to 
draw any conclusion about anything.

Opinion ?

Hugo