|Message: Gamma production from fast neutron scattering||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 am attempting to simulate a plastic neutron detector in the range of 50-100 MeV neutrons. I am using geant4.8.2 with the physics list "QGSP_BIC_HP".
When I run the simulation, there is a large disagreement between collected data and the simulated values of the detector. The simulation shows high-energy gammas producing excited electrons that are far too easy to detect. These gammas were released during the interaction of a neutron with 12C. A neutron hits a 12C nucleus, creating a 11B nucleus, a proton, a neutron, and three gammas.
I did a brief search of the forums to see if there was a solution to this problem. I found the post #1045 ( http://hypernews.slac.stanford.edu/HyperNews/geant4/get/hadronprocess/1045.html ) which describes what seems to be a similar issue wherein a neutron interacting with 6Li produces too many gammas. Would this issue be the same as mine, and, if so, could my issue be fixed by a modification of the patch attached to post #1045?
If there is any other information necessary to diagnose this problem, I would be happy to find it.
|Inline Depth:||Outline Depth:||Add message:|