Message: Re: training lecture problem Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question Re: training lecture problem 

Forum: Event and Track Management
Re: None training lecture problem (wangym)
Re: Disagree Re: training lecture problem (Gumplinger Peter)
Re: Question Re: training lecture problem (wangym)
Date: 31 Mar, 2009
From: wangym <wangym>

1.The particle's velocity at the beginning of the step is calculated.

2.Each active discrete or continuous process must propose a step length based on the interaction it describes. The smallest of these step lengths is taken.

3.The geometry navigator calculates "Safety", the distance to the next volume boundary. If the minimum physical-step-length from the processes is shorter than "Safety", the physical-step-length is selected as the next step length. In this case, no further geometrical calculations will be performed.

4.If the minimum physical-step-length from the processes is longer than "Safety", the distance to the next boundary is re-calculated.

5.The smaller of the minimum physical-step-length and the geometric step length is taken.

6.All active continuous processes are invoked. Note that the particle's kinetic energy will be updated only after all invoked processes have completed. The change in kinetic energy will be the sum of the contributions from these processes.

7.The track is checked to see whether or not it has been terminated by a continuous process.

8.The current track properties are updated before discrete processes are invoked. This includes:

updating the kinetic energy of the current track particle (note that 'sumEnergyChange' is the sum of the new kinetic energy after each continuos process was invoked, and NOT the sum of the energy difference before and after the process invocation) and

updating position and time.

9.The discrete process is invoked. After the invocation,

the energy of the current track particle is updated, and

the secondaries from ParticleChange are stored in SecondaryList. This includes constructing "G4Track" objects, and setting their member data. Note that the stepping manager is responsible for deleting secodaries from ParticleChange.

10.The track is checked to see whether or not it has been terminated by the discrete process.

11."Safety" is updated.

12.If the step was limited by the volume boundary, push the particle into the next volume.

13.Invoke the user intervention G4UserSteppingAction.

14.Handle hit information.

15.Save data to Trajectory.

16.Update the mean free paths of the discrete processes.

17.If the parent particle is still alive, reset the maximum interaction length of the discrete process which has occurred.

18.One step completed.

My question is 9.

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

1 Question: Re: training lecture problem   (wangym - 31 Mar, 2009)
(_ Question: Re: training lecture problem   (wangym - 31 Mar, 2009)
(_ Feedback: Re: training lecture problem   (Gumplinger Peter - 01 Apr, 2009)
1 Question: Re: training lecture problem   (wangym - 09 Nov, 2009)
1 Question: Re: training lecture problem   (wangym - 11 Nov, 2009)
... 4 Message(s)
2 Question: Re: training lecture problem   (wangym - 13 Nov, 2009)
 Add Message Add Message
to: "Re: training lecture problem"

 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 ]