Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improvements to VTKHDF format I/O #3582

Open
4 tasks
chrisrichardson opened this issue Dec 30, 2024 · 1 comment
Open
4 tasks

Improvements to VTKHDF format I/O #3582

chrisrichardson opened this issue Dec 30, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@chrisrichardson
Copy link
Contributor

chrisrichardson commented Dec 30, 2024

Various features can be added to the VTKHDF I/O format:

  • Handling of input markers for cell and boundary data
  • Support of higher-order geometry
  • Paraview compatibility
  • Function output
  • Paraview does not currently support the vtkLagrangePyramid type, which is needed for higher-order visualisation of meshes containing pyramids. See https://gitlab.kitware.com/paraview/paraview/-/issues/22840
  • Paraview fails to recognise 2D data for geometry for 2D meshes (probably needs padding to 3D).
@chrisrichardson chrisrichardson added the enhancement New feature or request label Dec 30, 2024
@jorgensd
Copy link
Member

  • Paraview fails to recognise 2D data for geometry for 2D meshes (probably needs padding to 3D).

Ref the Python implementation we had; I stored a variable gdim which is then used to prune the input coordinates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants