Problem 714

Summary:	Error: /process/inactivate annihil
Product:	Examples/Basic and Novice	Reporter:	mcchang
Component:	N03	Assignee:	kurasige
Status:	RESOLVED FIXED
Severity:	normal	CC:	mcchang
Priority:	P2
Version:	6.2
Hardware:	PC
OS:	Linux

Description mcchang 2005-01-15 21:17:43 CET

I use the Geant4 6.2.p2 version under RedHat9, Linux. While I try to switch
off/on the known physics process, only the /process/inactivate annihil can't be
proceed. The Error messages are as below:
==============================================================================
G4SteppingManager::InvokeAtRestDoItProcs: No AtRestDoIt process is active.

*** G4Exception: Aborting execution ***
Abort
==============================================================================

For the other cases, say,
/process/inactivate msc  ---> OK
/process/inactivate eIoni --> OK
/process/inactivate eBrem --> OK
/process/inactivate annihil  ---> Fail
/process/inactivate conv --> OK
/process/inactivate compt --> OK
/process/inactivate phot  --> OK

Does anyone know how to solve it?

Comment 1 mcchang 2005-01-15 23:15:59 CET

In the Geant4 7.0 version, this error is still there. But, there is no "Abort"
this time. I tried several particle beams and found that in the pi- case
("/gun/particle/pi-"), there is no such error message while proceed the
"/run/beamOn 1" after the "/process/inactivate annihil". But, for
e-/e+/gamma/pi0 will have the error message.

==========================================================================
G4SteppingManager::InvokeAtRestDoItProcs: No AtRestDoIt process is active.
==========================================================================

Does anyone know the reason?

Best regards,

Comment 2 kurasige 2005-01-17 18:16:59 CET

Annihilation is the only process for AtRest step for G4Positron. If you
inactivate "annihilation", no process is assigned for stopped positron. Same
situation can occurs for many particles if you inactivate "decay".
 In such case, the stepping manager can not treat the stopped track properly and
issues the error message. Geant4 is aborted before release 6.2. In 7.0, the
track is just killed with the error message.