|Message: Re: Incorporation of deuteron break up model||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)|
Chapter 3.5 (Hadronic Physics) of the GEANT4 Toolkit Developers Guide should have what you need. If you find that it is insufficient, *please* post specific questions here. Not only can the Hadronics working group members provide assistance, your questions can also help us to identify needed improvements to the documentation.
The hadronic framework is built as a "process-model" hierarchy. The G4HadronicProcess.hh base class inherits from G4VProcess, and specific subclasses of it (for elastic, inelastic, fission, whatever) are what get registered into your physics list.
Each G4HadronicProcess then has one or more _models_ registered within it. These models are what actually implement a particular kind of interaction (in your case, deuteron breakup). Models inherit from G4HadronicInteraction, and get called from the process as needed.
For your situation, you would write a subclass of G4HadronicInteraction, and implement the ApplyYourself() and IsApplicable() member functions. Obviously, you can write as many supporting member functions for your model as you might need, private data members, etc. Once written, you would register your model into the existing G4HadronInelasticProcess in your physics list.
|Inline Depth:||Outline Depth:||Add message:|