<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">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 update (or render) the data between the time steps. There
could be a call in ParaView Python API to force ParaView to render
data. Following code from SampleScripts/feslicescript.py<br>
<br>
freqs = {'input': [10, 100]}<br>
coprocessor.SetUpdateFrequencies(freqs)<br>
<br>
might be related with it but i am not sure. Any idea?<br>
<br>
--ufuk<br>
<br>
On 11/06/15 11:28, Peter wrote:<br>
</div>
<blockquote
cite="mid:6aa01707e399bbef2b76bf91f58b7ddd@peterheppel.com"
type="cite">
<p>Hi Ufuk,</p>
<p>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.</p>
<p>Can you find out how to get Paraview to render each timestep? </p>
<p>I guess to implement this in our simulations we'll have to put
a 'system("paraview --script=something") ; in our code just
after the FEAdaptor::Initialize() call. The script would
connect Catalyst.</p>
<p>Cheers</p>
<p> </p>
<div>
<pre>---
Peter Heppel
35/37 Rue de Locmalo
56290 Port-Louis
France
+33 6 81 30 76 52 cell
+33 2 97 82 19 30
USA +1 773 280 8142
Skype: peterheppel</pre>
</div>
<p>On 2015-06-11 10:10, Ufuk Utku Turuncoglu (BE) wrote:</p>
<blockquote type="cite" style="padding-left:5px;
border-left:#1010ff 2px solid; margin-left:5px"><!-- html ignored -->
<!-- head ignored --><!-- meta ignored -->
<div class="moz-cite-prefix">Hi Peter,<br>
<br>
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,<br>
<!-- meta ignored --><br>
ERROR: In
/Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx,
line 735,vtkSocketCommunicator (0x7fd4837cd120): Could not
send tag.<br>
<br>
ERROR: In
/Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx,
line 812,vtkSocketCommunicator (0x7fd4837cd120): Could not
receive tag. 8013<br>
<br>
ERROR: In
/Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx,
line 812,vtkSocketCommunicator (0x7fd4837cd120): Could not
receive tag. 1<br>
<br>
ERROR: In
/Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx,
line 812,vtkSocketCommunicator (0x7fd483a02280): Could not
receive tag. 1<br>
<br>
In this case, the code is also compiled with ParaView 4.2. So,
there is no any version issue.<br>
<br>
By the way, it is necessary to add follow code to include
section<br>
<br>
#include <iostream><br>
#include <unistd.h><br>
<br>
to make cout, endl and sleep function available.<br>
<br>
--ufuk<br>
<br>
On 11/06/15 10:47, Peter wrote:</div>
<blockquote type="cite" style="padding-left:5px;
border-left:#1010ff 2px solid; margin-left:5px">
<p>Hello,</p>
<p>I've made some progress, but its not the complete answer.</p>
<p>To make the Catalyst examples display in Paraview, you have
to go Paraview>Catalyst>Connect AFTER the client has
initialized Catalyst.<br>
You also have to turn OFF the file write in the catalyst
script.</p>
<p>Try the following changes (I tested CxxFullExample)</p>
<p>1) In FEDriver.cxx, after the call to
FEAdaptor::Initialize() , add something like</p>
<p> std::cout<<"Please connect in Paraview"<<endl;</p>
<p>sleep(20);</p>
<p>I also put a 'sleep(1)' into the timestep loop to give more
time to manipulate paraview.</p>
<p>2) In feslicescript.py, you remove the calls to
coprocessor.CreateWriter and change EnableLiveVisualization
to True).</p>
<p>Now, the test sequence is:</p>
<p>1) start Paraview. DONT connect Catalyst.</p>
<p>2) run the CxxFullExample with (path)feslicecinema.py as
argument .( To find out the exact command, go ctest
--verbose)</p>
<p>3) When you see "Please connect in Paraview", in the
Catalyst menu you go 'Connect' and dismiss the dialogs which
follow.</p>
<p>You'll see some changes in the pipeline browser. Paraview
can see some data but doesnt render it until after the end
of the timestepping. Would you like to look at that?</p>
<p> </p>
<p>Cheers</p>
<p> </p>
<div>
<pre>---
Peter Heppel
35/37 Rue de Locmalo
56290 Port-Louis
France
+33 6 81 30 76 52 cell
+33 2 97 82 19 30
USA +1 773 280 8142
Skype: peterheppel</pre>
</div>
<p>On 2015-06-10 22:54, Peter wrote:</p>
<blockquote style="padding-left: 5px; border-left: #1010ff 2px
solid; margin-left: 5px;"><!-- node type 8 --><!-- node type 8 --><!-- node type 8 -->
<p> </p>
<p>Thanks for replying. Take a look at</p>
<p><a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://public.kitware.com/pipermail/paraview/2015-June/034283.html">http://public.kitware.com/pipermail/paraview/2015-June/034283.html</a></p>
<p>Briefly,</p>
<p>Paraview segfaults with the above error message when I
run any of the tests in ParaViewCatalystExampleCode-master
with <em>coprocessor.EnableLiveVisualization(True). </em>They
all pass when this flag is False. I've tested with V4.3.1
and with yesterday's development version. There's another
user - <strong>u.utku.turuncoglu at be.itu.edu.tr</strong>
<a moz-do-not-send="true" title="[Paraview]
pqPipelineSource::getOutputPort( 0 ). Available number
of output ports: 0"
href="mailto:paraview%40paraview.org?Subject=Re%3A%20%5BParaview%5D%20pqPipelineSource%3A%3AgetOutputPort%28%200%20%29.%20Available%0A%20number%20of%20output%20ports%3A%200&In-Reply-To=%3C60384.88.235.36.106.1433760302.squirrel%40webmail.be.itu.edu.tr%3E">u.utku.turuncoglu
at be.itu.edu.tr </a>who has a similar problem on a
different O/S.</p>
<p>Are the tests in ParaViewCatalystExampleCode-master
known to run OK with <em>coprocessor.EnableLiveVisualization(True)? </em>
Or is that not the only change needed to make these
clients connect?</p>
<p>If we are running ParaViewCatalystExampleCode-master
correctly we'd appreciate your advice on where to start
looking for a bug.</p>
<p>best regards</p>
<p>Peter</p>
<p> </p>
<p> </p>
<div>
<pre>---
Peter Heppel
35/37 Rue de Locmalo
56290 Port-Louis
France
+33 6 81 30 76 52 cell
+33 2 97 82 19 30
USA +1 773 280 8142
Skype: peterheppel</pre>
</div>
<p>On 2015-06-10 19:47, Utkarsh Ayachit wrote:</p>
<blockquote style="padding-left: 5px; margin-left: 5px;"><!-- node type 8 --><!-- node type 8 --><!-- node type 8 -->
<div dir="ltr">I am not sure I follow what's happening
here. Can you provide details on what you're doing here
please? Thanks.
<div> </div>
<div>Utkarsh<br>
<br>
<div class="gmail_quote">
<div dir="ltr">On Wed, Jun 10, 2015 at 11:38 AM
Peter <<a moz-do-not-send="true"
href="mailto:peter@peterheppel.com">peter@peterheppel.com</a>>
wrote:</div>
<blockquote class="gmail_quote" style="border-left:
1px #ccc solid; padding-left: 1ex;"><span
style="text-decoration: underline;"></span>
<div style="font-size: 10pt; font-family:
Verdana,Geneva,sans-serif;">
<p>Hello</p>
<p>I just built the current Paraview development
version and got the same error on running the
Catalyst examples.</p>
<p>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 that it
only occurs after the socket connection is
successful. </p>
<p>P</p>
<p> </p>
<div>
<pre>--
Peter Heppel
35/37 Rue de Locmalo
56290 Port-Louis
France
+33 6 81 30 76 52 cell
+33 2 97 82 19 30
USA +1 773 280 8142
Skype: peterheppel</pre>
</div>
</div>
_______________________________________________<br>
Powered by <a moz-do-not-send="true"
href="http://www.kitware.com">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a
moz-do-not-send="true"
href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the
ParaView Wiki at: <a moz-do-not-send="true"
href="http://paraview.org/Wiki/ParaView">http://paraview.org/Wiki/ParaView</a><br>
<br>
Search the list archives at: <a
moz-do-not-send="true"
href="http://markmail.org/search/?q=ParaView">http://markmail.org/search/?q=ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a moz-do-not-send="true"
href="http://public.kitware.com/mailman/listinfo/paraview">http://public.kitware.com/mailman/listinfo/paraview</a></blockquote>
</div>
</div>
</div>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<br>
</body>
</html>