|Message: Re: Cross Section code Hadr03 Example||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 Thu, 10 Dec 2015 07:33:38 GMT, jeonyboy wrote:
> Hello, I am novice c++/geant4 user. > > I am interested in gaining cross section values for: > > 1. Cross section values for elastic/inelastic reaction for silicon and > proton/neutron > 2. Cross section values for each secondary particles > 3. Total Energy deposited by only secondary particles produced > > I have been using Hadr03 and Hadr06 examples to build my own. Hadr03 has > code that kills after first interaction event which isn't realistic and > stops me from finding out secondary particles produced from secondary > particles. > > My question is when I delete the following code, my executable file > produced fails. > > G4RunManager::GetRunManager()->AbortEvent(); > > > How would I fix this? I am using geant4 on Window 7 with Visual Studio > 2013. >
As we discussed in a previous thread, Hadr03 is designed to survey nuclear reactions. It assumes one interaction per event, and only one. There is a mechanism to build a string per nuclear channel. Also, nuclear interaction length is computed as the mean value of the unique step of the incident particle. If you allow secondary particles to travel and to become incident projectiles, all those things do not work or become wrong.
However, in a realistic simulation, you can extract cross sections, 'on fly', in SteppingAction, with G4HadronicProcessStore. In Hadr03, see a corresponding section in Run::EndOfRun()