|Message: Absolute replica number||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)|
Hello, I would need to compute the absolute replica number of the touchable in which my currently tracked particle is (inside a G4VSensitiveDetector::ProcessHits implementation). For example, suppose that I have a G4PVReplica describing 10 replicated volumes; its logical mother is then placed as a physical in N different locations, with N possibly varying in different geometry versions. With the touchable history I can get the replica number from 0 to 9, but how can I know how many physical mothers are there at runtime? I don't really care about their exact order, so for me it is sufficient to know that my touchable is the i-th replica of the j-th G4PVReplica, so that I can compute the "absolute replica number" as i+j*10.
I tried browsing the G4PhysicalVolumeStore but it seems that only one G4PVReplica is there (as far as I understand, the store contains N copies of the physical mother but only one replicated volume). I could browse the mothers to solve this specific case, but I would need a more general and robust solution to possibly account for "more nested" cases.
Is it feasible? Can anyone give me some hint? Thanks.
|Inline Depth:||Outline Depth:||Add message:|