Skip to content

GitLab

  • Menu
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,842
    • Issues 1,842
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 88
    • Merge requests 88
  • 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
  • ParaView
  • ParaViewParaView
  • Issues
  • #18883

Closed
Open
Created Mar 19, 2019 by Mathieu Westphal@mwestphalMaintainer

Progress is not handling well for temporal filter

Progress is unreadable when using temporal filter in the Pipeline. Consider the following usecase:

  • Open FileSeries->Wavelet*.vti
  • RandomVectors, Apply
  • StreamTracer, 100 points, apply
  • PlotDataOverTime, Apply
  • the progress bar will go from 0 to 100 at least 4 times, on for each timesteps/stream tracer execution, without giving any sense of remaining execution time.
  • It actually is possible to see the PlotDataOverTime progress, but it is displayed very fast, after the stream tracer progress.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking