|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)|
Nicola Mori writes: > Thans Michael for your reply. I'm writing a simulation software that can > handle arbitrary geometries so I'd need to identify an arbitrary > touchable in a unique way in order to save its hits on te output file. I > found that replica and copy numbers may not be sufficient with deeply > nested geometries, or that a computation of a unique ID for a touchable > would require traversing the full geometry tree and potentially be time > and memory consuming. Is there a smart way to identify a touchable and > recognize it in ProcessEvents across different events? Thanks. Pedro Arce developed a set of C++ tools for the GAMOS experiment, which can do this sort of thing. I adapted it to CDMS and have been pleased with how it works. See http://hypernews.slac.stanford.edu:5090/HyperNews/geant4/get/geometry/1357/1/1.html You can give the tool a string with the full nested hierarchy of volumes, and it can return the matching PV in the form of a G4VTouchable. You can also give it a valid touchable and it will construct the "long name" string for you. That might be an option for you to do what you need. -- Mike