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
  • #18348
Closed
Open
Issue created Aug 02, 2018 by David@dhrDeveloper

Cinema/Catalyst bug: multiple calls to RegisterView result in duplicate Cinema databases

When the following steps are executed in-situ with Catalyst, the output is incorrect.

create pipeline create renderViewA showing pipeline create renderViewB showing pipeline (different visualization) RegisterView( renderViewA ) RegisterView( renderViewB )

Output for both Cinema databases will always be the output for renderViewB (the last RegisterView call)

Attached script demonstrates this for an in-situ run with Nyx.catalyst_clip_calc.py

@patchett2002 @dhr

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