|Message: Tracking of low energy particles near a boundary||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)|
Hi, I'm looking at very low energy particles moving towards the boundary of a volume, i.e. a delta ray electron produced in volume A and moving towards volume B. As far as I understand tracking in Geant4, the step length of such a particle may be limited by the presence of the boundary between A and B: in this case, the particle is moved to the boundary and G4Navigator::fExitedMother is set to true. This will have the effect of "blocking" the current volume A when searching for the volume entered by the particle (B in this case) with G4VoxelNavigation::LevelLocate; this seems to be fine since the particle is leaving volume A so it makes no sense to check if it is entering volume A.
However, in this scheme a problem could arise when the direction of a low energy particle is heavily modified by e.g. multiple scattering. Such a particle may be moved to the border, triggering all the above described procedures; if now the modified momentum direction makes the particle re-enter in volume A, then the voxel navigator will identify the wrong post-step volume since A is blocked.
I'm investigating a strange behaviour in my simulations which seems to stem from the above described situation, but I don't know if such a situation can effectively happen given the internals of the tracking algorithm. I'm inspecting the code flow with gdb to check it, but I'd appreciate if some tracking expert could shed some light on this topic.
|Inline Depth:||Outline Depth:||Add message:|