|Message: Re: Turn off overlap warning||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)|
Hi Kareem, > I would like to request a new feature for the next version of GEANT. I > would like to be able to turn off the warning when I check for > overlapping volumes. Right now, I can call > G4PVPlacement::CheckOverlaps() and get a "true" return value, but > there's no way to turn off the warning, even with verbosity set to 0. A > simple "if( verbose )" flag would work great. I tried to attach an > appropriately-modified file, but for some reason I'm not allowed to > upload files. I'll post the file as a comment to this thread. > > I am trying to determine the smallest bounding volume of any arbitrary > shape, and as such I purposely create volumes that are too small. This > results in many warning messages, which alarms other people who use the > simulation. the method CheckOverlaps() is meant to inform in detail about overlaps in the geometry for debugging purposes. By running it in non-verbose mode it will just flag when an overlap is found and run silently otherwise. We could introduce an additional level of verbosity to satisfy your needs, however, let me point out that the technique you use for determining the smallest bounding box is certainly not efficient. It would be more appropriate to compute (with some coding) the extent of the solid, perhaps by adopting the CalculateExtent() method that each one of the shapes already provides... Cheers, Gabriele
|Inline Depth:||Outline Depth:||Add message:|