Message: Re: InvokePostStepDoIt question Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

None Re: InvokePostStepDoIt question 

Forum: Event and Track Management
Re: Question InvokePostStepDoIt question (Fernando Rannou)
Date: 26 May, 2008
From: Marc Verderi <Marc Verderi>

Hello Fernando,

I believe this has to do with the fact the process ordering in the 
GetPhysicalInteractionLength loop is reversed from the one in the DoIt 
one (this would need some time to be explained). The 
fSelectedPostStepDoItVector ordering corresponds certainly to the 
GetPhysicalInteractionLength ordering loop, with, for example the 
"transportation" being the last one : as such, its "condition" has been 
stored in the last element of the vector, but it will be the first 
having its DoIt called.

Cheers,
Marc


Fernando Rannou a écrit :
> *** Discussion title: Event and Track Management
> Email replies to PublicHyperNews@slac.stanford.edu must include:
>   In-Reply-To: <"/eventtrackmanage/814"@geant4-hn.slac.stanford.edu>
>   Subject: ...change this to be about your reply.
>
> Hello, sorry to bother you again with this question, but I'm not sure
> whether this function is buggy or not:
>
> Please take a look at G4SteppingManager::InvokePostStepDoItProcs():
>
> for (size_t np=0; np < MAXofPostStepLoops; np++) {
>    G4int Cond = (*fSelectedPostStepDoItVector)[MAXofPostStepLoops-np-1];
>    if (Cond != ...)
>    {
>        InvokePSDIP(np);
>    }
>   ...
>
> }
>
> notice that the "if" tests
> fSelectedPostStepDoItVector[MAXofPostStepLoops-np-1] but the np process
> is called.
>
> Is this correct?
>
> Thanks Fernando Rannou
>   


Inline Depth:
 1 1
 All All
Outline Depth:
 1 1
 2 2
 All All
Add message: (add)

 Add Message Add Message
to: "Re: InvokePostStepDoIt question"

 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 ]