Skip to Content.
Sympa Menu

sphenix-tracking-l - Re: [Sphenix-tracking-l] Draft poster on "Vertex determination in sPHENIX"

sphenix-tracking-l AT lists.bnl.gov

Subject: sPHENIX tracking discussion

List archive

Chronological Thread  
  • From: Anthony Frawley <afrawley AT fsu.edu>
  • To: "Osborn, Joseph" <josborn1 AT bnl.gov>, "sphenix-tracking-l AT lists.bnl.gov" <sphenix-tracking-l AT lists.bnl.gov>
  • Subject: Re: [Sphenix-tracking-l] Draft poster on "Vertex determination in sPHENIX"
  • Date: Mon, 28 Aug 2023 21:14:26 +0000

Hi Joe,

Thanks for the comments.

Good point. The figures have been redone using the sPHENIX style macro.

The speed difference from RAVE was taken from a presentation I made at the time in the tracking meeting, where I had recorded both the RAVE and PHSimpleVertexFinder execution times from a log file of the same AuAu 50 KHz job. It is as good a number as we will get. Resuscitating the RAVE interface to our tracking would be non-trivial, and I think it is not needed.

I made the suggested wording changes.

The tree used to extract the two-track DCA plot was made by Cameron. I thought they were single D0, but I am checking with Cameron.

I will upload a second version once I hear back from Cameron.

Thanks
Tony

From: Osborn, Joseph <josborn1 AT bnl.gov>
Sent: Monday, August 28, 2023 11:38 AM
To: Anthony Frawley <afrawley AT fsu.edu>; sphenix-tracking-l AT lists.bnl.gov <sphenix-tracking-l AT lists.bnl.gov>
Subject: Re: Draft poster on "Vertex determination in sPHENIX"
 

Hi Tony,

 

Thanks for the poster, here are a few comments.

 

-  Is it possible to remake the figures using the sPHENIX style macro? You can get it here with some instructions on how to use it, should be as simple as including a file and calling a function in your plotting macro.

https://github.com/sPHENIX-Collaboration/macros/tree/master/macros/sPHENIXStyle

 

- I assume that the 14x faster than RAVE is recollection from when the vertexing algorithm was initially developed, or were you able to find the logs for these jobs? I know we found it was way faster, I just don’t remember the exact number. Just asking as we should be able to defend these numbers in the event some RAVE users/developers are walking around, although they should be easily defendable since our vertexing algorithm is inherently less complex.

 

- Under “Track DCA Performance” I suggest changing “perigee surface containing the event vertex” to “perigee surface defined by the event vertex.”

 

- Under “Secondary vertex determination” I suggest changing “This is done using the KFP…” to “This is accomplished using the KFP…”

 

Is the two track DCA plot for single D0s or for the D0s in your single PYTHIA jet events? Could be worth clarifying, as the way it is written right now implies to me that it is in simulated single D0 decays.

 

Joe

 

___________________________

Joe Osborn, Ph.D

Physics Department

Brookhaven National Laboratory

josborn1 AT bnl.gov

 

 

From: sPHENIX-tracking-l <sphenix-tracking-l-bounces AT lists.bnl.gov> on behalf of Anthony Frawley via sPHENIX-tracking-l <sphenix-tracking-l AT lists.bnl.gov>
Date: Thursday, August 24, 2023 at 10:16 PM
To: sphenix-tracking-l AT lists.bnl.gov <sphenix-tracking-l AT lists.bnl.gov>
Subject: Re: [Sphenix-tracking-l] Draft poster on "Vertex determination in sPHENIX"

Sorry, forgot to include the direct link:

 

The note supporting the new plots is in the works.

 

Tony


From: Anthony Frawley <afrawley AT fsu.edu>
Sent: Thursday, August 24, 2023 3:41 PM
To: sphenix-tracking-l AT lists.bnl.gov <sphenix-tracking-l AT lists.bnl.gov>
Cc: Anthony Frawley <afrawley AT fsu.edu>
Subject: Draft poster on "Vertex determination in sPHENIX"

 

Hi All,

 

I have uploaded a draft of the poster "Vertex determination in sPHENIX" to Invenio. It can be accessed (I think) by accessing the "requests" tab in the sPHENIX community.

 

There are still minor details to finish, mostly the references. Comments welcome.

 

Tony

 




Archive powered by MHonArc 2.6.24.

Top of Page