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 830
    • Issues 830
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 240
    • Merge requests 240
  • 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
  • #18092
Closed
Open
Issue created Jan 26, 2021 by Sebastien Jourdain@sebastien.jourdainDeveloper

vtkFlyingEdges3D not producing valid result while vtkContourFilter does on very thin slab

Contouring the attached file for a scalar=1 don't produce the same result.

The vtkFlyingEdges3D seems to be connecting all the points to a virtual point in the origin of the image data. Such connectivity is wrong and does not appear when the filtering is done with vtkContourFilter.

thin-slab.vti

Screen_Shot_2021-01-26_at_15.14.58

Screen_Shot_2021-01-26_at_15.15.05

Assignee
Assign to
Time tracking