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,960
    • Issues 1,960
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 96
    • Merge requests 96
  • 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

Gitlab will be updated February 2nd, between 8am and 9am EST (UTC-5). Gitlab will be offline during that time.

  • ParaViewParaView
  • ParaViewParaView
  • Issues
  • #2708
Closed
Open
Issue created Jan 09, 2006 by Kitware Robot@kwrobotOwner

SNL: Filters screw up Global Ids for D3

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


D3 has a feature where it can accept a point data array in which each entry has a unique id across all processes (unless the point is duplicated on another process in which case the ids will be consistent). D3 uses this array to collapse duplicated points once the data is redistributed. Currently, the Exodus reader can provide this global id array and greatly speed D3's performance.

The problem occurs when you first run the data through a filter that invalidates the meaning of the global id array. For example, the glyph filter will place a glyph on points, and each point in the glyph inherits the same global id from the original point the glyph was placed. When the glyphs are run through D3, D3 collapse all the points in each glyph into a single point, making all the polygons degenerate.

It is important that this behavior be corrected because, when parallel volume rendering is on, everything is run through D3. Thus, when parallel rendering is on, glyphs originating from Exodus files often dissapear. Tubes and isosurfaces are two other examples with similar results.

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