You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Testing integration with the libsim/visit adapter and the VTK-IO adapter exposed an issue in the SVTKUtils. It seems the SVTKUtils were written to work only with a VTK 9.x.x.
I have not tested explicitly which versions don't work, but it does not work with and of the VTK 8.x.x versions used by visit but it does work with the VTK inside of ParaView 5.10 when catalyst is on (roughly VTK 9).
There seem to be two options, either write variations of the SVTKUtils that work with VTK 8 or disable the VTK adapters when building the Visit adapters.
This is a consequence of backward incompatible changes between VTK 8 and 9 unstructured meshes and the massive performance degradation associated with using the VTK < 9 zero-copy API with newer VTK 9. We don't have the resources to support VTK < 9. However, it would be OK to add support for VTK < 9 if a patch for this were to come from the community. we should add CMake Version check for VTK 9 for our adaptors that make use of VTK 9 unstructured mesh zero-copy API so that the situation is clear.
burlen
changed the title
libsim/VTK-IO integration error: Sensei requires VTK 9 for VTK adapters but Visit requires VTK 8
Add CMake version checks for our VTK based adaptors that use VTK 9 unstructured grid zero-copy API
May 16, 2022
Testing integration with the libsim/visit adapter and the VTK-IO adapter exposed an issue in the SVTKUtils. It seems the SVTKUtils were written to work only with a VTK 9.x.x.
I have not tested explicitly which versions don't work, but it does not work with and of the VTK 8.x.x versions used by visit but it does work with the VTK inside of ParaView 5.10 when catalyst is on (roughly VTK 9).
There seem to be two options, either write variations of the SVTKUtils that work with VTK 8 or disable the VTK adapters when building the Visit adapters.
@burlen
The text was updated successfully, but these errors were encountered: