Make Catalyst external dependency and move Conduit module to VTK
Goal
Having the VTK-conduit converter inside VTK directly.
Side effect: having a simple VTKCatalyst implementation.
Tehnical locks
- VTK should depends on Conduit
- ParaViewCatalyst will depend on vtkConduit, but should use Conduit from catalyst
-> VTK should depends on Catalyst to access Conduit.
TODO
-
VTK -
create an optional CatalystConduit
module from VTKExtension to VTK/IO- dependency on catalyst
- also put
vtkDataObjetToConduit
part of this module (instead of Client/InSitu)
-
Make a simple VTKCatalyst
implementation,along to the correspondingvtkBlueprint
-
-
ParaView -
Remove Catalyst third party from paraview -
update Client/InSitu
to use VTK Conduit module updateParaViewCatalyst
and ParaView Blueprint implementations according to the VTK ones.
-
-
ParaView SuperBuild -
add catalyst project
-
-
CI -
VTK docker image (linux) -
VTK windows -
VTK MacOs -
PV docker -
PV windows -
PV MacOs
-
Related MRs
adding optional Conduit module to VTK, and a VTKCatalyst: vtk/vtk!8926 (merged)
removing Conduit module from ParaView and use VTK one: !5517 (merged)
catalyst in superbuild: paraview-superbuild!966 (merged)
Edited by Nicolas Vuaille