|Message: Re: G4Scintillation: Wrong number of photons||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)|
We are aware of this problem for some time now and are working on a solution. It was also an item of discussion at the recent G4 workshop.
The problem is one of 'stepping manager' (G4SteppingManager2.cc) where for a 'killed' track in one PostStep action, another PostStep action is not called even when it is 'forced'. Unfortunately, fixing this code, which seems simple enough causes a whole set of new problems.
I welcome your posting because it adds more urgency to the issue. I sincerely hope that the next public release comes with a fix. In the meantime, you may want to do the following (excerpt from an email):
At the moment the only solution is changing all 'StopAndKill' assignments in all processes to 'StopButAlive'. This was found to cause only a tiny performance penalty. The 'break' statement in the InvokePostStepDoIt method cannot be removed because then the G4OpBoundary process would be called for an optical photon at the world-boundary, causing a crash because of an ill (incomplete) defined PostStepPoint in this case.
Regards, Peter Gumplinger
|Inline Depth:||Outline Depth:||Add message:|