ParaView Catalyst warns instead of raising an error when the script is not found

In Situ Support
1

Dear all,

If the catalyst script is not found, ParaView displays

[pvbatch.0       ]vtkInSituInitialization:295   WARN| File/path does not exist and not in PYTHONPATH: 'my_paraview_interface'. Skipping.

and the ParaView Catalyst initialize call returns catalyst_status_ok.

I really think this should be an error. What does the community thinks?

I tried to reproduce this with the examples, but I can no longer find the Catalyst2 examples in the source code. Not sure where they went. In particular, the links here are broken: Examples for Simulation Developers — ParaView Documentation 5.12.0 documentation

Thanks,
Alexandre

2

That makes sense to me. Cc: @Jeff_Lee

The examples now live: https://gitlab.kitware.com/paraview/catalyst-examples

Cc: @Bob_Obara for the examples bit.

3

Agree, this should be an adaptor choice whether to continue the simulation if the script isn’t found. We can return an error code specific to that condition so the adaptor can decide whether to abort or continue.