Details
-
Improvement
-
Status: Done (View Workflow)
-
Low
-
Resolution: Done
-
None
-
None
Description
For tracking in magnetic field in CMS detector we observe tracks being stuck and need pushes to recover. This happens with VecGeom installation (not with native geometry) and in volumes which are unions of CutTubs. The error message looks like:
-
-
- G4Exception : GeomNav1002
issued by : G4Navigator::ComputeStep()
Stuck Track: potential geometry or navigation problem.
Track stuck, not moving for 10 steps.
Current phys volume: 'PixelForwardInnerDiskOuterRing'
- G4Exception : GeomNav1002
-
- at position : (-20.21612115201446,114.9815721065278,-390.2499999993482)
in direction: (-0.0560404498019309,0.3135342786240882,-0.9479217921926207)
(local position: (-20.21612115201446,114.9815721065278,13.25000000065182))
(local direction: (-0.0560404498019309,0.3135342786240882,-0.9479217921926207)).
Previous phys volume: 'PixelForwardDiskZminus'
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. ***
-
-
Attachments
Issue Links
- contains
-
VECGEOM-542 Generic tube with phi cut gives convention errors
-
- Closed
-