sPHENIX MAPS tracker discussion

["Osborn, Joe" <osbornjd AT ornl.gov>]

Hi Cameron,

 

Thanks for the email – it looks like that doesn’t fix it. I’ve been looking through the G4_Mvtx history and I can’t seem to find anything obvious that would be causing this issue. I’m wondering if there was a calibration file or something similar that was responsible for the Mvtx geometry that got changed? I think Tony originally wrote the code that is now causing Acts to crash with the most up to date macros, so maybe he knows where “av_1” actually came from and this can help us track down if/where it got changed.

 

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

 

Joe Osborn, Ph.D.

Postdoctoral Research Associate

Oak Ridge National Laboratory

osbornjd AT ornl.gov

(859)-433-8738

 

 

From: Cameron Thomas Dean <cameron.dean AT cern.ch>
Date: Monday, August 31, 2020 at 1:44 PM
To: "Osborn, Joe" <osbornjd AT ornl.gov>, sPHENIX-tracking-l <sphenix-tracking-l-bounces AT lists.bnl.gov>, "sphenix-maps-l AT lists.bnl.gov" <sphenix-maps-l AT lists.bnl.gov>
Subject: [EXTERNAL] Re: [Sphenix-maps-l] MVTX TGeoNode Name Change?

 

Hi Joe,

Sorry about the issues here. To try and trace this down, would it be possible to run Acts with the following set to false?
https://github.com/sPHENIX-Collaboration/macros/blob/master/common/G4_Mvtx.C#L31

Line 31: bool MVTX_SERVICE = false;

I don’t recall any changes to objects with “av_1” in their name but if the problem disappears with this change then the issue is related to the service barrel. I’ll be able to debug further if this is the case.

 

Cheers,
Cameron

From: sPHENIX-MAPS-l <sphenix-maps-l-bounces AT lists.bnl.gov> on behalf of "Osborn, Joe" <osbornjd AT ornl.gov>
Date: Monday, August 31, 2020 at 8:53 AM
To: sPHENIX-tracking-l <sphenix-tracking-l-bounces AT lists.bnl.gov>, "sphenix-maps-l AT lists.bnl.gov" <sphenix-maps-l AT lists.bnl.gov>
Subject: [Sphenix-maps-l] MVTX TGeoNode Name Change?

 

Hi MVTX experts,

 

I updated my macros repository this morning and it seems that the Acts tracking no longer works because of a change in the MVTX geometry. Previously we were accessing the TGeoNodes in the geometry by iterating over the TGeoVolume and accessing the MVTX objects by getting the nodes that had “av_1” in their name. This now returns no valid MVTX nodes, which means I’m guessing that the node names were changed. Perhaps this is related to the recent addition of the MVTX services into the geometry?

 

Does anyone have a pointer as to what happened here? Just for clarity, the way we were accessing the MVTX nodes previously can be found here in lines 807-826.

 

Thanks for any help you may have,

 

Joe Osborn

 

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

 

Joe Osborn, Ph.D.

Postdoctoral Research Associate

Oak Ridge National Laboratory

osbornjd AT ornl.gov

(859)-433-8738