Skip to content
GitLab
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 831
    • Issues 831
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 233
    • Merge requests 233
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTKVTK
  • VTKVTK
  • Issues
  • #17260
Closed
Open
Issue created Mar 09, 2018 by Maik Froechtenicht@ifmfrContributor

vtkmPolyDataNormals does not respect AutoOrientNormalsOn()

Using vtkmPolyDataNormals with AutoOrientNormalsOn() (https://www.vtk.org/doc/nightly/html/classvtkmPolyDataNormals.html) does not affect the output of the filter, which leads to wrong results. As far as I understand is SurfaceNormals, which is called, not able to handle the requested AutoOrientNormalsOn setting. As a workaround, the flag should be added in vtkmPolyDataNormals.cxx to the existing list of exceptions that makes sure to fallback to the serial vtkPolyDataNormals.

Edited Apr 20, 2018 by Maik Froechtenicht
Assignee
Assign to
Time tracking