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
freqs = {'input': [10, 100]}
coprocessor.SetUpdateFrequencies(freqs)
might be related with it but i am not sure. Any idea?
--ufuk
On 11/06/15 11:28, Peter wrote:
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 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.
Cheers
---
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
On 2015-06-11 10:10, Ufuk Utku Turuncoglu (BE) wrote:
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: In
/Users/turuncu/Qsync/progs/paraview-4.2.0/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx,
line 735,vtkSocketCommunicator (0x7fd4837cd120): Could not send tag.
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
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
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
In this case, the code is also compiled with ParaView 4.2. So, there
is no any version issue.
By the way, it is necessary to add follow code to include section
#include <iostream>
#include <unistd.h>
to make cout, endl and sleep function available.
--ufuk
On 11/06/15 10:47, Peter wrote:
Hello,
I've made some progress, but its not the complete answer.
To make the Catalyst examples display in Paraview, you have to go
Paraview>Catalyst>Connect AFTER the client has initialized Catalyst.
You also have to turn OFF the file write in the catalyst script.
Try the following changes (I tested CxxFullExample)
1) In FEDriver.cxx, after the call to FEAdaptor::Initialize() , add
something like
std::cout<<"Please connect in Paraview"<<endl;
sleep(20);
I also put a 'sleep(1)' into the timestep loop to give more time to
manipulate paraview.
2) In feslicescript.py, you remove the calls to
coprocessor.CreateWriter and change EnableLiveVisualization to True).
Now, the test sequence is:
1) start Paraview. DONT connect Catalyst.
2) run the CxxFullExample with (path)feslicecinema.py as argument .(
To find out the exact command, go ctest --verbose)
3) When you see "Please connect in Paraview", in the Catalyst menu
you go 'Connect' and dismiss the dialogs which follow.
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?
Cheers
---
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
On 2015-06-10 22:54, Peter wrote:
Thanks for replying. Take a look at
http://public.kitware.com/pipermail/paraview/2015-June/034283.html
Briefly,
Paraview segfaults with the above error message when I run any
of the tests in ParaViewCatalystExampleCode-master with
/coprocessor.EnableLiveVisualization(True). /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 -
*u.utku.turuncoglu at be.itu.edu.tr* u.utku.turuncoglu at
be.itu.edu.tr
<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>who
has a similar problem on a different O/S.
Are the tests in ParaViewCatalystExampleCode-master known to
run OK with /coprocessor.EnableLiveVisualization(True)? / Or is
that not the only change needed to make these clients connect?
If we are running ParaViewCatalystExampleCode-master correctly
we'd appreciate your advice on where to start looking for a bug.
best regards
Peter
---
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
On 2015-06-10 19:47, Utkarsh Ayachit wrote:
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 <mailto:pe...@peterheppel.com>> wrote:
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 that it only occurs after the socket
connection is successful.
P
--
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
_______________________________________________
Powered by www.kitware.com <http://www.kitware.com>
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView
Wiki at: http://paraview.org/Wiki/ParaView
Search the list archives at:
http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Search the list archives at: http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
