[G4VecGeom_X] Multiple relvals failed with "Stuck track"

[iarspider]

Several RelVals (160.0, 1304.18, 1304.181, 1304.182, 250200.118, 250200.182 ) failed with Stuck Track: potential geometry or navigation problem.

Error message:

-------- EEEE ------- G4Exception-START -------- EEEE -------
*** G4Exception : GeomNav0003
      issued by : G4Navigator::ComputeStep()
Stuck Track: potential geometry or navigation problem.
  Track stuck, not moving for 25 steps.
  Current  phys volume: 'PixelForwardInnerDiskCFInnerRing'
   - at position : (-3.025221731688998,36.22389584399818,-310.997522674291)
     in direction: (-0.5021349830335725,0.8473731737201923,-0.1726822610265527)
    (local position: (-3.025221731688998,36.22389584399818,1.002477325709037))
    (local direction: (-0.5021349830335725,0.8473731737201923,-0.1726822610265527)).
  Previous phys volume: 'PixelForwardDiskZminus'

  Likely geometry overlap - else navigation problem !
 Track *abandoned* due to excessive number of Zero steps. Event aborted. 


TrackID=8669 ParentID=0  pi+; Ekin(MeV)=218.227; time(ns)=7.10096; status=0
   position(mm): (-3.02522,36.2239,-310.998); direction: (-0.502135,0.847373,-0.172682)
   PhysicalVolume: PixelForwardInnerDiskCFInnerRing; material: FPix_CFSkin_InnerInnerRing
   stepNumber=383; stepLength(mm)=1e-07; weight=1 

-------- EEEE -------- G4Exception-END --------- EEEE -------

[cmsbuild]

A new Issue was created by @iarspider .

@Dr15Jones, @perrotta, @dpiparo, @makortel, @smuzaffar, @qliphy can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[Dr15Jones]

Assign simulation

[cmsbuild]

New categories assigned: simulation

@mdhildreth,@civanch you have been requested to review this Pull request/Issue and eventually sign? Thanks

[iarspider]

@cms-sw/simulation-l2 any progress? This still happens, e.g. link

[civanch]

@iarspider , the problem may be reduced/fixed if we will integrate vecgeom 1.1.20 (cms-sw/cmsdist#7735 )

[civanch]

+1

the problem is fixed now

[cmsbuild]

This issue is fully signed and ready to be closed.

[civanch]

@iarspider , you may close this issue now.