Message: Re: Understanding ProcName Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Feedback Re: Understanding ProcName 

Forum: Processes Involving Optical Photons
Re: Question Understanding ProcName
Date: 23 Aug, 2013
From: Gumplinger Peter <Gumplinger Peter>

Dear Baptiste,

First and foremost, The ProcName you are questioning is:

fStep->GetPostStepPoint()->GetProcessDefinedStep()->GetProcessName()

e.g. it is the name of the process that limited this current step.

G4Scintillation is a so called G4VRestDiscreteProcess and it is StronglyForced but its GetMeanFreePath and GetMeanLifeTime return DBL_MAX. This means, that as a process it will always be considered but it will not limit the step either in space or in time. Therefore, I do not understand why you get "Scintillation" instead of "Decay" in this line:

> 119 -8.52 351 9.01e+03 0 0 0 3.41e+03 physical_box_TEST Scintillation

If I find time, I'll debug this and try to understand it.

The G4Cerenkov process can, in some cases depending on user input, limit the step. In those cases you should see Cerenkov written in the SteppingVerbose. In most cases, another process will have limited the step and that process' name will appear. This doesn't mean that no Cerenkov photons were produced, only that it wasn't the Cerenkov process that limited the step.

The optical photons are not called 'Cerenkov' when they are propagated, nor are they called 'Scintillation'; regardless of how they have been produced their name is 'opticalphoton'.

Peter

 Add Message Add Message
to: "Re: Understanding ProcName"

 Subscribe Subscribe

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