[Paraview] pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0
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 (I tested CxxFullExample) 1) In FEDriver.cxx, after the call to FEAdaptor::Initialize() , add something like std::coutPlease connect in Paraviewendl; 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 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 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 [1] Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html [2] Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView [3] Search the list archives at: http://markmail.org/search/?q=ParaView [4] Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview [5] Links: -- [1] http://www.kitware.com [2] http://www.kitware.com/opensource/opensource.html [3] http://paraview.org/Wiki/ParaView [4] http://markmail.org/search/?q=ParaView [5] 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
Re: [Paraview] pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0
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 ParaviewCatalystConnect 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::coutPlease connect in Paraviewendl; 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%200In-Reply-To=%3C60384.88.235.36.106.1433760302.squirrel%40webmail.be.itu.edu.tr%3Ewho 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
Re: [Paraview] pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0
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 ParaviewCatalystConnect 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::coutPlease connect in Paraviewendl; 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 [1] 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 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 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
Re: [Paraview] pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0
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
ParaviewCatalystConnect 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::coutPlease connect in Paraviewendl;
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%200In-Reply-To=%3C60384.88.235.36.106.1433760302.squirrel%40webmail.be.itu.edu.tr%3Ewho
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
Re: [Paraview] pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0
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 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 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
[Paraview] pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0
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 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
[Paraview] pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0
Hello Here's a ParaView Catalyst problem that may be related to bug (0027323). O/S is ubuntu 14.04 lts - 64 bit I'd like to connect to a Catalyst-enabled simulation, so first I'm running the example code. I do this: 1) download ParaView-v4.3.1-source and build. The ccmake settings are below. 2) download ParaViewCatalystExampleCode-master and build. The ccmake settings are below. 3) run ctest in ParaViewCatalystExampleCode-master/Build - 100% pass 4) run paraview (Build/bin/paraview ), menu CatalystConnect -take port 2 dismiss the Ready 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-v4.3.1-source/Qt/Core/pqPipelineSource.cxx:240, pqOutputPort* pqPipelineSource::getOutputPort(int) const) I've tried with different port numbers, with PV built as debug, as release, with qt4, with qt5, with and without the intel compiler environment( because it supplies its own MPI) Any suggestions, anyone? Thanks ccmake screen for ParaViewCatalystExampleCode-master - BUILD TESTINGON CMAKE_BUILD_TYPE Release CMAKE_INSTALL_PREFIX /usr/local ParaView_DIR /home/r3/software/ParaView-v4.3.1-source/Build QT_QMAKE_EXECUTABLE /usr/bin/qmake-qt4 Qt5Core_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Core Qt5Gui_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui USE_CATALYST ON ccmake screen for ParaView-v4.3.1-source - BUILD_DOCUMENTATION OFF BUILD_EXAMPLES ON BUILD_SHARED_LIBSON BUILD_TESTINGON BUILD_USER_DEFINED_LIBS OFF CMAKE_BUILD_TYPE Release CMAKE_INSTALL_PREFIX /usr/local CTEST_TEST_TIMEOUT 3600 GMVReader_GMVREAD_LIB_DIR /home/r3/software/ParaView-v4.3.1-source/Utilities/VisItBridge/databases/GMV GMVReader_SKIP_DATARANGE_CALCU OFF MPI_C_INCLUDE_PATH /usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi MPI_C_LIBRARIES /usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so PARAVIEW_BUILD_QT_GUION PARAVIEW_ENABLE_CATALYST ON PARAVIEW_ENABLE_FFMPEG OFF PARAVIEW_ENABLE_PYTHON ON PARAVIEW_INSTALL_DEVELOPMENT_F OFF PARAVIEW_USE_DAX OFF PARAVIEW_USE_MPI ON PARAVIEW_USE_PISTON OFF PARAVIEW_USE_UNIFIED_BINDINGSOFF PARAVIEW_USE_VISITBRIDGE OFF Qt5Core_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Core Qt5Designer_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Designer Qt5Gui_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui Qt5Help_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Help Qt5Network_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Network Qt5PrintSupport_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5PrintSupport Qt5Test_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Test Qt5UiTools_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5UiTools Qt5Widgets_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Widgets Qt5Xml_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Xml SURFACELIC_PLUGIN_TESTINGON VTK_PYTHON_VERSION 2 VTK_RENDERING_BACKENDOpenGL VTK_SMP_IMPLEMENTATION_TYPE Sequential VTK_USE_LARGE_DATA OFF XDMF_USE_BZIP2 OFF XDMF_USE_GZIPOFF -- 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 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
Re: [Paraview] pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0
Hi, I have also same problem in Mac OS 10.10 + python (framework) + OpenMPI (compiled with gnu compilers). I compiled both ParaView 4.3.1 and also 4.2.0 from the source but after running Catalyst Examples i am getting same port error. I might help to found the source of the problem. Regards, --ufuk Hello Here's a ParaView Catalyst problem that may be related to bug (0027323). O/S is ubuntu 14.04 lts - 64 bit I'd like to connect to a Catalyst-enabled simulation, so first I'm running the example code. I do this: 1) download ParaView-v4.3.1-source and build. The ccmake settings are below. 2) download ParaViewCatalystExampleCode-master and build. The ccmake settings are below. 3) run ctest in ParaViewCatalystExampleCode-master/Build - 100% pass 4) run paraview (Build/bin/paraview ), menu CatalystConnect -take port 2 dismiss the Ready 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-v4.3.1-source/Qt/Core/pqPipelineSource.cxx:240, pqOutputPort* pqPipelineSource::getOutputPort(int) const) I've tried with different port numbers, with PV built as debug, as release, with qt4, with qt5, with and without the intel compiler environment( because it supplies its own MPI) Any suggestions, anyone? Thanks ccmake screen for ParaViewCatalystExampleCode-master - BUILD TESTINGON CMAKE_BUILD_TYPE Release CMAKE_INSTALL_PREFIX /usr/local ParaView_DIR /home/r3/software/ParaView-v4.3.1-source/Build QT_QMAKE_EXECUTABLE /usr/bin/qmake-qt4 Qt5Core_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Core Qt5Gui_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui USE_CATALYST ON ccmake screen for ParaView-v4.3.1-source - BUILD_DOCUMENTATION OFF BUILD_EXAMPLES ON BUILD_SHARED_LIBSON BUILD_TESTINGON BUILD_USER_DEFINED_LIBS OFF CMAKE_BUILD_TYPE Release CMAKE_INSTALL_PREFIX /usr/local CTEST_TEST_TIMEOUT 3600 GMVReader_GMVREAD_LIB_DIR /home/r3/software/ParaView-v4.3.1-source/Utilities/VisItBridge/databases/GMV GMVReader_SKIP_DATARANGE_CALCU OFF MPI_C_INCLUDE_PATH /usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi MPI_C_LIBRARIES /usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so PARAVIEW_BUILD_QT_GUION PARAVIEW_ENABLE_CATALYST ON PARAVIEW_ENABLE_FFMPEG OFF PARAVIEW_ENABLE_PYTHON ON PARAVIEW_INSTALL_DEVELOPMENT_F OFF PARAVIEW_USE_DAX OFF PARAVIEW_USE_MPI ON PARAVIEW_USE_PISTON OFF PARAVIEW_USE_UNIFIED_BINDINGSOFF PARAVIEW_USE_VISITBRIDGE OFF Qt5Core_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Core Qt5Designer_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Designer Qt5Gui_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui Qt5Help_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Help Qt5Network_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Network Qt5PrintSupport_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5PrintSupport Qt5Test_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Test Qt5UiTools_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5UiTools Qt5Widgets_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Widgets Qt5Xml_DIR /usr/lib/x86_64-linux-gnu/cmake/Qt5Xml SURFACELIC_PLUGIN_TESTINGON VTK_PYTHON_VERSION 2 VTK_RENDERING_BACKENDOpenGL VTK_SMP_IMPLEMENTATION_TYPE Sequential VTK_USE_LARGE_DATA OFF XDMF_USE_BZIP2 OFF XDMF_USE_GZIPOFF -- 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 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
