# paraview particle tracer
**URL:** https://discourse.paraview.org/t/paraview-particle-tracer/16998
**Category:** ParaView Support
**Created:** [July 23, 2025, 6:23pm UTC](https://discourse.paraview.org/t/paraview-particle-tracer/16998 "2025-07-23T18:23:34Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@semeraro](https://discourse.paraview.org/u/semeraro)
#### Post date: [July 23, 2025, 6:23pm UTC](https://discourse.paraview.org/t/paraview-particle-tracer/16998/1 "2025-07-23T18:23:34Z")
Hello there,
I am encountering errors when I use the particletracer filter on a vtr time series in paraview version 5.11.1. The error looks like this
ERROR: In vtkStreamingDemandDrivenPipeline.cxx, line 878
vtkPVPostFilterExecutive (0xf4e1920): The update extent specified in the information for output port 0 on algorithm vtkPVPostFilter (0xf3d90c0) is 0 96 0 76 0 22, which is outside the whole extent 1 1 0 76 0 22.
My data is a sequence of vtr datasets. They contain separate U,V, and W velocity components. I use the calculator to construct a velocity vector. I then extract a subset ( x = 1 plane) of the data to use as a seed for the particle tracer. The input of the particle tracer is the calculator output. The seed is the extract subset filter output. Executing the pipeline gives the error above.
I am running this on one of the HPC systems at TACC, single node no parallelism (small data). I can run the pipeline without error on my laptop ( god I know that sounds bad, sorry) so I think I am using the filters correctly. I even copied the state file from my laptop to the HPC system to no avail. It still fails on the HPC system. Any ideas how I can get this to work on the HPC system? I have some large data in the wings.
Best Regards,
Dave
---
### Author:  [@semeraro](https://discourse.paraview.org/u/semeraro)
#### Post date: [July 23, 2025, 7:25pm UTC](https://discourse.paraview.org/t/paraview-particle-tracer/16998/2 "2025-07-23T19:25:11Z")
never mind. I figured it out. It was basically a difference between 5.11.0 and 5.11.1. I fixed it by using a source object as the seed (plane) rather than a subset of the whole data.
thanks,
Dave