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 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
  • #16997
Closed
Open
Issue created Oct 29, 2016 by Elias Pipping@pipping

Poly Line Source field Points broken in animation view

If I add a Line source, the following information is made available in the animation view:

  • Point1 (0)
  • Point1 (1)
  • Point1 (2)
  • Point2 (0)
  • Point2 (1)
  • Point2 (2)
  • Resolution
  • Visibility
  • Opacity

All of these are scalar quantities. They work as expected, too.

If I add a Poly Line Source source (not sure why it has the Source again in the name), I get the following fields in the animation view:

  • Closed
  • Points
  • Visibility
  • Opacity

The fields Closed, Visibility, and Opacity again work as expected. But Points already looks odd when you add it: It shows up as "PolyLineSource - Points (-1)", with a default value of 0 (whatever that means). Sure enough, when I run the animation this way, ParaView 5.1.2 crashes.

I'd like to change the coordinates of certain points at certain keyframes, albeit not their number. Is that possible from within python at least?

PS: I'm not sure how to do anything with the animation view from within python because changes in it appear not to be traced.

PPS: The Expression field of the Python Annotation filter also appears to behave rather weirdly in the animation view (not entirely surprisingly, e.g. because interpolation of expressions would be weird -- only the step function approach could really be expected to work)

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