KAHIBARO
8.6 Geometry Overlap Checking
Table of Contents
Detecting overlapping volumes
Geant4 requires a consistent, non overlapping geometry in order to transport particles correctly. If two physical volumes occupy the same region of space, or one volume extends slightly outside its mother volume, step limitation and navigation can fail, particles can get “stuck,” and energy deposition can be recorded in the wrong place. For this reason, you should routinely check new or modified geometries for overlaps.
Geant4 provides built in tools that test for overlaps numerically. They do not modify your geometry, but they probe it with points or rays and report suspicious regions.
The simplest way is to use the overlap checking options in G4PVPlacement and related classes when you construct volumes in C++. Almost every placement constructor has an optional boolean argument pMany and an integer argument pCheckOverlaps. When you set this flag to a positive value, Geant4 activates overlap checking for that placement. Internally, it generates random points on the surface of the solid and checks whether they are also inside other solids or outside the mother volume.
A typical placement call with overlap checking looks like:
auto physDetector = new G4PVPlacement(
rotation, // rotation
position, // translation
logicalDetector, // logical volume
"Detector", // name
logicalMother, // mother volume
false, // pMany
copyNumber, // copy number
true // check overlaps
);
The last argument true activates default overlap checking using a standard number of sample points. You can also pass an integer instead of a boolean in some constructors to control how many points are used. A larger number is slower but increases the chance of catching small overlaps.
When you run your application, overlap messages appear on the standard output or terminal. They typically report the volumes involved and the approximate location of the problem. If no messages appear during initialization, no overlaps were found with the chosen sampling.
Overlap checking can also be controlled with UI commands. If your geometry uses placements without the check flag, you can ask Geant4 to perform a general check, for example:
/geometry/test/recursion_start 1
/geometry/test/runor, in some versions:
/geometry/test/run 1000which tells the geometry system to fire a number of test rays through the setup and look for navigation problems which often indicate overlaps or gaps. The exact command set can vary slightly by version, so the Geant4 Application Developers Guide is the reference for these commands.
Visualization is another very effective way to detect overlaps. Using the visualization commands you can draw the full geometry, zoom in and rotate, and look for volumes that seem to “poke out” of their mothers or interpenetrate neighbors. Switching between solid and wireframe rendering and making some volumes transparent can help expose hidden overlaps. In some viewers, you can draw only selected volumes and inspect their boundaries carefully.
For very small overlaps, you can also ask Geant4 to compute the distance to boundaries for navigation and report suspicious values. However, for an absolute beginner, enabling overlap checking on placements and inspecting the log and visualization is usually sufficient.
Always enable overlap checking when you develop or modify geometry, at least once per change. Undetected overlaps can cause incorrect physics results even if the program runs without crashes.
Debugging geometry
When an overlap is reported or you suspect a geometry problem, the goal is to locate the exact volumes and parameters that cause it and then correct the dimensions or placements.
The first step is to carefully read the overlap messages in the terminal. Geant4 usually tells you which daughter volume and which mother volume are involved and provides an approximate test point where the overlap was found. Make a note of the volume names. Clear and consistent naming in your geometry code is extremely helpful here. If you have generic names like "boxLV" for many objects, debugging becomes much harder.
Once you know the suspicious volumes, revisit their definitions in your DetectorConstruction. Check the following aspects in the C++ code.
Verify the solid dimensions. Ensure that the half lengths or radii you specify actually fit inside the mother volume. Remember that classes such as G4Box and G4Tubs use half lengths and radii in their constructors. A common beginner mistake is to confuse full length and half length which can easily produce a small overlap with the world or neighboring volumes.
Verify the placement position. Look at the translation vector you pass to G4PVPlacement. Work out, on paper if needed, the expected minimum and maximum coordinates of the placed volume in the mother coordinate system. Compare those with the mother volume bounds. If the sum of the position and half lengths exceeds the mother size, you have an overlap or a protruding volume.
If rotations are involved, remember that the placement position is the center of the volume, expressed in the mother coordinate system, after rotation. In complex setups, it is sometimes easier to temporarily remove rotations or simplify placements to see which part causes the problem.
Next, use visualization to guide corrections. Draw the geometry and then selectively hide or show the problematic volumes. For example, draw only the mother and the child volumes that overlap, give them contrasting colors, and use transparency. Rotate and zoom until you can visually see the area where the overlap occurs. This often reveals whether the problem is due to an incorrect dimension or a misaligned translation.
If overlaps are very subtle, change the visualization to wireframe mode. Wireframe renders outlines instead of solid faces. In this mode, interpenetrating edges are easier to see.
You can also simplify the geometry temporarily. Comment out or conditionally disable complex surrounding structures, leaving only the volumes that might overlap. Once those are correct, reintroduce the rest progressively and keep overlap checking active at each step. This incremental approach makes it easier to isolate the origin of problems.
Sometimes, the overlap message may refer to a volume that comes from a Boolean solid. In that case, carefully review the union, subtraction, or intersection operation. Ensure that the translations and rotations of the component solids inside the Boolean construction are what you expect. Small mistakes in these internal offsets can create thin overlapping slivers that are difficult to notice.
For repeated geometries, such as replicas or parameterized volumes, check the replication parameters or the parameterization function. If a copy size or offset is miscomputed, copies can overlap each other or extend beyond their mother. Verify that the sum of all replica dimensions does not exceed the size of the container.
If your geometry is imported from external sources, such as GDML or CAD conversions, you might inherit overlaps from the original design. In those cases, you can still use Geant4’s overlap tools but may need to fix the source geometry or adjust scaling and positions in the import step.
Once you believe you have fixed the problem, recompile and rerun your application with overlap checking still enabled. Confirm that no new overlap messages appear and that the visualization looks correct. Only then is it safe to proceed with physics simulations.
Never ignore overlap warnings. Always identify the volumes, check their dimensions and placements, and confirm with visualization that the geometry is valid before trusting any simulation results.
Views: 9