You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Issue while performing Intersection operation on triangulated solids. #9467
I am encountering an issue while performing the Intersection operation on triangulated solids.
For the attached dataset, the call to corefine_and_compute_intersection() fails in the attached prototype application. However, corefine_and_compute_union() and corefine_and_compute_difference() both complete successfully on the same dataset.
I have attached the dataset reproducing the issue and a small prototype application demonstrating the problem.
The issue appears to be specific to the intersection operation for this geometry. Could you please investigate whether this may be a robustness issue, limitation or a potential bug in the Boolean intersection implementation?
Any guidance or recommendations would be greatly appreciated.
Source Code
The dataset along with a small prototype application is attached.
Please note that your meshes are oriented in such a way that the volumes they bound are infinite.
My guess is that you want the finite volumes. Calling PMP::reverse_face_orientations() will fix that. Once orientation fixes, I could compute union, and the 2 differences. However the intersection contains some non-manifold edges and is not representable as 2-manifold.
You can workaround that using this example. The API is not that nice, but if you are adventurous enough you can try the function provided in #9363 that works directly on triangle soups.
Activity
sloriot commentedon May 7, 2026
Please note that your meshes are oriented in such a way that the volumes they bound are infinite.
My guess is that you want the finite volumes. Calling
PMP::reverse_face_orientations()will fix that. Once orientation fixes, I could compute union, and the 2 differences. However the intersection contains some non-manifold edges and is not representable as 2-manifold.You can workaround that using this example. The API is not that nice, but if you are adventurous enough you can try the function provided in #9363 that works directly on triangle soups.
kundansharma1947 commentedon May 9, 2026
Thanks Sebastien for providing the solution. It works now.