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 99
    • Merge requests 99
  • 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
  • #13274
Closed
Open
Issue created Jun 27, 2012 by Kitware Robot@kwrobotOwner

Xdmf Reader mixup on GeometryType='ORIGIN_DXDYDZ'

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


The XDMF reader appears to have a bug with grids with a GeometryType of "ORIGIN_DXDYDZ". The documentation at http://www.xdmf.org/index.php/XDMF_Model_and_Format states:

ORIGIN_DXDYDZ - Six Values : Ox,Oy,Oz + Dx,Dy,Dz

This would imply that the Origin DataItem's three values would be, in order: "X, Y, Z". VisIt interprets these coordinates in this order as well. ParaView, on the other hand, interprets the coordinates as "Z, Y, X".

This becomes most noticeable when you have a larger grid made up of sub-grids, each with a GeometryType of ORIGIN_DXDYDZ, and they line up along the wrong axis.

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