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,961
    • Issues 1,961
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 99
    • Merge requests 99
  • 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
  • #20738
Closed
Open
Issue created May 26, 2021 by Utkarsh Ayachit@utkarsh.ayachit⛰Contributor

ParaView Catalyst blueprint: add support for `params` in execute

Extend the ParaView-Catalyst blueprint as follows:

protocol: 'execute'

params: pass parameters that can change per execute invocation.

  • params: (optional) a 'list' of strings.

Next, add a new function in the paraview.catalyst module that Catalyst scripts can use to access these params. Possible names:

  • paraview.catalyst.get_params(), or more explicitly
  • paraview.catalyst.get_execute_params()

for details on how to implement this, see !4869 (merged).

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