|Message: Re: Howto make G4Track information persistent?||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)|
The example for dealing with trajectories at the URL above is very useful. However, like other examples I've seen for customizing track handling, it apparently doesn't expand upon the "trajectory point" concept. I can imagine that one might want to carry additional information in the "point" such as time and energy, or perhaps even generalize the concept of "point" to include "line segment" with information smilar to that in the step. Is there an example somewhere of how to do this (correctly!)? Couldn't one simply create a G4TrajectoryPoint class constructor that might, e.g. use aTrack->GetStep() where Asai's example uses aTrack->GetPosition()? I mean something like "new G4TrajectoryPoint(aTrack->GetStep())" where the constructor extracts whatever information from the step that is of interest, and hides it in the G4TrajectoryPoint class along with the location vector. I guess I don't mind doing this myself if it's a sensible way to handle additional information about a trajectory. However, not finding examples of this appraoch, I'm suspicious that perhaps I'm missing something more fundamental. Is there another way to handle the generalization of the trajectory to something other than a set of points in space, or is this just something that isn't of interest to most people, and so isn't on the radar screen? -Thanks.
|Inline Depth:||Outline Depth:||Add message:|