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

vmtksurfaceendclipper does not work consistently #169

Open
kayarre opened this issue Sep 27, 2016 · 2 comments
Open

vmtksurfaceendclipper does not work consistently #169

kayarre opened this issue Sep 27, 2016 · 2 comments

Comments

@kayarre
Copy link
Contributor

kayarre commented Sep 27, 2016

when running the command:
vmtk vmtksurfaceendclipper -ifile simplification_fixed.ply -ofile simplification_fixed_clip.ply

I am also selecting points near the end of the model, I don't know if that effects things.

The command execute properly, but there is a unclipped triangle:
screenshot from 2016-09-27 15-21-43

I run the same command selecting points on a different branch and have different results.

vmtk vmtksurfaceendclipper -ifile simplification_fixed.ply -ofile simplification_fixed_clip.ply

Done executing vmtksurfaceendclipper.
Writing PLY surface file.
ERROR: In /home/ksansom/build/vmtk/build/VTK/IO/PLY/vtkPLYWriter.cxx, line 122
vtkPLYWriter (0x49b3660): No data to write!
Output vmtksurfaceendclipper members:
Id = 0
Surface = vtkPolyData

@kayarre
Copy link
Contributor Author

kayarre commented Oct 6, 2016

It appears there are two separate issues, The first is that the normal estimation routine gets an inverted normal sometimes and can't continue when the main body of the mesh has been clipped. The second issue is the one I listed above where the triangles are not fully clipped.

@kayarre kayarre changed the title vmtksurfaceendclipper does no work consistently vmtksurfaceendclipper does not work consistently Oct 9, 2016
@kayarre
Copy link
Contributor Author

kayarre commented Oct 18, 2017

After further investigation I have been able to discern that the normal estimation filter often inverts the normal which leads to clipping the surface that you want to keep.

the second issue i believe is due to clipping an anisotropic mesh, meaning the seamfilter consistently creates a small triangle that does not lie on the implicit plane. I was able to reduce the issue by remeshing the cells in the neighborhood of the implicit plane.

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

No branches or pull requests

1 participant