|Message: Re: Want to Tag Each Particle With the First Surface Material It Encounters||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)|
Hi, G4Track does not have such information by default, so that you need to develop some code for it. G4VUserTrackInfromation will be used for this purpose. The concrete class of G4VUserTrackInformation can be attached to G4Track object. And, users can access it via G4Track object. You will find several examples in Geant4 examples. I think the examples/extended/field/field04 may be a good reference. The overview of developing code is as follows, (1) Define your TrackInformation class i.e. F04UserTrackInformation You may define a flag to identify the first material. (2) Define your TrackingAction class i.e. F04TrackingAction You will instantiate TrackInformation object and attach it to Track object. (3) Define your SteppingAction class i.e. F04SteppingAction You will write codes in it for changing the flag according to the volume material etc. (4) TrackingAction and SteppingAction should be registered to RunManager. i.e. field04.cc (runManager->SetUserAction( ... )) (5) Of course, you need to modify your scoring code to check your TrackInformation. Best regards, Tsukasa