Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ParaView
ParaView
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,758
    • Issues 1,758
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 68
    • Merge Requests 68
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaView
  • ParaViewParaView
  • Issues
  • #3436

Closed
Open
Opened Jun 22, 2006 by Kitware Robot@kwrobotOwner

SNL: D3 strips global Ids

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


When running D3 on an input with global ids in it (for example read from an Exodus file), the global point and cell ids are stripped.

D3 should have the opposite behavior. It should keep global ids if they are there or provide the global ids that it generates if they are not in the input.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: paraview/paraview#3436