|Message: Re: Relation between physical particles and G4Tracks||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)|
Dear Peter, thank you very much for your explanations. Just one thing, as I perhaps expressed it mistakable: >> So my question is: Is it correct, that a particle also creates a new >> G4Track for itself when creating new particles (e.g. a muon creating >> photons by scintillation seems to create the photons' G4Tracks as well >> as a new muon G4Track, having the same trackID, parentID,... as the >> original muon G4Track)? > > I am surprised that you are saying that the trackID has not also changed, or > the parentID? That should not be the case. You should be able to trace (if > you have saved G4Trajectories) the history of tracks from trackID to > parentId, and so on. In my simulation, I have one muon going through a scintillator. I added "cout"s in my TrackingAction::PreUserTrackingAction(const G4Track* aTrack) (-> G4cout << "TrackID " << aTrack->GetTrackID() << G4endl;G4cout << "ParentID " << aTrack->GetParentID() << G4endl;) and in my SteppingAction::UserSteppingAction(const G4Step* theStep) (-> cout << "StepNumber " << theTrack->GetCurrentStepNumber() << G4endl;). That should give me a list with the trackID of each G4Track followed by the stepnumbers of all G4Steps belonging to a G4Track. Is that correct? And I get something like this: TrackID 1 -> my muon ParentID 0 StepNumber 1 StepNumber 2 StepNumber 3 TrackID 73 -> one of the scintillation photons ParentID 1 StepNumber 1 StepNumber 2 TrackID 72 -> one of the scintillation photons ParentID 1 StepNumber 1 StepNumber 2 TrackID 71 -> one of the scintillation photons ParentID 1 StepNumber 1 StepNumber 2 . . . TrackID 2 -> one of the scintillation photons ParentID 1 StepNumber 1 StepNumber 2 TrackID 1 -> my muon again ParentID 0 StepNumber 4 TrackID 256 -> one of the scintillation photons ParentID 1 StepNumber 1 StepNumber 2 TrackID 255 -> one of the scintillation photons ParentID 1 StepNumber 1 StepNumber 2 TrackID 254 -> one of the scintillation photons ParentID 1 StepNumber 1 StepNumber 2 . . . TrackID 74 -> one of the scintillation photons ParentID 1 StepNumber 1 StepNumber 2 TrackID 1 -> my muon again ParentID 0 StepNumber 4 . . . This brings me to the conclusion, that the muon has several G4Tracks, which have all the same TrackID and ParentID (and therefore can be assigned to the muon) but different StepNumbers (so that the full trajectory of the muon has continuous StepNumbers). Is do you agree? Because I need to know if my conclusion is correct, as my logic for assigning the G4Tracks ti the particles is based on the fact, that the TrackIDs/ParentIDs repeat. Best regards, Erik
|Inline Depth:||Outline Depth:||Add message:|