Skip to content
GitLab
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,961
    • Issues 1,961
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 97
    • Merge requests 97
  • 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
  • #18991
Closed
Open
Issue created May 01, 2019 by Boonthanome Nouanesengsy@boonthDeveloper

Merge Blocks filter creates incorrect output

If data that was created in Paraview 5.5.2 is loaded into Paraview 5.6.0, and the Merge Blocks filter is used, the results look incorrect. This seems to happen to point data. The cell data still looks correct.

If I load the data in Paraview 5.5.2 and use Merge Blocks, it looks right. Using the latest git master of Paraview also looks right.

I have included a screeenshot of what this looks like, and have attached the data used.

To reproduce, load the data in Paraview 5.6.0, and apply the Merge Blocks filter, and have it show point_density.

@patchett2002 @demarle

data.tar.gz mergeblocks

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