Take a look at the ParaView tests that exercise this functionality:
[~/projects/ParaView/build]$ ctest -R CatalystLive
Test project /home/danlipsa/projects/ParaView/build
Start 1848: pv.CatalystLiveSetBreakpoint
1/4 Test #1848: pv.CatalystLiveSetBreakpoint … Passed 29.40 sec
Start 1849: pvcs.CatalystLiveSetBreakpoint
2/4 Test #1849: pvcs.CatalystLiveSetBreakpoint … Passed 29.10 sec
Start 1850: pv.CatalystLivePause
3/4 Test #1850: pv.CatalystLivePause … Passed 33.21 sec
Start 1851: pvcs.CatalystLivePause
4/4 Test #1851: pvcs.CatalystLivePause … Passed 32.42 sec
You can use ctest -N -V -R CatalystLive
to see the full commands executed.
You’ll need to build ParaView from source and enable tests: BUILD_TESTING should be ON.
In these tests there are two scripts:
ParaView/src/Applications/ParaView/Testing/XML/CatalystWaveletDriver.py
This plays the role of the simulation and generates the data.
ParaView/src//Applications/ParaView/Testing/XML/CatalystWaveletCoprocessing.py
this is the processing pipeline.
In your case, you need the simulation (which can be a python script as well) and a processing pipeline python script which creates a visualization every step of the simulation.