sPHENIX tracking discussion

[Anthony Frawley <afrawley AT fsu.edu>]

Hi Joe,

That is puzzling. I don't understand how it could have been this way previously without us noticing it. There are 26 events, of which 6 (20-25%) have a number of clusters in the MVTX that would imply 1000 tracks.  Before the recent optimization of the silicon-tpc track matcher loop, this should have made the matching very slow.

Is it possible to extract the number of truth tracks for these events?

Tony

---

From: sPHENIX-tracking-l <sphenix-tracking-l-bounces AT lists.bnl.gov> on behalf of Osborn, Joe via sPHENIX-tracking-l <sphenix-tracking-l AT lists.bnl.gov>
Sent: Tuesday, June 21, 2022 1:57 PM
To: pinkenburg <pinkenburg AT bnl.gov>; sphenix-tracking <sphenix-tracking-l AT lists.bnl.gov>
Subject: Re: [Sphenix-tracking-l] [EXTERNAL] 20 segments with current G4 (10.07.p03)

 

Hi all,

 

Okay, Chris re-ran some jobs with no pile up. This is because the pile up is thrown randomly, so there is already inherently a level of irreproducibility. The new files have the same HEPMC input and just run the reconstruction before adding pileup (I think, Chris can correct me if I’m wrong).

 

I made a quick spreadsheet of the number of silicon clusters in the MVTX to seed with in each version of geant11 and geant10.07.03:

 

https://docs.google.com/spreadsheets/d/1wgW2ev6TZpLlB52Wx_xMrlpI_RWsxLWFHF_5ORlFcQU/edit?usp=sharing

 

Nothing stands out as too egregious – there are a few events where there are large differences between the geant versions but otherwise they are reasonably comparable.

 

Is there any way to run with the same pile up environment in each version as well? i.e. remove this random element from the simulation?

Joe

 

 

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

 

Joe Osborn, Ph.D.

Associate Research Scientist

Oak Ridge National Laboratory

osbornjd AT ornl.gov

(859)-433-8738

 

 

From: sPHENIX-tracking-l <sphenix-tracking-l-bounces AT lists.bnl.gov> on behalf of pinkenburg via sPHENIX-tracking-l <sphenix-tracking-l AT lists.bnl.gov>
Date: Saturday, June 18, 2022 at 11:01 AM
To: sphenix-tracking <sphenix-tracking-l AT lists.bnl.gov>
Subject: [EXTERNAL] [Sphenix-tracking-l] 20 segments with current G4 (10.07.p03)

Hi folks,

I ran 20 segments using the current new build using G4 10.07.p03. They
use runnumber 40. All files are in lustre and gpfs. The trackseeds are in
/sphenix/sim/sim01/sphnxpro/mdc2/shijing_hepmc/fm_0_20/trackseeds
the clusters are in
/sphenix/sim/sim01/sphnxpro/mdc2/shijing_hepmc/fm_0_20/trkrcluster

you can use the CreateFileList.pl to get a list of those files via:

CreateFileList.pl -type 4 -run 40 DST_TRKR_CLUSTER
or
CreateFileList.pl -type 4 -run 40 DST_TRACKSEEDS

The tracking (job C) right now bombs out with
/home/phnxbld/sPHENIX/gcc-8.3/new/source/coresoftware/offline/packages/trackreco/PHActsTrkFitter.cc:1097:
TpcTrackSeedContainer not on node tree. Bailing

It looks like the node names in pass A have changed.

The old G4 version (11.0.0) can be found under runnumber 4

Chris


--
*************************************************************

Christopher H. Pinkenburg       ;    pinkenburg AT bnl.gov
                                ;    http://www.phenix.bnl.gov/~pinkenbu

Brookhaven National Laboratory  ;    phone: (631) 344-5692
Physics Department Bldg 510 C   ;    fax:   (631) 344-3253
Upton, NY 11973-5000

*************************************************************

_______________________________________________
sPHENIX-tracking-l mailing list
sPHENIX-tracking-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/sphenix-tracking-l