I know you said that was a simplified case but the first thing that jumps out at me is that you are explicitly setting the time. You already have a handle to the timesteps through times = tk.TimestepValues so you should set the time like tk.Time = times[1]
As far as the time looping goes, the full code shouldn’t be much different from a simplified version. Just some code pushed under a for loop.
You might need a general UpdatePipeline() or Render() call as well.
I have not yet implemented a loop, as I thought I would not add any more complexity if I could not even manually switch the time affectively. The trace seemed to suggest that tk.Time = was the way to go. But either this is not the case or there is a bug.
I have probeLocation1.UpdatePipeline() on line 55, so I doubt it will do anything or maybe I am using it wrong.
As for Render(), I thought that was just used to force a redraw/render to a viewport. Since this is strictly in the command line with no viewport, I thought it would not do anything. In fact, I just tested it and it gives an error if used.
So, the question still remains, how would I go about changing the time to location probe data?
@lizliv I couldn’t dig up the code, but I feel like I’ve run into that issue before and solved it by adding a call to the UpdateVTKObjects property of the client-side source of interest.
So for you it would be integrateVariables1.UpdateVTKObjects() before the Fetch call.
This is just based off of fuzzy memory so I apologize if it doesn’t help.
I found a solution! I ran Trace with “Skip Rendering Components” enabled and found the command UpdatePipeline() without any render/source input, it acts on the proxy. This is my code snippet that worked to loop over time within a filter:
tsteps = paraviewReader.TimestepValues
...
integrateVariables1 = IntegrateVariables(Input=slice1)
for t in tsteps:
UpdatePipeline(time=t, proxy=integrateVariables1)
...