# Unexpected behavior of Temporal Shift Scale Filter

**URL:** https://discourse.paraview.org/t/unexpected-behavior-of-temporal-shift-scale-filter/15472
**Category:** ParaView Support
**Created:** [September 30, 2024, 6:12am UTC](https://discourse.paraview.org/t/unexpected-behavior-of-temporal-shift-scale-filter/15472 "2024-09-30T06:12:14Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![jameskress](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jameskress/32/10687_2.png) [@jameskress](https://discourse.paraview.org/u/jameskress)
#### Post date: [September 30, 2024, 6:12am UTC](https://discourse.paraview.org/t/unexpected-behavior-of-temporal-shift-scale-filter/15472/1 "2024-09-30T06:12:14Z")

</div>

Good morning,

It looks like the behavior of the temporal shift scale filter has changed in recent versions of ParaView. I have a state file from 5.11 where the behavior was what I’ll call “correct” for the purposes of this discussion.

What I am observing now, is that if I create a pipeline with `temporal shift scale` that it will not update unless the `temporal shift scale` filter is active in the pipeline browser. Meaning, any downstream filters fail to get the shifted time values, instead they get a static time value, if it is not marked as `visible` in the pipeline browser. This is not great, as you have to then assign it a representation, and I don’t care to see intermediate steps in my workflow, so I have to set the opacity of these intermediate steps to `0`.

Is this expected behavior now? It took a while to figure this out, so it seems non-obvious.

This can easily be reproduced with the `SpatioTemporalHarmonicsUniformGrid` data source, a `temporal shift scale` filter, an `append attributes` filter, and a `calculator`. State file is attached. You will see that with the `Temporal Shift Scale` filter not visible that the result is `0`. Whereas when you make is visible the result is as expected.

Cheers,  
James

[temporalshiftscale.pvsm](https://discourse.paraview.org/uploads/short-url/96UeGHpaFuiLY8Ur3AQGMwIsr5f.pvsm) (623.8 KB)

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [September 30, 2024, 8:00am UTC](https://discourse.paraview.org/t/unexpected-behavior-of-temporal-shift-scale-filter/15472/2 "2024-09-30T08:00:53Z")

</div>

This is clearly a bug and it should be investigated and fixed.

---

<div class="post-metadata">

### Author: ![jameskress](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jameskress/32/10687_2.png) [@jameskress](https://discourse.paraview.org/u/jameskress)
#### Post date: [September 30, 2024, 11:17am UTC](https://discourse.paraview.org/t/unexpected-behavior-of-temporal-shift-scale-filter/15472/3 "2024-09-30T11:17:36Z")

</div>

Created an issue

[https://gitlab.kitware.com/paraview/paraview/-/issues/22766](https://gitlab.kitware.com/paraview/paraview/-/issues/22766)
