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,846
    • Issues 1,846
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 87
    • Merge requests 87
  • 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
  • #18575
Closed
Open
Created Oct 30, 2018 by Joel A. Kulesza@jkulesza_lanl

AnnotateTimeFilter Shift/Scaling Malfunctioning

Issue Summary

The AnnotateTimeFilter behaves differently in 5.6.0 RC3 versus 5.5.2. Specifically, it seems to work correctly in 5.5.2 and not correctly in 5.6.0 RC3. When the shift and scale values are adjusted and applied, there appears to be a lag to the application of the modification.

Steps to reproduce the behavior given below.

All testing performed on macOS 10.12.6.

Steps to Reproduce

  1. Load attached files as time-sequence data.
  2. Apply to "visualize" the data.
  3. Select the block_in_a_block_00* pipeline object.
  4. Insert a Filters -> Annotate Time Filter.
  5. Apply. Annotation should display as "Time: 0.000000".
  6. Moving forward/backward through time should display the correct value.
  7. Go to the 0th time step.
  8. Change Shift from 0 to 30. Apply.

The Time does not update. Moving forward and backward through time goes as 0, 1, 2 not 30, 31, 32.

  1. Change Scale from 1 to 2. Apply.

Now the shift is captured correctly, but the scaling is not. Moving forward and backward through time goes as 30, 31, 32 not 30, 32, 34.

CC: @patchett2002 @ethan.stam

Files

block_in_a_block_001.vtk

block_in_a_block_002.vtk

block_in_a_block_003.vtk

Edited Oct 31, 2018 by Joel A. Kulesza
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking