Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,842
    • Issues 1,842
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 89
    • Merge requests 89
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaView
  • ParaViewParaView
  • Issues
  • #17500

Closed
Open
Created Jun 09, 2017 by Andrew Bauer@acbauerDeveloper

Connectivity filter does not work correctly in parallel

Steps to reproduce:

  1. Start pvserver with 8 processes and connect the GUI client
  2. Create Wavelet source with default values
  3. Create Contour filter with default values
  4. Create Connectivity filter
  5. Pseudo-color by Id and see that things don't match up

There are actually less id values in parallel than in serial so what's likely happening is that each process is starting from id 0 and independently creating their own ids without any global information merge.

Closed by !2077 (merged).

Edited Dec 06, 2017 by Cory Quammen
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking