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

too many renders

Steps (for linux):

  • start paraview as follows: env PARAVIEW_LOG_RENDERING_VERBOSITY=INFO ./bin/paraview -dr. This will cause ParaView to output information on terminal every time ParaView does a render.
  • Wavelet, Apply, Contour Apply
  • Now observe the terminal and click on Wavelet1 and then Contour1 and you'll notice each time the active source changes, a render is triggered.

That should not be necessary and causes the application to feel clunky when rendering large datasets.

Edited Apr 01, 2020 by Utkarsh Ayachit
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking