|Message: Re: Help desperately needed on the tessellated GDML volumes.||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)|
Yes, tessellated solid is processed by G4 in an extremely inefficient way.
It's a known problem. It seems the developers does not want to improve the efficiency of tessellated solid. You must do it by your self.
1) Optimize tessellated solid by reduce surface triangles. Some edge-cut algorithm can help you.
2) Use step model directly. You can use OCC to load the step file, wrap the CAD entity by G4VSolid -- just provide G4 information such as in/out and distance to entity surface. As far as I know, OCC does provide functions to above algorithm.
3) use other method to describe the detector and re-implemente G4Navigator I am try to use levelset as detector description. In principle, this method should be very efficient.