# ParaView 6.2.0 complains about not having any points for plot over line on an MPI distributed dataset
**URL:** https://discourse.paraview.org/t/paraview-6-2-0-complains-about-not-having-any-points-for-plot-over-line-on-an-mpi-distributed-dataset/17755
**Category:** In Situ Support
**Tags:** vtk
**Created:** [October 2, 2026, 2:25pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-complains-about-not-having-any-points-for-plot-over-line-on-an-mpi-distributed-dataset/17755 "2026-10-02T14:25:30Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Alexandre\_Minot](https://discourse.paraview.org/u/Alexandre_Minot)
#### Post date: [October 2, 2026, 2:25pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-complains-about-not-having-any-points-for-plot-over-line-on-an-mpi-distributed-dataset/17755/1 "2026-10-02T14:25:30Z")
Hello,
I am getting these warning since I updated from ParaView 6.2.0 RC1 to 6.2.0:
```auto
( 1.403s) [pvbatch.0] vtkPolyDataReader.cxx:267 WARN| vtkPolyDataReader (0x7cd01787c980): No points read!
( 1.403s) [pvbatch.0] vtkPolyDataReader.cxx:267 WARN| vtkPolyDataReader (0x7cd01787ae80): No points read!
( 1.404s) [pvbatch.0] vtkPolyDataReader.cxx:267 WARN| vtkPolyDataReader (0x7cd01787ba80): No points read!
( 1.404s) [pvbatch.0] vtkPolyDataReader.cxx:267 WARN| vtkPolyDataReader (0x7cd017884480): No points read!
( 1.404s) [pvbatch.0] vtkPolyDataReader.cxx:267 WARN| vtkPolyDataReader (0x7cd017882f80): No points read!
( 1.404s) [pvbatch.0] vtkPolyDataReader.cxx:267 WARN| vtkPolyDataReader (0x7cd017880b80): No points read!
( 1.452s) [pvbatch.0] vtkPolyDataReader.cxx:267 WARN| vtkPolyDataReader (0x7cd017cb1080): No points read!
( 1.452s) [pvbatch.0] vtkPolyDataReader.cxx:267 WARN| vtkPolyDataReader (0x7cd017cb2580): No points read!
( 1.452s) [pvbatch.0] vtkPolyDataReader.cxx:267 WARN| vtkPolyDataReader (0x7cd017cb3a80): No points read!
( 1.453s) [pvbatch.0] vtkPolyDataReader.cxx:267 WARN| vtkPolyDataReader (0x7cd017cb4f80): No points read!
( 1.453s) [pvbatch.0] vtkPolyDataReader.cxx:267 WARN| vtkPolyDataReader (0x7cd017cb6480): No points read!
( 1.453s) [pvbatch.0] vtkPolyDataReader.cxx:267 WARN| vtkPolyDataReader (0x7cd017cb7980): No points read!
( 1.453s) [pvbatch.0] vtkPolyDataReader.cxx:267 WARN| vtkPolyDataReader (0x7cd017cb8e80): No points read!
```
These warning are thrown when using the PlotOverLine filter on an MPI distributed dataset (CFD code + ParaView Catalyst).
I suspect this is thrown by the filter on ranks that do not have data that intersects with the line.
This may not seem like a big deal, but in a ParaView Catalyst context, we are talking about hundreds of ranks throwing warnings to the screen log everytime Catalyst is called, which is potentially often. This renders the screen log almost unreadable.
If you confirm what I am saying, then I would consider this a regression and would appreciate a quick resolution. I do not think we can use ParaView 6.2 in this state.
Many thanks,
Alexandre
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 2, 2026, 2:29pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-complains-about-not-having-any-points-for-plot-over-line-on-an-mpi-distributed-dataset/17755/2 "2026-10-02T14:29:47Z")
Is that catalyst or can this be reproduced by just opening a specific file and adding PlotOverLine ?
If that is so, please share that file.
---
### Author:  [@Alexandre\_Minot](https://discourse.paraview.org/u/Alexandre_Minot)
#### Post date: [October 2, 2026, 2:32pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-complains-about-not-having-any-points-for-plot-over-line-on-an-mpi-distributed-dataset/17755/3 "2026-10-02T14:32:20Z")
I have not tried to reproduce it in ParaView, as I am not well versed in creating distributed datasets in ParaView.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [October 2, 2026, 8:18pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-complains-about-not-having-any-points-for-plot-over-line-on-an-mpi-distributed-dataset/17755/4 "2026-10-02T20:18:11Z")
@Alexandre_Minot is it convenient for you to try reverting [https://gitlab.kitware.com/vtk/vtk/-/commit/a78669d689337d262ceac319a36878c8dedc3668](https://gitlab.kitware.com/vtk/vtk/-/commit/a78669d689337d262ceac319a36878c8dedc3668) locally and see if the warning messages disappear?
By the way, IMO reading zero points is fine and should not produce a warning in any case, so we should remove that message.