|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)|
Thank you for the answer, it seems pretty the same idea that was in second tips and tricks link. But I'm not still sure about implementation. It will definitely work for the particles which born below limit, I put a flag at PreUserTrackingAction and propagate it at PostUserTrackingActions. But that's not the only way how I get particles. E.g. for my primary track: Step# X(mm) Y(mm) Z(mm) KinE(MeV) dE(MeV) StepLeng TrackLeng NextVolume ProcName 0 -9.39 -300 -4.27 14 0 0 0 worldPV initStep 1 -13.5 -275 -6.44 14 0 25.4 25.4 leafPVL Transportation 2 -15.1 -265 -7.31 14 0 10.2 35.6 leafPVL Transportation .... 26 140 118 2.03 0.0162 0.0103 8.52 488 watBoxPV hadElastic 27 131 123 -0.544 0.0028 0.0134 10.9 499 watBoxPV hadElastic <-- somewhere here I'm putting a flag from UserSteppingAction to UserTrackInformation 28 131 124 -3.24 0.00231 0.000492 2.75 502 watBoxPV hadElastic ...
35 350 74.6 20.3 9.42e-05 0 208 735 OutOfWorld Transportation Track (trackID 1, parentID 0) is processed with stopping code 2
After that at PostUserTrackingAction I will have a flag at associated UserTrackInformation and list of all secondaries from all steps, but I definitely need only that were born at steps 27+. Maybe I can put an exact TrackID of secondary particle instead of flag, but here I'm not sure that they exist by this time. I didn't follow the source code, but from book for toolkit developers it's not clear, "The parentID and the process pointer which created this track are set" and nothing about the Track ID itself. Also potentially IDs might change from StackingAction.