|Message: Re: Stuck Track using very simple geometry and parallel beam model||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 John and Grabriele for your replies.
To preface my runtime environment, I was unfortunately having a grab-bag of issues, such as the c++11 versions of G4 not playing well on my Windows 10 development environment (debug mode has issues due to too many debug flags), and ended up regressing back to 10.01 with VS2010. For consistency, I used the same, 10.01 code base on my linux MT runtime
Regarding the nonphysical beam geometry, I was trying to run some idealized simulations of narrow-beam and broad-beam beam configurations for didactic purposes in the medical physics field (depth-dose at interfaces, etc but with additional scoring of particle flux characteristics such as energy/direction distributions etc.) to illustrate various physics, when I ran into these issues.
I had seen the voxel edge issue in previous forum posts in a different fashion (particles initiating from origin, with either even or oddly numbered parameterisation, and the need to shift by a non-integer multiple of voxel spacing in order to avoid stuck particle issues) from previous years, and had hoped this bug in the navigation had been resolved in the version I was using (as upgrading G4 versions is currently a problem for me).
Until the windows side of G4 catches up a bit, I will try the suggestions and add a bit of nonzero divergence to my beams, and update my linux runtime environment to the most recent version
thank you both for your time and your replies C: