Dear Geant4 team, I was able to digitize using the ROGeometry stuff until a week ago using G4.3.2. From this week onwards, it does not work. It turns out that: In Geant4.3.2/source/digits+hits/detector/src/G4VReadOutGeometry.cc, the G4Navigator class has two calls to its member function named LocateGlobalPointAndUpdateTouchable. The first call does not match arguements of any member function declarations in Geant4.3.2/source/geometry/volumes/include/G4Navigator.hh. The second call uses the track momentum information as one of the arguements. In my case this returns the 'world' volume instead of the appropriate readout geometry volume. If I replace this call with the version of the member function without the momentum information and set the last arguement as 'false' then it returns the correct readout geometry volume. So at the moment, I have to copy this .cc file and replace both the calls with the version of member function without the momentum info. They label this member function to be the old version, but it is the only one which works for the digitization purpose. I also explicitly set the last arguement as 'false' as indicated by the comments in this .cc file. regards, Sajan
Problem seems related to LocateGlobalPointAndUpdateTouchable method of the G4Navigator used in RO geometry (variable ROnavigator in G4VReadOutGeometry.cc files). The user, by changing: LocateGlobalPointAndUpdateTouchable( currentStep->GetPreStepPoint()->GetPosition(), currentStep->GetPreStepPoint()->GetMomentumDirection(), touchableHistory); with: LocateGlobalPointAndUpdateTouchable( currentStep->GetPreStepPoint()->GetPosition(), touchableHistory,false); got a temporary fix. Before that, the call was returning the world volume, instead of the RO volume. Due to the fact that the problem looks to be fixed when the track direction is not used anymore let me think this can be a problem with the geometry. Marc Verderi
Can the user please verify if this problem still exist in the latest release 4.0 + patch-02 ? Point location now implicitely adopts direction in 4.0. The problem report will be otherwise closed.
Closing bug as invalid
