|Message: Re: BooleanProcessor - Too many edges problem||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)|
Indeed, as the Release Notes say, we "improved" boolean processing in 9.4. Seems it improved it for our test cases but made things worse for you!!
First, let me say that this has nothing to do with tracking - tracking will be OK. You can check that by viewing your volume with the RayTracerX driver, which uses Geant4 tracking algorithms.
Boolean processing is used solely in creating polyhedral representations for the purposes of visualisation (for drivers other than RayTracer). It's a tricky computational problem, especially if components share or closely share some surfaces; computer rounding errors are tricky to deal with. One thing you can do is to make sure that subtracting solids "stick out" so avoiding shared surfaces. You can often improve things just by moving components around by a few micrometres.
The message comes after boolean processing and during the conversion to a HepPolyhedron (G4Polyhedron). Curiously, it doesn't flag an error, so presumably the HepPolyhedron will still be a valid one, as indeed you have discovered, possibly with some bits missing(!). If you're confident that your solid is OK, you could simply go into BooleanProcessor.cc, ll.1949-1952 and comment out the write statement.
We need to try and fix this. Could you please package up a snippet of your code so that we can try to reproduce the problem. Quick results not guaranteed!
|Inline Depth:||Outline Depth:||Add message:|