|Message: Re: Tracking in a UnionSolid||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)|
> When I generate events only in the end-cap part, then > It shows always single "LH2_target_log" immediately followed by different logical volumes, which is indication that this track indeed originated > in the target volume, but however doesn't interact with the target itself.
Yes, it looks like in this case the track always just takes a single step from its origin to the volume boundary. Now, this in itself is not necessarily an indication that something's gone wrong. Can you please regenerate the track but with:
(It looks like, you may also have to recompile:
with the environment variable G4VERBOSE set to 1)
If you don't understand the output a look at the code:
Please, post the output for the first few steps for one track originating in the end-cap. What I am looking for is the list of processes that were invoked during the AlongStepDoItAllDone():
It should include the same list of processes that you see for a track originating in the cylinder. It is seems, in the cylinder, the ionization 'process' limits steps, while it doesn't in the end-cap. Still, the process should appear as 'invoked'.
If you find the only process is 'Transportation' (PostStepDoItAllDone), then we've really got a problem. You should ask, what is the name of the material at the preStepPoint (as opposed to the name of the 'logical volume'):
Is it what it should be?
Happy hunting, Peter
|Inline Depth:||Outline Depth:||Add message:|