Hello,
I've made some progress, but its not the complete answer.
To make the Catalyst examples display in Paraview, you have to go
ParaviewCatalystConnect AFTER the client has initialized Catalyst.
You also have to turn OFF the file write in the catalyst script.
Try the following changes
Hi Peter,
I followed your steps in Paraview 4.2 (compiled under MacOS 10.10.3) and
as you mentioned, i could see the pipeline in the pipeline browser. I
also decrease to time step (from 100 to 3) to test the code. After
finishing the time step loop the ParaView gives following error,
ERROR:
Hi Ufuk,
Good. You get the same result as me. I think the error messages start
after the timestep loop has finished. The good news is that Paraview
handles the termination of the client without crashing.
Can you find out how to get Paraview to render each timestep?
I guess to implement
Actually, that must be handled by the Python script without any
modification in the source code (C++). As i know, the C++ code is just
responsible for data conversion between model code and the ParaView to
create VTK data representation of actual data but in some reason, the
ParaView does not
I am not sure I follow what's happening here. Can you provide details on
what you're doing here please? Thanks.
Utkarsh
On Wed, Jun 10, 2015 at 11:38 AM Peter pe...@peterheppel.com wrote:
Hello
I just built the current Paraview development version and got the same
error on running the
Hello
I just built the current Paraview development version and got the same
error on running the Catalyst examples.
Paraview declined the connection gracefully when the client was built
with a different VTK version, so I suspect the issue isnt related to the
socket handshake, but rather
connections dialog
4) in any of the ParaViewCatalystExampleCode-master scripts, I change
coprocessor.EnableLiveVisualization to (True) and run the test.
paraview crashes with
Invalid output port : pqPipelineSource::getOutputPort( 0 ). Available
number of output ports: 0
(...ParaView-v4.3.1-source/Qt
for Catalyst connections dialog
4) in any of the ParaViewCatalystExampleCode-master scripts, I change
coprocessor.EnableLiveVisualization to (True) and run the test.
paraview crashes with
Invalid output port : pqPipelineSource::getOutputPort( 0 ). Available
number of output ports: 0
(...ParaView
