Intersection of meshes gives sometimes an empty mesh

[mauigna06]

Hi Ronald. Thank you very much for your work. With our opensource free Slicer module BoneReconstructionPlanner virtual surgical planning of mandibular reconstruction using fibula is possible. But using your library we are able to take the plan to the operating room with patient-specific surgical guides.

Here are some examples of what we achieved using your library (already used on clinical cases):

Right now we are trying to get the intersection of fibula bone pieces but the result is an empty mesh when it shouldn't be that way.

Here are meshes to replicate this behaviour:
Meshes.zip

The operations that fail are:
"Fibula Segment 0A-0B.vtk" intersection "Fibula Segment 1A-1B.vtk"
"Fibula Segment 1A-1B.vtk" intersection "Fibula Segment 2A-2B.vtk"

Hope you can help. Thank you again for this great library

[zippy84]

I know that this bug is very old, but now I have a first approach to get this work. I have been working on a simple algorithm to align nearly equal points. The code can be found in https://github.com/zippy84/vtkbool/blob/dev/dev/test2.py. Currently it is implemented in Python. When it has been sufficiently tested, I will integrate it into vtkbool. The class should eliminate the need of a "small random translation", mentioned in #81.

Here is a screenshot:

The result can be downloaded here: union.zip

[mauigna06]

Ok Ronald :)
Great work
Thanks a lot!

[mauigna06]

https://github.com/zippy84/vtkbool/blob/dev/dev/test2.py

Hi Ronald,

The fix did not work, I'll provide more info in the next week :)

[zippy84]

@mauigna06 It's just a prototype.