Closed sfladi closed 4 months ago
As far as I understand this is an issue with VTK and is already patched in VTK https://gitlab.kitware.com/vtk/vtk/-/merge_requests/10629
Im sorry I have little insight into this topic, but is it just a matter of waiting for dependency updates to propagate through to pyvista?
As far as I understand this is an issue with VTK and is already patched in VTK https://gitlab.kitware.com/vtk/vtk/-/merge_requests/10629
Im sorry I have little insight into this topic, but is it just a matter of waiting for dependency updates to propagate through to pyvista?
You are right. It seems that it has not been added to vtk
v9.3.0. We need to wait until the next vtk
version and close this issue when you check that it is reflected.
Edit: To make sure it is still not on release. We can see that the patch is not in the dev at release note directory. https://gitlab.kitware.com/vtk/vtk/-/blob/2b2257711e4b4fed98422894939c123004e23b6b/Documentation/release/dev/expat-large-size-fix.md
I understand, thank you for looking into this!
This is fixed with the release of VTK
v9.3.1: https://discourse.vtk.org/t/vtk-9-3-1-is-out/14141
This is fixed with the release of
VTK
v9.3.1: https://discourse.vtk.org/t/vtk-9-3-1-is-out/14141
Awesome! Thanks for sharing this.
Describe the bug, what's wrong, and what you expected.
Pyvista raises an error, when reading large VTK XML-files on Windows. In my current use case this is an approximately 7GB .vtu-file holding a large mesh with finite element result data.
The encountered error message is:
This seems to be related to a an issue recently resolved in ParaView, c.f. https://gitlab.kitware.com/paraview/paraview/-/issues/22201 or https://gitlab.kitware.com/paraview/paraview/-/issues/21145. In fact, I encountered literally the identical error, when trying to open my large .vtu-file in ParaView, as i did when using pyvista. Upgrading my ParaView installation to the most recent version resolved the issue in ParaView, indicating for my .vtu-file to be valid.
When trying to reproduce the bug, i would advise to use the .vtu-file provided in the ParaView issue 22201 mentioned above. This will produce a different but seemingly related error message, documented below.
Steps to reproduce the bug.
This produces the following error message:
System Information
Screenshots
No response