The job terminates with the following dump: *** Dump for solid - OCMS *** =================================================== Solid type: G4Tubs Parameters: inner radius : 0 mm outer radius : 13000 mm half length Z: 27000 mm starting phi : 0 degrees delta phi : 360 degrees ----------------------------------------------------------- Position: p.x() = -143151.8084426259 mm p.y() = -135861.7443316784 mm p.z() = 1174255.58497939 mm Direction: v.x() = -0.5547001962252291 v.y() = 0.8320502943378437 v.z() = 0 Proposed distance : snxt = 9e+99 mm
More information from T.Todorov: This one looks like the tracking escaped the main volume and went more then one kilometer away before crashing. But it happends only in one event out of about 25000 (single electron), more precisely it happened twice over a sample of 50K.
This means that G4Tubs::DistanceToOut(p,v,...)is called from outside. Therefore since the particle is located far from surface, the reason is spike in navigation and does not relate to G4Tubs tracking functions.
Simple application showing the problem is needed to resove a prehistory of the invalid call of DistanceToOut
