Message: Re: Scintillation Process invoked in Non Scintillators Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Feedback Re: Scintillation Process invoked in Non Scintillators 

Forum: Processes Involving Optical Photons
Re: None Scintillation Process invoked in Non Scintillators (Marcus O'Flaherty)
Re: Feedback Re: Scintillation Process invoked in Non Scintillators (Gumplinger Peter)
Re: Question Re: Scintillation Process invoked in Non Scintillators (Marcus O'Flaherty)
Re: Feedback Re: Scintillation Process invoked in Non Scintillators (Gumplinger Peter)
Re: None Re: Scintillation Process invoked in Non Scintillators (Marcus O'Flaherty)
Date: 13 Jun, 2016
From: Gumplinger Peter <Gumplinger Peter>

> One last question, though, if you would. There are two lines there: add
> as last process for PostStepDoIt and AtRestDoIt. I see scintillation in
> AtRestDoIt, but not PostStepDoIt?
> 
> **PostStepDoIt (after all invocations):&#13;
> &#13;
>     ++List of invoked processes: &#13;
>       1) Transportation&#13;
>       2) msc&#13;
>       3) eBrem (Forced)&#13;

I don't know ....

I do know that this has to do with the specific code in source/tracking/srcG4SteppingVerbose.cc.

It doesn't print all of the processes, only those with:

(*fSelectedPostStepDoItVector)[npGPIL] == 2 and (*fSelectedPostStepDoItVector)[npGPIL] == 1

while G4Scintillation has 5.

I don't know what this flag means - I suspect it means (>0) that the process was actually invoked during this particular step. I think it is an oversight that 5 isn't also printed.

Now, G4Scintillation is

(*fSelectedAtRestDoItVector)[npGPIL] == 1

and so it is printed.

 Add Message Add Message
to: "Re: Scintillation Process invoked in Non Scintillators"

 Subscribe Subscribe

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