|Message: Re: Set TrackStatus Question||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)|
Neoh writes: > Thank you for the reply. > > [ I wrote: ] > > If you're really meaning to implement a hadronic "model", then you > > should inherit from G4HadronicInteraction, and use the "RegisterMe()" > > function to attach your model to the appropriate InelasticProcess when > > building your physics list. > > Yes, this is what I am currently doing. > > One last question. What would I expect if, for some reason, I didn't set > track status in the code (only add secondaries list)? Would it flag an > error/warning, or is there a default track status for each track? The default status is fAlive. If your hadronic model absorbs the primary (i.e., if it's an inelastic interaction), then you *must* set StopAndKill to conserve four-momentum, since the secondaries sum up to the original kinematics. The only time you would leave the status fAlive for an inelastic model is if the interaction failed. In that case, you initialize G4HadFinalState in your model with the track's input momentum, and the fAlive return tells tracking that nothing happened, and the particle should move on to the next interaction. If you're implementing a "quasi-elastic" model, then it is possile for the original projectile to be scattered and to remain in an fAlive state, but with a lower energy and different momentum direction, even though you have secondaries. In that case, you'll set fAlive, the new primary kinematics, and fill the secondaries list. Finally, a true _elastic_ model would always set fAlive, together with the changed kinematics. If you want the recoiling nucleus to be tracked, then you would put it onto the list of secondaries as a G4Ions instance. -- Mike