|Message: alternative to scoring planes||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)|
I have a situation where I need to track a set of particles traveling through a series of volumes. I would like to read off various particle properties at the volume boundaries. At the moment I am achieving this by placing ultra thin planes (1e-11m) between my main volumes. This forces a stepping point in Geant. Then in the usersteppingaction I can check for the plane volume name and store the particle information if its in this volume.
This works ok - but when I extend the example to several thousand volumes then I end up with a large memory overhead in building the planes. There is also the fact that several thousand 'thin' planes start to add up! (and I need nanometer precision at the end of all these volumes...)
Is there a convenient way in UserSteppingAction to save particle information at the exact point that a particle is leaving a given volume? I've tried comparing the current volume and the nextvolume, but this does not seem to be accurate as each track will be at a slightly different distance from the boundary when this condition of nextvolume should be different is found. There is also the problem that sometimes the volume/nextvolume check is a bit dubious. I have some volumes which built in a mother/daughter fashion and if the exiting boundary is one which both mother and daughter share then it gives the current volume as the daughter and the next volume as the mother, when in reality the next volume should be a seperate volume entirely.
|Inline Depth:||Outline Depth:||Add message:|