When I export a Catalyst Python V2 script from Paraview 5.9.1 and try to run it as an in-situ pipeline in a ParaView Catalyst instrumented code, the corresponding Input Data Description always seems to request all fields rather than just the ones needed by the pipeline which can be a little costly in a simulation and makes code that checks what fields are needed (e.g. this line) somewhat redundant (at least for these scripts)?
I can see from a comment in the
vtkCPPythonScriptV2Helper class that this is because these new scripts do not implement data descriptions like the old scripts. Is there a plan to implement these soon so that my simulations don’t pass fields unnecessarily to Catalyst?