|Message: Creating process name mismatched||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 saw this interesting feature during detector simulation and I could produce it with examples/novice/ExN02 with minimal modifications. Specifically, I changed to the QGSP_BERT physics list and added a user tracking action class to print out all tracked particles. For mu- with kinetic energy of 0.5 MeV in the center of the detector, I saw that the daughter list from the mu- is consistent with a mu- decay, i.e., nu_mu + anti_nu_e + e-, but the creating process name (track->GetCreatorProcess()->GetProcessName()) is muMinusCaptureAtRest! I understand that mu- could decay or get captured depending on where it stopped, but the creating process name seems inconsistent with the used physics process.
I also tried turning off the muMinusCaptureAtRest process using /process/inactive muMinusCaptureAtRest in the macro, then track->GetCreatorProcess()->GetProcessName() correctly gave the process name as 'Decay'
Debian Squeeze 64-bit on AMD, gcc 4.4.5, GEANT4.9.4.p02
|Inline Depth:||Outline Depth:||Add message:|