Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,993
    • Issues 1,993
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 86
    • Merge requests 86
  • 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
  • ParaViewParaView
  • ParaViewParaView
  • Issues
  • #20379
Closed
Open
Issue created Dec 10, 2020 by Andrew Bauer@acbauerDeveloper

Pass Arrays filter a bit weird with vtkGhostType

The Pass Arrays filter has weird behavior with vtkGhostType arrays. If the input dataset has a vtkGhostType array and the user unchecks the vtkGhostType array for the Pass Arrays filter, that array is still in the output. See the attached pvsm file. passarrays_vtkghosttype.pvsm

Note that this happens with other dataset types as well. The original issue was found with an spcth dataset from a multiblock of rectilinear grids. I can't share that dataset though but it appears to happen with more than just vtkUniformGrid datasets.

I know there is the Remove Ghost Information filter which should be used here but am just wondering what is the proper behavior here. I think the new behavior is to allow the user full control of such "special" arrays like vtkGhostType and such. My guess is that this filter should still show the vtkGhostType array (and other special arrays) and allow them to be removed but would probably be fine with not showing special arrays. I'm more just reporting this behavior because of the incorrect behavior to try and get a fix for it.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking