|Message: Re: Calculate deposit from child track with condition||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 Tue, 14 Nov 2017 20:57:44 GMT, Alexey Solovyev wrote:
> I need to score dose deposit from all particles, which born from certain > ancestor particle which had some condition. To be more precise, I need > to explicitly calculate the deposit from secondary protons and > electrons, which born from neutron with < 10 keV, and that neutrons are > born somewhere inside my volumes (collimators) or moderated (filters), > while particle source is 14 MeV neutrons. > > With scoring part I'm pretty certain that I should score deposit in my > SD for all particles which have some condition in my class inherited > from G4UserTrackInformation.
To do this, you need to have code which runs when both the parent track and the new secondaries exist. The place for that is in a G4SteppingAction subclass. This class gets called on every G4Step, so you'll want to put in short and simple if-blocks to bail out quickly if the track or step doesn't meet your criteria (not a neutron, too much energy, etc.). Do volume checking towards the end of those tests.
Once you have a good step, you have access to the parent particle, as well as the list of secondaries created by that parent. Those secondaries are G4Track objects, so at this point you can attach user track info to them to identify them as being "interesting." Then later, when your SD sees them deposit energy, it will see the user-info flag and can do what you want.
-- Michael Kelsey
|Inline Depth:||Outline Depth:||Add message:|