sphenix-tracking-l AT lists.bnl.gov
Subject: sPHENIX tracking discussion
List archive
Re: [Sphenix-tracking-l] [EXTERNAL] 20 segments with current G4 (10.07.p03)
- From: "Osborn, Joe" <osbornjd AT ornl.gov>
- To: Anthony Frawley <afrawley AT fsu.edu>, 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)
- Date: Tue, 21 Jun 2022 18:40:24 +0000
In each the g11 and g10 case, the silicon-tpc track matcher runs in ~130 ms per event when running over these first 26 events. The silicon seed merger runs in ~340 ms per event in g10, and ~560 ms per event in g11, so there is a nontrivial difference there in terms of the number of silicon seeds produced in g11 vs. g10. It occurred to me that this would be useful information, so I added the number of silicon seeds found in each of the events in the two geant versions to the spreadsheet. There are two interesting observations:
Chris can correct me if I’m wrong, but I don’t see the corresponding truth DSTs for these runs. Are they available somewhere?
---------------------------
Joe Osborn, Ph.D. Associate Research Scientist Oak Ridge National Laboratory osbornjd AT ornl.gov (859)-433-8738
From:
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>
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:
hxxps://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 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> Hi folks, |
-
[Sphenix-tracking-l] 20 segments with current G4 (10.07.p03),
pinkenburg, 06/18/2022
-
Re: [Sphenix-tracking-l] [EXTERNAL] 20 segments with current G4 (10.07.p03),
Osborn, Joe, 06/21/2022
-
Re: [Sphenix-tracking-l] [EXTERNAL] 20 segments with current G4 (10.07.p03),
Anthony Frawley, 06/21/2022
-
Re: [Sphenix-tracking-l] [EXTERNAL] 20 segments with current G4 (10.07.p03),
Osborn, Joe, 06/21/2022
- Re: [Sphenix-tracking-l] [EXTERNAL] 20 segments with current G4 (10.07.p03), pinkenburg, 06/21/2022
-
Re: [Sphenix-tracking-l] [EXTERNAL] 20 segments with current G4 (10.07.p03),
Osborn, Joe, 06/21/2022
-
Re: [Sphenix-tracking-l] [EXTERNAL] 20 segments with current G4 (10.07.p03),
Anthony Frawley, 06/21/2022
-
Re: [Sphenix-tracking-l] [EXTERNAL] 20 segments with current G4 (10.07.p03),
Osborn, Joe, 06/21/2022
Archive powered by MHonArc 2.6.24.