exampleB5::HadCalorimeterHit.cc

Particles, Track, Event, Run and Biasing
1

Hello G4 community,

I used ExampleB5 as a reference to assist with a current issue in my work. I observed that the G4cout command in the constructor of HadCalorimeterHit.cc does not output the expected statement (G4cout << "statement"). Additionally, the simulation results do not display the G4cout statement in the HadCalorimeterHit::Print() function. However, the EventAction.cc correctly records the hit in the HadCalorimeterHit sensitive detector. I am unable to determine why, if EventAction is recording the energy deposition (edep) for a hit in the HadCalorimeterHit sensitive detector, the G4cout statement in the constructor of HadCalorimeterHit.cc is not printing. Has anyone encountered a similar issue? For the other hit types (e.g., DriftChamberHit, HodoscopeHit, and EmCalorimeterHit), everything appears to be working correctly.

Geant4 Version: 11.1.1
Operating System: ubuntu 22.04lts
Compiler/Version:
CMake Version:

2

Hello,

The HadCalorimeterHit class provides two constructors:

    HadCalorimeterHit() = default;
    HadCalorimeterHit(G4int iCol, G4int iRow);

and the objects are created in HadCalorimeterSD::Initialize() using the default one (without parameters), see HadCalorimeterSD.cc:

  // fill calorimeter hits with zero energy deposition
  for (auto column = 0; column < kNofHadColumns; column++) {
    for (auto row = 0; row < kNofHadRows; row++) {
      fHitsCollection->insert(new HadCalorimeterHit());
    }
  }

I suppose that you have added your printing statement in the constructor with parameters, which is not called.

Best regards,

3

Thanks Dr Ivana. Issue resolved.

4

Hi,

I was going through the output of exampleB5 and noted G4Exception message at some places for a simulation of 10k events. One of the G4Exception message is pasted below:
-⁠-⁠-⁠-⁠-⁠-⁠-⁠-⁠ WWWW -⁠-⁠-⁠-⁠-⁠-⁠-⁠ G4Exception-⁠START -⁠-⁠-⁠-⁠-⁠-⁠-⁠-⁠ WWWW -⁠-⁠-⁠-⁠-⁠-⁠-⁠
*** G4Exception : GeomNav1002
issued by : G4Navigator::ComputeStep()
Stuck Track: potential geometry or navigation problem.
Track stuck, not moving for 10 steps.
Current phys volume: ‘worldPhysical’

  • at position : (-603.6802470845078,-10.51975824238436,797.226542006717)
    in direction: (-0.7842092357606798,0.1439671976672922,-0.603563849599591)
    (local position: (-603.6802470845078,-10.51975824238436,797.226542006717))
    (local direction: (-0.7842092357606798,0.1439671976672922,-0.603563849599591)).
    Previous phys volume: ‘magneticPhysical’

Likely geometry overlap -⁠ else navigation problem !
*** Trying to get unstuck using a push - expanding step to 1e-07 (mm) … Potential overlap in geometry !

*** This is just a warning message. ***
-⁠-⁠-⁠-⁠-⁠-⁠-⁠-⁠ WWWW -⁠-⁠-⁠-⁠-⁠-⁠-⁠-⁠ G4Exception-⁠END -⁠-⁠-⁠-⁠-⁠-⁠-⁠-⁠-⁠ WWWW -⁠-⁠-⁠-⁠-⁠-⁠-⁠

G4WT0 >
-⁠-⁠-⁠-⁠-⁠-⁠-⁠-⁠ WWWW -⁠-⁠-⁠-⁠-⁠-⁠-⁠ G4Exception-⁠START -⁠-⁠-⁠-⁠-⁠-⁠-⁠-⁠ WWWW -⁠-⁠-⁠-⁠-⁠-⁠-⁠
*** G4Exception : GeomNav1002
issued by : G4Navigator::ComputeStep()
Stuck Track: potential geometry or navigation problem.
Track stuck, not moving for 10 steps.
Current phys volume: ‘magneticPhysical’

  • at position : (-603.6859360284194,-10.51872027918331,797.2222341615236)
    in direction: (-0.8185004345445213,0.14120319305418,-0.5568830190639087)
    (local position: (-603.6859360284194,-797.2222341615236,-10.51872027918326))
    (local direction: (-0.8185004345445213,0.5568830190639087,0.14120319305418)).
    Previous phys volume: ‘worldPhysical’

Likely geometry overlap -⁠ else navigation problem !
*** Trying to get unstuck using a push - expanding step to 1e-07 (mm) … Potential overlap in geometry !

*** This is just a warning message. ***
-⁠-⁠-⁠-⁠-⁠-⁠-⁠-⁠ WWWW -⁠-⁠-⁠-⁠-⁠-⁠-⁠-⁠ G4Exception-⁠END -⁠-⁠-⁠-⁠-⁠-⁠-⁠-⁠-⁠ WWWW -⁠-⁠-⁠-⁠-⁠-⁠-⁠

I understand that it says that particle track got stuck but curious to know how it affects the final simulation results. And why does track simulation got stuck?. What can be done to avoid this G4Exception message.