# ParaView error when reading OpenSees VTU files with ASDAbsorbingBoundary
**URL:** https://discourse.paraview.org/t/paraview-error-when-reading-opensees-vtu-files-with-asdabsorbingboundary/17683
**Category:** ParaView Support
**Created:** [August 14, 2026, 1:19pm UTC](https://discourse.paraview.org/t/paraview-error-when-reading-opensees-vtu-files-with-asdabsorbingboundary/17683 "2026-08-14T13:19:58Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Aliy1766](https://discourse.paraview.org/u/Aliy1766)
#### Post date: [August 14, 2026, 1:19pm UTC](https://discourse.paraview.org/t/paraview-error-when-reading-opensees-vtu-files-with-asdabsorbingboundary/17683/1 "2026-08-14T13:19:58Z")
Hello,
I am using OpenSees for dynamic soil–structure interaction analysis and ParaView for post-processing the results.
My model contains quad soil elements and structural elements. The VTK output works correctly in ParaView when no absorbing boundary elements are used.
However, after adding ASDAbsorbingBoundary elements, ParaView cannot read the generated .vtu files and gives the following error:
Cannot read point data array “Disp” from PointData in piece 0.
The data array in the element may be too short.
The error is repeated for the time steps.
I am using:
recorder vtk NPP\_Results disp accel -dT 0.002
Is ASDAbsorbingBoundary fully supported by the OpenSees VTK recorder? Could these elements cause an inconsistency between the number of mesh points and the Disp PointData array?
What is the recommended way to export an OpenSees model containing ASDAbsorbingBoundary elements to ParaView?
Thank you
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [August 17, 2026, 12:23pm UTC](https://discourse.paraview.org/t/paraview-error-when-reading-opensees-vtu-files-with-asdabsorbingboundary/17683/2 "2026-08-17T12:23:45Z")
Please share a non working .vtu file
---
### Author:  [@Aliy1766](https://discourse.paraview.org/u/Aliy1766)
#### Post date: [August 22, 2026, 7:06am UTC](https://discourse.paraview.org/t/paraview-error-when-reading-opensees-vtu-files-with-asdabsorbingboundary/17683/3 "2026-08-22T07:06:42Z")
[displacement000000000000000000005.vtu](https://discourse.paraview.org/uploads/short-url/1EjVWmkvIAFAhtRhXuRVlnAGLo5.vtu) (248.2 KB)
This file is one of several VTU files available in the results folder.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [August 24, 2026, 9:56am UTC](https://discourse.paraview.org/t/paraview-error-when-reading-opensees-vtu-files-with-asdabsorbingboundary/17683/4 "2026-08-24T09:56:39Z")
Works fine in ParaView 6.1.0 binary release for Linux, which version of ParaView are you using ?
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [August 24, 2026, 4:05pm UTC](https://discourse.paraview.org/t/paraview-error-when-reading-opensees-vtu-files-with-asdabsorbingboundary/17683/5 "2026-08-24T16:05:13Z")
Error confirmed in ParaView 6.2.0-RC1 on macOS.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [August 24, 2026, 4:07pm UTC](https://discourse.paraview.org/t/paraview-error-when-reading-opensees-vtu-files-with-asdabsorbingboundary/17683/6 "2026-08-24T16:07:37Z")
Error confirmed also in ParaView 6.1.1 and 5.12.1 on macOS.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [August 24, 2026, 4:16pm UTC](https://discourse.paraview.org/t/paraview-error-when-reading-opensees-vtu-files-with-asdabsorbingboundary/17683/7 "2026-08-24T16:16:54Z")
There’s nothing obviously wrong with the “Disp” data array definition in the XML file at first glance. The number of values looks to be right. I would need to dig in deeper to see what’s going on.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [August 25, 2026, 8:29am UTC](https://discourse.paraview.org/t/paraview-error-when-reading-opensees-vtu-files-with-asdabsorbingboundary/17683/8 "2026-08-25T08:29:54Z")
Really strange to see a MacOS / Linux diff tbh