Re: Final step information for parent particle

Help: Forums, postings and threads

Forums, postings and threads

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.

Layout of the posting thread(s)

The posting threads can be shown with/without the text of the postings ("Inline depth"). In addition the depth of the thread can be controlled ("Outline depth"). For both cases several values are provided, which can be toggled. Note that the displayed values are those, which can be chosen, they do not correspond to the actual display status of the thread(s).

Add message

Add a new posting thread to this Forum

Show subscribers

Click "Show subscribers" to get the List of all subscribers, who receive e-mail from postings to this Forum, if they have not explictly unsubscribed from a posting thread. This includes:

Subscribers to the forum
Explicit subscribers to the posting or any of its ancestors
The author of the posting (if he has not unsubscribed)
The authors of any ancestor posting (if they have not unsubscribed)

Some browsers display old pages from the cache

Some browsers (e.g. Firefox) display a page from the cache even though the page has been updated. As a result, one may not get the latest messages in the forum's outline or the logon ID of the previous session appears on the upper right corner. If one suspects that he or she does not get the latest content of a page, try clearing up the personal data from the browser's cache as the following:

Tools -> Clear Private Data -> Clear Private Data (from browser Firefox)

Tools -> Delete Private Data (from browser Opera)

then reflesh the current page to get the latest content.

Details on "Inline depth" and "Outline depth"

Threads and the follow-up messages are numbered. There is one line per posting, normally starting with the posting number. The URLs of a posting and its responses reflect the depth of the follow-up postings. Watch the URLs to see how this is done. Depending on the chosen display options, the thread-display may be incomplete; the number of messages at the next level is, however, displayed, e.g. "…3 message(s)". You may not see all contributors unless you choose "All".

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.

Argument Default value Alternative Comment

1 0 1 no text / full text of posting

2 1 All text for level 1 only / text for All postings

Argument	Default value	Alternative		Comment
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.

Argument Default value Alternative Comment

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)

Argument	Default value	Alternative	Comment
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 Tue, 19 May 2009 10:12:55 GMT, Cristian Bungau wrote:

> The only information I need in my code is to
> know if the muons which I detect have been produced by pion decay at
> rest or in flight. That's why I mentioned I had to access the
> information on parent energy or momentum.

OK, The kinetic energy of a G4Track is available from track->GetKineticEnergy(). This has the usual floating-point disease that comparisons to 0.0 may not work. Perhaps you can use track->IsBelowThreshold(). Perhaps you can use track->GetTrackStatus() -- you'll have to do this in UserSteppingAction(), checking for fStopButAlive. Note that UserSteppingAction() does not get called after the final step (when the track has been killed); PostUserTrackingAction() does (but status will be fStopAndKill there, having forgotten whether it was at rest or not).

I suspect track->IsBelowThreshold() is the best, but I have never used it.

> If there is no simple way of doing this, I guess the tip in
> http://geant4.slac.stanford.edu/Tips/event/1.html should probably work?

Adding a G4VUserTrackInformation is neither needed nor appropriate. In particular, to access it you need a G4Track pointer, and that requires the vector<G4Track*> I mentioned before. Given that vector, you can get the kinetic energy directly from the G4Track, or the status.

> Or using the GimmeSecondaries() method to pass the information from
> parent track to the daughter particles would be best ?

Your code would need to be clairvoyant to do that, because you must call that while tracking the parent (in PostUserTrackingAction). You cannot just save the last track's status, as the order of tracks being tracked has no useful ordering (other than parents are tracked before their secondaries). So you need a vector, and must search the vector for the correct parent track. If your events have many tracks (> 30, say), perhaps use a std::map<G4int,G4Track*> mapping track ID to track pointer, avoiding the linear search of a large vector.

NOTE: don't use G4Track in the vector or map, as you may not be able to easily distinguish an unknown track ID (default G4Track) from a stopped track; a null pointer is easy to detect.

I suggest setting up the vector<G4Track*> in PostUserTrackingAction(), clearing it in BeginOfEventAction() (and deleting the tracks). When your PreUserTrackingAction() finds it has a muon, use track->GetParentID() to get the ID of the parent, and search the vector (or map) for the track with trk->GetTrackID() equal to it, then call trk->GetKineticEnergy() and you'll have the kinetic energy of the parent. Or use trk->IsBelowThreshold().