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 740
    • Issues 740
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 196
    • Merge requests 196
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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
  • VTK
  • VTKVTK
  • Issues
  • #3115
Closed
Open
Created Apr 09, 2006 by Kitware Robot@kwrobotOwner

vtkPolyDataConnectivityFilter treats seeded regions as one

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


I think I found a bug in vtkPolyDataConnectivityFilter, or at least misleading documentation.

The Documentation for mode 4 says "4) extract all regions sharing specified cell ids;" To me this means that the list of seed IDs will be used to seed different regions. GetNumberOfExtractedRegions should give me the number of seeds, and the regions should be colored differently if SetColorRegions is on. This is not what happens. Instead GetNumberOfExtractedRegions returns 1, and all the regions are given the same region number.

After looking at Graphics/vtkPolyDataConnectivityFilter.cxx I see the comment on line 202, "regions have been seeded, everything considered in same region" So I think it's the documentation that is wrong, for the simple reason that it's easier to fix. A second connectivity filter with SetExtractionModeToAllRegions will get what I want.

I think a solution would be a line in the documentation that seeded regions will all be considered to have the same ID but a seccond connectivity filter can then add the abilities of extract all regions.

Assignee
Assign to
Time tracking