Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 732
    • Issues 732
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 202
    • Merge requests 202
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTKVTK
  • Issues
  • #18422

Closed
Open
Created Dec 29, 2021 by aveek-brahmachari@aveek-brahmachari

clipping a polydata using the implicit of another polydata via vtkClipPolyData leads to a big hole on the cut side.

vtkSmartPointer<vtkPolyData> clipMesh (const vtkSmartPointer<vtkPolyData> &mesh1, const vtkSmartPointer<vtkPolyData> &mesh2) {

	vtkNew<vtkImplicitPolyDataDistance> implicit_distance_2;
	implicit_distance_2->SetInput(mesh2);

	vtkNew<vtkClipPolyData> clip;
	clip->SetInputData(mesh1);
	clip->SetClipFunction(implicit_distance_2);
	clip->Update();

	return clip->GetOutput();
}

I dont understand why the mesh returned has a no surface on the clipped side. Please let me know how I can improve this function to have a water tight mesh.

Edited Dec 30, 2021 by Mathieu Westphal
Assignee
Assign to
Time tracking