Problem 136

Summary:	PostStepDoIt gets called which interactionlength was DOUBLE_MAX
Product:	Geant4	Reporter:	Hans-Peter.Wellisch
Component:	processes	Assignee:	kurasige
Status:	CLOSED WORKSFORME
Severity:	critical
Priority:	P5
Version:	2.0
Hardware:	PC
OS:	Linux

Description Hans-Peter.Wellisch 2000-07-19 08:59:29 CEST

Hi Hisaya,

  Thomas found a case where the Fission process is called for a final state on
Hydrogen (or even vacuum). In checking this I find that in the last
GetPhysicalInteractionLength call the fission process returned
1.7976931348623157e+308 so I would not expect Fission to be called for final
state production. The error occures already after a few thousend events.
I suspect a missing protection in either process/management or tracking, but
did not manage to find anything suspicious.
Can you please have a look? The test program is located in
/afs/cern.ch/user/t/tpapaeva/public/fissionMonitor.tar , the special fission
model I did for n-tof is also located there (G4ParaFissionModel.hh, only header
needed) This one would be quite urgent, as it leads subsequently to an infinite
loop.

Many greetings,

Hans-Peter.