Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intersection of meshes gives sometimes an empty mesh #43

Open
mauigna06 opened this issue Apr 21, 2021 · 0 comments
Open

Intersection of meshes gives sometimes an empty mesh #43

mauigna06 opened this issue Apr 21, 2021 · 0 comments
Labels

Comments

@mauigna06
Copy link

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):

111072265-8bd87600-84b8-11eb-8087-6cdee7cd40bc
108536826-a8b7ca00-72bb-11eb-9ca1-a4a7703f7ae1

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants