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
  • #19117
Closed
Open
Issue created Jun 21, 2019 by W. Alan Scott@wascottMaintainer

CGNS bad in parallel with the D3 filter

CGNS data is not being handled properly with the D3 filter in parallel. Here is how to replicate:

  • Master (v5.6.1-1676-gc5bc2677), remote server (I am using 16 ranks), Linux.
  • Open sparc.cgns.4. Ask me for this dataset if needed. Default variables and blocks. Ignore FlowSolutionPointers on. Apply.
  • D3. Apply. (This should be surface.)

Notice there are holes in the inside of the curve. D3 appears to be drawing triangles wrong.

This is not holding anything up, but seems important since it is CGNS.

This is a Watney bug.

Edited Nov 06, 2019 by W. Alan Scott
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking