|Message: Re: daughter volumes not sensitive but should be pointed to?||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)|
Let me confirm again that a SD pointer do NOT propagate to the daughter volumes. This restriction came from the case where absorber layers (they are not sensitive) are dipped in liquid Argon calorimeter (liquid Argon is sensitive to collect all energy deposition in it). On the other hand, it is perfectly allowed to set the same SD object to both the mother and the daughter volumes. In this case, ProcessHits() method of your SD will be invoked with a G4Step which has a touchable recording all the geometry hierarchy from the immediate PV (level 0) to the top (world volume). Please note that it is always the case that a SD object assigned to the immediate PV (level 0) is invoked, and any SD objects that might be assigned to (grand)mother volumes are not invoked. In other words, there can NOT be any daughter volume below level 0 for touchable that is provided along ProcessHits() method. > It is still true that when a daughter volume's boundary > is crossed the SD calls ProcessHits() for the parent volume. I see > that in the log output. But within ProcessHits() it seems I loose > the information about any daughter volumes, unless I inspect by > looking at the hit position and infer the deepest volume at > that point by brute force inspection. Here I do not understand what you meant. Even if a step is limited by the daughter volume's bounday, the step belongs to that daughter volume and thus the SD associated to the daughter volume is invoked. > I will instead probably take > the easy route of simply making all the daughter volumes sensitive > as needed, creating and maintaining of course more hit collections, > which is a slight pain but not too burdensome. As I wrote above, you can assign the same SD object to both mother and daughter volumes. Then you have only one hits collection.
|Inline Depth:||Outline Depth:||Add message:|