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
  • #20211
Closed
Open
Issue created Sep 15, 2020 by Boonthanome Nouanesengsy@boonthDeveloper

Cannot dynamically change Catalyst Channel name

Currently, when a file written with Catalyst is loaded into Paraview, the Catalyst Channel's name is shown in the Pipeline Browser in the upper left. The default channel name is "input". I attempted to have our Catalyst adaptor give a more descriptive name. I added a new Catalyst input, and set the name of the input to the name of the problem being run.

The issue is that with Catalyst python scripts, you need to know the name of the Catalyst Channel a priori. This is due to the following lines of a basic Catalyst script:

  freqs = {'input': [outputfrequency]}
  coprocessor.SetUpdateFrequencies(freqs)

These lines are executed when Catalyst is initialized, so I don't see a way I can dynamically set the Catalyst channel name.

I've found two workarounds for this. The first one is to create an additional Catalyst input, name it what you want, and set the grid to be the same grid as the "input" channel. This will change the Catalyst channel name of the final output files.

The second workaround is when you have the data in the Catalyst script, you manually change the field data __CatalystChannel__ to whatever you would like.

Is there some way to do this more properly, that I am missing? Both of these workarounds are hacky, and I'd rather not use them if there's another way. Also, I'm wondering if the new Catalyst API will deal with this situation better.

@patchett2002 @cory.quammen @utkarsh.ayachit

Edited Oct 20, 2020 by Boonthanome Nouanesengsy
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking