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,962
    • Issues 1,962
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 98
    • Merge requests 98
  • 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
  • #19794
Closed
Open
Issue created Mar 25, 2020 by Utkarsh Ayachit@utkarsh.ayachit⛰Contributor

volume mapper: doesn't respect array changes

Steps:

  • disk_out_ref.ex2, all variables, Apply
  • Adaptive Resample to Image, Nnumber of image: 4, Apply -- notice: we're coloring by vtkBlockColors.
  • Switch representation to Volume. You get errors
ERROR: In /home/utkarsh/Kitware/ParaView3/ParaView/VTK/Rendering/VolumeOpenGL2/vtkSmartVolumeMapper.cxx, line 271
vtkSmartVolumeMapper (0x558d7e7bccd0): Could not find the requested vtkDataArray! 5, 1, -1, vtkBlockColors

This is reasonable. vtkBlockColors indeed is missing for the volume representation. However, changing the coloring array to Temp, for example, doesn't change the error message. The only way around is to color the view, create a new one and color by Temp before changing the representation type to Volume

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