|Message: Re: RE: How should I slice up a volume to tabulate charge deposition?||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)|
On Tue, 17 Jun 2008 22:06:04 GMT, Asai, Makoto wrote: > Hi Mark, > > With the command-based scoring feature in Geant4 version 9.1, > you don't need to implement any extra geometry for scoring. > All you need is the real material volumes. Then, just utilize the > UI commands to define the scoring mesh and the quantities you > want to score. > Please try examples/extended/runAndEvent/RE03 > > Makoto
Thanks for reminding me about this; it simplifies the slicing and dicing considerably. However, upon reviewing your charts from the February meeting in Tokyo, it seems that the actual scoring uses the same approach I've described: particle tracks are interrupted at scoring-region boundaries in the parallel geometry defined by the commands, and (for my application) I would implicitly use a G4PSCellCharge primitive scorer on each cell to count the difference in charge between particles entering the volume and those exiting the volume. What I'm trying to do is avoid interruption of tracks by the very fine mesh of cell boundaries I need to use; if I could just let the physics interrupt the tracks when there was an interaction, and log any charge liberated or deposited at that point, I'd waste a lot less processing time and introduce fewer possibilities for round-off tracking errors (which in your charts you noted was a possibility for too-fine meshes in the command-based scoring).
Can anybody suggest a way that I can "get my hands on" the individual interactions? For example, is there a method that is called every time a particle is created or discarded, on top of which I could build some code to locate the interaction and tabulate any charge-deposition changes there? Some kind of Pre- or PostStepAction I could register to look at the genesis or fate of the particle in the step?
|Inline Depth:||Outline Depth:||Add message:|