|Message: Re: G4AssemblyVolumes with G4Regions||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)|
Thanks for the response!
I understand. Out of the options you provide the first two would not be very practical in my current use case since the parent volume is considerably more than I would like to include in this region and a containing volume would require a pretty complex set of boolean solids to avoid overlapping with surrounding geometry (that's why I'm using an assembly volume in the first place).
The third option of looping over each constituent volume would be fine and I did look at implementing this approach already. However, G4AssemblyVolume doesn't provide a method to iterate over the constituent volumes themselves which I would need. The method `GetVolumesIterator()` returns an iterator to the placed volumes, which is only meaningful once the assembly has had `MakeImprint` called. Since there is not a `GetLogicalVolumeIterator()` method (presumably because this would expose the G4AssemblyTriplet class ?), I think your final suggestion of adding a set of helper methods to G4AssemblyVolume would be the nicest. Of course the assembly volume itself wouldn't need to be a RootLogicalVolume, but instead each constituent volume could be added to the region as a RootLogicalVolume as part of implementation of the new helper methods.
Thanks again for your response,