Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 833
    • Issues 833
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 241
    • Merge requests 241
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTKVTK
  • VTKVTK
  • Issues
  • #17065
Closed
Open
Issue created Jun 13, 2017 by Armin Wehrfritz@awehrfritzContributor

Feature request: Volume rendering for (non-uniform) rectilinear grids

Currently, volume rendering for (non-uniform) rectilinear grids is not available (using the binary installer: ParaView-5.4.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz).

In order to do a volume rendering of such a dataset, it has to be explicitly converted to an unstructured dataset. This is however inefficient, as 1) the memory usage increases significantly and 2) the volume rendering for unstructured dataset is magnitudes slower than for uniform rectilinear (i.e. image) dataset.

Thus this feature request for an efficient and fast volume rendering of non-uniform rectilinear grids.

Alternatively, ParaView could offer a volume rendering representation for non-uniform rectilinear and structured grids in general by internally converting the dataset to an unstructured grid. The option could be named "Volume (unstructured)" or something the like. This would at least give the user a hint that for the respective dataset only the unstructured volume rendering option is available, though with a significant performance hit.

This has been requested and discussed in a few mailing list conversations/ bug reports:

http://www.vtk.org/Bug/bug_relationship_graph.php?bug_id=2567

http://public.kitware.com/pipermail/vtkusers/2009-February/050457.html

http://public.kitware.com/pipermail/paraview/2013-October/029642.html

http://lists.mcs.anl.gov/pipermail/petsc-users/2015-April/025148.html

/label triage:feature area:rendering

@kmorel @berkgeveci @lisa-avila @aashish-chaudhary

Edited Jun 15, 2017 by Armin Wehrfritz
Assignee
Assign to
Time tracking