Message: Atomic Deexcitation in Penelope Physics Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question Atomic Deexcitation in Penelope Physics 

Forum: Physics List
Date: 09 Feb, 2012
From: Elena Novikova <Elena Novikova>

I thought I will rephrase my question which was (probably mistakenly) placed on another forum.

I noticed that G4EmPenelopePhysics::ConstructProcess() calls G4PenelopeIonisationModel (for e-and e+), which in turn, has an object of the class G4AtomicDeexcitation as one of its private members. At the same time, at the end of the G4EmPenelopePhysics::ConstructProcess() method, G4UAtomicDeexcitation class is engaged.

Thus, two different (?) deexcitation classes (G4AtomicDeexcitation and G4UAtomicDeexcitation) are linked to the same EM physics.

Was that meant to be so, or this is a temporary oversight?

When I am setting G4EmProcessOptions, am I "talking" to G4UAtomicDeexcitation engaged at the end of G4EmPenelopePhysics::ConstructProcess(), or to G4AtomicDeexcitation linked to e- and e+ in the main part of G4EmPenelopePhysics::ConstructProcess()?

The reason I got interested in this was the message on the standard output that appears when running Penelope:

*                  W A R N I N G ! ! !                   *
*                                                        * 
*  Class G4AtomicDeexcitation is obsolete. It has been   *
* discontinued and is going to be removed by next Geant4 * 
*     release please migrate to G4UAtomDeexcitation.     *
*                                                        *

I traced that message to the scenario I described above.


--Elena Novikova.

 Add Message Add Message
to: "Atomic Deexcitation in Penelope Physics"

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews

[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]