# vtu files not behaving as expected

**URL:** https://discourse.paraview.org/t/vtu-files-not-behaving-as-expected/2264
**Category:** ParaView Support
**Created:** [July 19, 2019, 11:06am UTC](https://discourse.paraview.org/t/vtu-files-not-behaving-as-expected/2264 "2019-07-19T11:06:21Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![RicardoCanelas](https://discourse.paraview.org/user_avatar/discourse.paraview.org/ricardocanelas/32/1761_2.png) [@RicardoCanelas](https://discourse.paraview.org/u/RicardoCanelas)
#### Post date: [July 19, 2019, 11:06am UTC](https://discourse.paraview.org/t/vtu-files-not-behaving-as-expected/2264/1 "2019-07-19T11:06:21Z")

</div>

Hi!

I’m writing particle data to a .vtu file. I’m not using cell data, and set all of solution directly in point data.  
I can load these files in Paraview, but can only render the data as Point Gaussian (not ideal for large data sets) and most important, filters applied to this data come out empty, with not output.

Any idea why that might be and what I would need to do in order to solve this? Any help would be most welcome.

I’m attaching two files, one written in ascii and one in raw, they both should have the same data.

Best regards,  
Ricardo

[ascii\_IBI\_00002.vtu](https://discourse.paraview.org/uploads/default/original/2X/8/859f041cb2b812c0e9d944152575be987a90235c.vtu) (4.9 KB)  
[raw\_IBI\_00002.vtu](https://discourse.paraview.org/uploads/default/original/2X/4/4ce21f3931559eb0b650503932f5868c1e5b4e19.vtu) (3.7 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: [July 19, 2019, 11:18am UTC](https://discourse.paraview.org/t/vtu-files-not-behaving-as-expected/2264/2 "2019-07-19T11:18:54Z")

</div>

There is no cells associated to your points.  
Please add a programmable filter with the following script to correct this.

```
pdi = self.GetInput()
pdo = self.GetOutput()
numPts = pdi.GetNumberOfPoints()
ids = vtk.vtkIdList()
ids.SetNumberOfIds(1)
for i in range(0, numPts):
    ids.SetId(0, i)
    pdo.InsertNextCell(vtk.VTK_VERTEX, ids)
```

---

<div class="post-metadata">

### Author: ![RicardoCanelas](https://discourse.paraview.org/user_avatar/discourse.paraview.org/ricardocanelas/32/1761_2.png) [@RicardoCanelas](https://discourse.paraview.org/u/RicardoCanelas)
#### Post date: [July 19, 2019, 11:29am UTC](https://discourse.paraview.org/t/vtu-files-not-behaving-as-expected/2264/3 "2019-07-19T11:29:02Z")

</div>

Thank you for the speedy reply!

would there be any way to make this at file level? I’m looking at multiple files, with 10^6+ points each. Using the programmable filter might be a bit nose heavy at some point.

Regards

---

<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: [July 19, 2019, 11:37am UTC](https://discourse.paraview.org/t/vtu-files-not-behaving-as-expected/2264/4 "2019-07-19T11:37:07Z")

</div>

Well, you can of course write the vertex cells when you are generating your .vtu files.
