|Message: Re: Lifetime of touchables||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)|
To address the original question, about the lifetime of touchables: It is possible to get a smart pointer (handle) to a touchable using a very similar method: G4TouchableHandle touchableHandle = aStep->GetPreStepPoint()->GetTouchableHandle(); When you get and keep an object of this type (handle), it acts as an anchor which maintains in memory not only the touchable to which it points, but also the necessary objects of which it is created. One important caveat: for different tracks that encounter the same volume a different touchable will be created by the Navigator, so you will get a different handle which will point to a different touchable that contains the same information. There are some important consequences: - you cannot do a simple comparison of pointers (or handles) to identify whether you are referring to the same touchable volume. A deep comparison is required to identify the equality of the touchables to which the handles point; - the amount of memory required to hold these smart pointers (handles) is likely significant. [ I mention that a different/revised version of the navigator which uses a single touchable for all tracks is under development by a colleague, who has created already a prototype implementation. Developments regarding its potential integration are under discussion. I note that this was *not* included in the last 10.1-beta development release. ] - John Apostolakis On Aug 2, 2014, at 12:28 AM, "Michael H. Kelsey" <firstname.lastname@example.org> wrote: > > *** Discussion title: Geometry > > On Fri, 01 Aug 2014 13:32:10 GMT, Nicola Mori wrote: > >> Hi, to identify volumes where hits happen I'm using the address of the >> corresponding touchable: >> >> const G4VTouchable *touchable = aStep->GetPreStepPoint()->GetTouchable(); >> >> In my hit object I record this address during >> G4VSensitiveDetector::ProcessHits, but in my EndOfEventAction() it seems >> that the memory location pointed by this pointer contains invalid data. > > You can't do that. Steps and Tracks only have lifetime while they are > actively involved. What's more, those objects, and some of their > constituents, are allocated from fixed memory pools using the > "G4Allocator" method, with the result that a cached address might point > to a valid object of the type you care about, but have completely > different content. > > What you need to do in your ProcessHits() class, is make use of that > Touchable to extract whatever information (data) you actually plan to > store, rather than trying to defer that activity until later. > > -- Michael Kelsey > > ------------------------------------------------------------- > Visit this GEANT4 at hypernews.slac.stanford.edu message (to reply or unsubscribe) at: > http://hypernews.slac.stanford.edu/HyperNews/geant4/get/geometry/1362/1.html
|Inline Depth:||Outline Depth:||Add message:|