|Message: Re: possible flagging the process at the prepoint ?||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
On Mon, 08 Oct 2018 08:54:04 GMT, David Sangcheol Lee wrote:> I understand what you are trying to say. The objective I am looking is
> to find the process that goes under the each tracking step. If I flag > the creation process, that would tell me what process is used to create > the particle but not the step when the particle is tracking.
So there are almost always multiple processes which contribute to the state of the track at the end of each step. There is the DiscreteProcess which limited the step (i.e., which caused the step to be the exact length it happens to be), and that is what you find in the GetProcessDefinedStep() output. But there are continuous processes (like energy loss, Cherenkov emission, multiple scattering) which also affect the track's kinematics, but which are not step-limiting.
Then, you need to realize the for a given step, the "PreStepPoint()" is nothing more nor less than the PostStepPoint of the previous step! It's just copied over. So if you look at PreStepPoint()->GetProcessDefinedStep(), you are not learning anything new; that's just the process that limited the previous step. Obviously, for the first step that pointer will be null.
There is no process which "started the step". Steps are started by G4Transportation, moving the track from point A to point B.
I hope that helps clarify things, at least a little.
-- Michael Kelsey
|Inline Depth:||Outline Depth:||Add message:|