|Message: GetGlobalTime returns a constant value throughout event.||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)|
I am investigating sponataneous and neutron induced fissions using Geant4.9.5.p02 and have some queries regarding the response of certain time methods.
In my Stepping Action class file (modified from example rdecay02) I call: G4double gloTime = fTrack->GetGlobalTime() / second; G4double locTime = fTrack->GetLocalTime() / second;
The Local time acts as expected (time difference between current step and creation of track), however, the Global time is identical for all steps of all tracks generated in the same event. Furthermore, according to the G4 documentation GetGlobalTime() should return "the time since the event in which the track belongs is created", whereas it appears to increase with increasing event number.
I am interested in the time difference between the Spontaneous fission and any subsequent induced fissions, I had attempted to compare the Global Time for my primaries with their secondaries satisfying:
fTrack->GetCreatorProcess()->GetProcessName() == nFission
With the Global time remaining constant for an individual event this obviously would not work. As a work-around I presume I could use the local time of the primary particle immediately prior to the nFission process being called but I am unsure where/how I can access this information.
I would appreciate any suggestions people might have.
|Inline Depth:||Outline Depth:||Add message:|