Re: [Paraview] MPI Socket in use

2012-04-17 Thread Gena Bug
Hi!

Some time ago I tried to built ParaView with MPI and noticed that even if 
variables 
MPI_{CXX,C}_COMPILER pointed to the right compilers (mpicxx and mpicc 
respectively), the 
compilers from CMAKE_{CXX,C}_COMPILER variables were used (g++ and gcc).

Try turning on CMAKE_VERBOSE_MAKEFILE and look what exactly happens.

P.S. What is the difference between MPI_{CXX,C}_COMPILER and 
CMAKE_{CXX,C}_COMPILER 
variables?

On Tue April 17 2012 08:26:37 Adam Dershowitz, Ph.D., P.E. wrote:
 I am sure that I use ccmake and changed PARAVIEW_USE_MPI to ON, (I also
 enabled python and pointed to the open mpi compiler, so that it then
 filled in most of the variables for MPI, as the note explains).  Then I
 did configure and generate.  Finally I did make, and sudo make install. 
 All seemed to work fine, and paraview runs fine, with a single processor.
 I even went so far and to make a new, empty directory, and rebuilt it
 there.  With the same results. I have also tried to explicitly put in the
 correct path, just to make sure that there isn't some other pvserver
 around: mpirun -np 3 /home/dersh/projects/ParaView-bin/bin/pvserver
 with exactly the same results.
 I have gone back, and now I see that MPIEXEC_MAX_NUMPROCS and
 VTK_MPI_MAX_NUMPROCS are set to 2.  But, I get the same error if I try to
 run it with -np 2, so clearly just using MPI is failing.  A
 
 I realized that the problem is consistent with it not being built with MPI,
 but I definitely set it on.  Are there some other variables that have to
 be set?  Clearly something is not being built correctly, but I am not sure
 what it is.
 
 Thanks,
 
 --Adam
 
 On Apr 16, 2012, at 7:09 PM, Utkarsh Ayachit wrote:
  You may want to verify PARAVIEW_USE_MPI flag again and ensure that the
  pvserver you're running is indeed the one that has PARAVIEW_USE_MPI
  set to ON. The problem you're seeing is typical when ParaView not
  built with MPI.
  
  Utkarsh
  
  On Mon, Apr 16, 2012 at 8:10 PM, Adam Dershowitz
  
  adershow...@exponent.com wrote:
  I just built paraview on an opensuse linux box.  When I use the GUI, and
  a single connection it seems to work fine.  But, if I try to use
  multiple CPUs, or run with mpi, it fails.
  I do have OpenMPI installed.
  When I first started getting the error, I googled around some and found
  that maybe make install would help (I had been running it just in the
  build directory).  But I am getting the same error after installing.  I
  also added my openmpi libraries to LD_LIBRARY_PATH (when I first tried
  to run it I had other errors about a shared library).
  
  I did build with PARAVIEW_USE_MPI set to on.  It looks as though one
  pvserver will run, but any additional ones finds a port in use.  Clearly
  something is not right about how MPI is being handled, but I am not sure
  how to fix it.
  
  
  If I try mpirun, here is error I get:
  
  
  mpiexec -np 3  pvserver
  Waiting for client...
  Connection URL: cs://cfd:1
  Accepting connection(s): cfd:1
  Waiting for client...
  Connection URL: cs://cfd:1
  ERROR: In
  /home/dersh/projects/ParaView-3.14.1-Source/VTK/Common/vtkSocket.cxx,
  line 206
  vtkServerSocket (0xebd970): Socket error in call to bind. Address
  already in use.
  
  ERROR: In
  /home/dersh/projects/ParaView-3.14.1-Source/ParaViewCore/ClientServerCor
  e/vtkTCPNetworkAccessManager.cxx, line 343
  vtkTCPNetworkAccessManager (0x661800): Failed to set up server socket.
  
  Exiting...
  Waiting for client...
  Connection URL: cs://cfd:1
  ERROR: In
  /home/dersh/projects/ParaView-3.14.1-Source/VTK/Common/vtkSocket.cxx,
  line 206
  vtkServerSocket (0xebd970): Socket error in call to bind. Address
  already in use.
  
  ERROR: In
  /home/dersh/projects/ParaView-3.14.1-Source/ParaViewCore/ClientServerCor
  e/vtkTCPNetworkAccessManager.cxx, line 343
  vtkTCPNetworkAccessManager (0x661800): Failed to set up server socket.
  
  Exiting...
  
  - It seems that [at least] one of the processes that was started
  with mpirun did not invoke MPI_INIT before quitting (it is possible
  that more than one process did not invoke MPI_INIT -- mpirun was only
  notified of the first one, which was on node n0).
  
  mpirun can *only* be used with MPI programs (i.e., programs that
  invoke MPI_INIT and MPI_FINALIZE).  You can use the lamexec program
  to run non-MPI programs over the lambooted nodes.
  
  - mpirun failed with exit status 252
  
  And suggestions would be greatly appreciated.
  
  thanks,
  
  --Adam
  
  
  ___
  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
  
  Follow this link to subscribe/unsubscribe:
  

[Paraview] vtkSource as output of a paraview plugin filter

2012-04-17 Thread Boettcher, Prof. Dr. Peter
Dear All

 

I managed to write a PV plugin which fits a sphere to points selected on a poly 
data object. I can pass the sphere as the output of the filter - fine. But now 
I would like to  be able to interactively adjust the radius of the sphere to 
perform some measurements. The way I implemented the filter, this is not 
possible because the sphere is not a sphere to PV but a 3D object of any shape. 
So, is it possible to generate a vtkSource out of a PV plugin?

 

Any help would be highly appreciated.

 

Thanks - Peter.

 

-

Prof. Dr. Peter Böttcher, DipECVS

European Veterinary Specialist in Surgery

Fachtierarzt für Kleintierchirurgie

Klinik für Kleintiere 

Universität Leipzig 

An den Tierkliniken 23 

D-04103 Leipzig (Germany)

Tel: +49-341-9738700 

Fax: +49-341-9738799

Email: boettc...@kleintierklinik.uni-leipzig.de

 

___
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

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview


Re: [Paraview] MPI Socket in use

2012-04-17 Thread Utkarsh Ayachit
Do you mind posting your CMakeCache.txt file? Also do a ldd
libvtkParallel.so. Let's verify that vtkParallel is linking against
MPI libs.

Utkarsh

On Tue, Apr 17, 2012 at 12:26 AM, Adam Dershowitz, Ph.D., P.E.
adershow...@exponent.com wrote:
 I am sure that I use ccmake and changed PARAVIEW_USE_MPI to ON, (I also 
 enabled python and pointed to the open mpi compiler, so that it then filled 
 in most of the variables for MPI, as the note explains).  Then I did 
 configure and generate.  Finally I did make, and sudo make install.  All 
 seemed to work fine, and paraview runs fine, with a single processor.
 I even went so far and to make a new, empty directory, and rebuilt it there.  
 With the same results.
 I have also tried to explicitly put in the correct path, just to make sure 
 that there isn't some other pvserver around:
 mpirun -np 3 /home/dersh/projects/ParaView-bin/bin/pvserver
 with exactly the same results.
 I have gone back, and now I see that MPIEXEC_MAX_NUMPROCS and 
 VTK_MPI_MAX_NUMPROCS are set to 2.  But, I get the same error if I try to run 
 it with -np 2, so clearly just using MPI is failing.  A

 I realized that the problem is consistent with it not being built with MPI, 
 but I definitely set it on.  Are there some other variables that have to be 
 set?  Clearly something is not being built correctly, but I am not sure what 
 it is.

 Thanks,

 --Adam



 On Apr 16, 2012, at 7:09 PM, Utkarsh Ayachit wrote:

 You may want to verify PARAVIEW_USE_MPI flag again and ensure that the
 pvserver you're running is indeed the one that has PARAVIEW_USE_MPI
 set to ON. The problem you're seeing is typical when ParaView not
 built with MPI.

 Utkarsh

 On Mon, Apr 16, 2012 at 8:10 PM, Adam Dershowitz
 adershow...@exponent.com wrote:
 I just built paraview on an opensuse linux box.  When I use the GUI, and a
 single connection it seems to work fine.  But, if I try to use multiple
 CPUs, or run with mpi, it fails.
 I do have OpenMPI installed.
 When I first started getting the error, I googled around some and found that
 maybe make install would help (I had been running it just in the build
 directory).  But I am getting the same error after installing.  I also added
 my openmpi libraries to LD_LIBRARY_PATH (when I first tried to run it I had
 other errors about a shared library).

 I did build with PARAVIEW_USE_MPI set to on.  It looks as though one
 pvserver will run, but any additional ones finds a port in use.  Clearly
 something is not right about how MPI is being handled, but I am not sure how
 to fix it.


 If I try mpirun, here is error I get:


 mpiexec -np 3  pvserver
 Waiting for client...
 Connection URL: cs://cfd:1
 Accepting connection(s): cfd:1
 Waiting for client...
 Connection URL: cs://cfd:1
 ERROR: In
 /home/dersh/projects/ParaView-3.14.1-Source/VTK/Common/vtkSocket.cxx, line
 206
 vtkServerSocket (0xebd970): Socket error in call to bind. Address already in
 use.

 ERROR: In
 /home/dersh/projects/ParaView-3.14.1-Source/ParaViewCore/ClientServerCore/vtkTCPNetworkAccessManager.cxx,
 line 343
 vtkTCPNetworkAccessManager (0x661800): Failed to set up server socket.

 Exiting...
 Waiting for client...
 Connection URL: cs://cfd:1
 ERROR: In
 /home/dersh/projects/ParaView-3.14.1-Source/VTK/Common/vtkSocket.cxx, line
 206
 vtkServerSocket (0xebd970): Socket error in call to bind. Address already in
 use.

 ERROR: In
 /home/dersh/projects/ParaView-3.14.1-Source/ParaViewCore/ClientServerCore/vtkTCPNetworkAccessManager.cxx,
 line 343
 vtkTCPNetworkAccessManager (0x661800): Failed to set up server socket.

 Exiting...
 -
 It seems that [at least] one of the processes that was started with
 mpirun did not invoke MPI_INIT before quitting (it is possible that
 more than one process did not invoke MPI_INIT -- mpirun was only
 notified of the first one, which was on node n0).

 mpirun can *only* be used with MPI programs (i.e., programs that
 invoke MPI_INIT and MPI_FINALIZE).  You can use the lamexec program
 to run non-MPI programs over the lambooted nodes.
 -
 mpirun failed with exit status 252

 And suggestions would be greatly appreciated.

 thanks,

 --Adam


 ___
 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

 Follow this link to subscribe/unsubscribe:
 http://www.paraview.org/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

Follow this link to 

Re: [Paraview] PV 3.14.1 Linux crashes when trying to open a file

2012-04-17 Thread Utkarsh Ayachit
Richard,

The binaries have been updated. Please feel free to give them a try.

Thanks
Utkarsh

On Thu, Apr 12, 2012 at 7:48 AM, Richard GRENON richard.gre...@onera.fr wrote:
 Thank you, Utkarsh.

 Please, let me know when the updated binaries will be available and I'll
 tray again.

 Richard

 Utkarsh Ayachit a écrit :

 Doh! I forgot about the SVG plugin problem. I'll request the files to be
 updated soon. Thanks

 Utkarsh


 --
 Richard GRENON
 ONERA
 Departement d'Aerodynamique Appliquee - DAAP/ACI
 8 rue des Vertugadins
 92190 MEUDON - FRANCE
 phone : +33 1 46 73 42 17
 fax   : +33 1 46 73 41 46
 mailto:richard.gre...@onera.fr
 http://www.onera.fr

___
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

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview


Re: [Paraview] PV 3.14.1 Linux crashes when trying to open a file

2012-04-17 Thread Richard GRENON

Thank you, Utkarsh.

With these new binaries, PV 3.14.1 is working fine now.

Richard.

Utkarsh Ayachit a écrit :

Richard,

The binaries have been updated. Please feel free to give them a try.

Thanks
Utkarsh

On Thu, Apr 12, 2012 at 7:48 AM, Richard GRENON richard.gre...@onera.fr wrote:
  

Thank you, Utkarsh.

Please, let me know when the updated binaries will be available and I'll
tray again.

Richard

Utkarsh Ayachit a écrit :



Doh! I forgot about the SVG plugin problem. I'll request the files to be
updated soon. Thanks

Utkarsh

  

--
Richard GRENON
ONERA
Departement d'Aerodynamique Appliquee - DAAP/ACI
8 rue des Vertugadins
92190 MEUDON - FRANCE
phone : +33 1 46 73 42 17
fax   : +33 1 46 73 41 46
mailto:richard.gre...@onera.fr
http://www.onera.fr





  



--
Richard GRENON
ONERA
Departement d'Aerodynamique Appliquee - DAAP/ACI
8 rue des Vertugadins
92190 MEUDON - FRANCE
phone : +33 1 46 73 42 17
fax   : +33 1 46 73 41 46
mailto:richard.gre...@onera.fr
http://www.onera.fr

___
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

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview


Re: [Paraview] PV3.14.1 STL reader *could* be broken.

2012-04-17 Thread Utkarsh Ayachit
The fix is now in gerrit awaiting review:
http://review.source.kitware.com/#/c/5242/

Utkarsh

On Sat, Apr 14, 2012 at 10:37 AM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
 I was able to reproduce the issue. We'll track it down soon.

 Utkarsh

 On Sat, Apr 14, 2012 at 8:04 AM, Magician f_magic...@mac.com wrote:
 Hi Frank,


 I have same errors about STL Reader on ParaView 3.14.0.
 When I read STL data on Linux (CentOS 5.3), ParaView may be terminated 
 irregularly.
 If on Windows (Windows XP SP3), ParaView dumps errors, but still works.
 And these problems may be depends on ASCII STL data only.
 Binary STLs are imported safely.

 If you want to import STLs right now, how about using Binary format?
 Some ASCII to Binary STL converters are distributed on the web.

 And also I hope above bugs are modified.


 Magician


 On 2012/04/14, at 1:14, paraview-requ...@paraview.org wrote:

 Message: 1
 Date: Fri, 13 Apr 2012 18:14:18 +0200
 From: Albina, Frank frank.alb...@sauber-motorsport.com
 Subject: [Paraview] PV3.14.1 STL reader *could* be broken.
 To: paraview@paraview.org paraview@paraview.org
 Message-ID:
       589ceb614006334d93c1a48c1b1964c97f7b982...@srvmes03.spe-ch-md9.net
 Content-Type: text/plain; charset=us-ascii

 Dear all!

 I have just found out that the STL reader is broken under my Linux 64 bits 
 distro for both the PV3.14.1 binaries either compiled from source or 
 downloaded from paraview.org. The linux distribution I am using is SuSE 
 SLED10 SP2. The error message I am getting is:

 ERROR: In 
 /home/utkarsh/Kitware/superbuild/paraview/src/paraview/VTK/IO/vtkSTLReader.cxx,
  line 446
 vtkSTLReader (0x1bba420): STLReader error reading file: 
 susp-rr-tlink-E-0001-lhs.stl Premature EOF while reading end solid.


 *** glibc detected *** 
 /home/fal/Downloads/ParaView-3.14.1/lib/paraview-3.14/paraview: double free 
 or corruption (!prev): 0x0163c2f0 ***
 === Backtrace: =
 /lib64/libc.so.6[0x2b3d0dbb06de]
 /lib64/libc.so.6(__libc_free+0x6c)[0x2b3d0dbb1d5c]
 /lib64/libc.so.6(fclose+0x162)[0x2b3d0dba1cd2]
 /home/fal/Downloads/ParaView-3.14.1/lib/paraview-3.14/libvtkIO.so.pv3.14(_ZN12vtkSTLReader11RequestDataEP14vtkInformationPP20vtkInformationVectorS3_+0x24f)[0x2b3d098e7c2f]
 /home/fal/Downloads/ParaView-3.14.1/lib/paraview-3.14/libvtkPVVTKExtensions.so(_ZN19vtkFileSeriesReader11RequestDataEP14vtkInformationPP20vtkInformationVectorS3_+0x65)[0x2b3d006aefa5]
 /home/fal/Downloads/ParaView-3.14.1/lib/paraview-3.14/libvtkPVVTKExtensions.so(_ZN19vtkFileSeriesReader14ProcessRequestEP14vtkInformationPP20vtkInformationVectorS3_+0x169)[0x2b3d006adf39]
 /home/fal/Downloads/ParaView-3.14.1/lib/paraview-3.14/libvtkFiltering.so.pv3.14(_ZN12vtkExecutive13CallAlgorithmEP14vtkInformationiPP20vtkInformationVectorS3_+0x54)[0x2b3d0c26ee44]
 /home/fal/Downloads/ParaView-3.14.1/lib/paraview-3.14/libvtkFiltering.so.pv3.14(_ZN23vtkDemandDrivenPipeline11ExecuteDataEP14vtkInformationPP20vtkInformationVectorS3_+0x4c)[0x2b3d0c26313c]
 /home/fal/Downloads/ParaView-3.14.1/lib/paraview-3.14/libvtkFiltering.so.pv3.14(_ZN24vtkCompositeDataPipeline11ExecuteDataEP14vtkInformationPP20vtkInformationVectorS3_+0xa1)[0x2b3d0c245e41]
 /home/fal/Downloads/ParaView-3.14.1/lib/paraview-3.14/libvtkFiltering.so.pv3.14(_ZN23vtkDemandDrivenPipeline14ProcessRequestEP14vtkInformationPP20vtkInformationVectorS3_+0x293)[0x2b3d0c265eb3]
 /home/fal/Downloads/ParaView-3.14.1/lib/paraview-3.14/libvtkFiltering.so.pv3.14(_ZN32vtkStreamingDemandDrivenPipeline14ProcessRequestEP14vtkInformationPP20vtkInformationVectorS3_+0x209)[0x2b3d0c3d29e9]
 /home/fal/Downloads/ParaView-3.14.1/lib/paraview-3.14/libvtkFiltering.so.pv3.14(_ZN24vtkCompositeDataPipeline15ForwardUpstreamEP14vtkInformation+0x204)[0x2b3d0c244924]
 /home/fal/Downloads/ParaView-3.14.1/lib/paraview-3.14/libvtkFiltering.so.pv3.14(_ZN23vtkDemandDrivenPipeline14ProcessRequestEP14vtkInformationPP20vtkInformationVectorS3_+0x23c)[0x2b3d0c265e5c]
 /home/fal/Downloads/ParaView-3.14.1/lib/paraview-3.14/libvtkFiltering.so.pv3.14(_ZN32vtkStreamingDemandDrivenPipeline14ProcessRequestEP14vtkInformationPP20vtkInformationVectorS3_+0x209)[0x2b3d0c3d29e9]
 /home/fal/Downloads/ParaView-3.14.1/lib/paraview-3.14/libvtkFiltering.so.pv3.14(_ZN23vtkDemandDrivenPipeline10UpdateDataEi+0x9e)[0x2b3d0c2653fe]
 /home/fal/Downloads/ParaView-3.14.1/lib/paraview-3.14/libvtkFiltering.so.pv3.14(_ZN32vtkStreamingDemandDrivenPipeline6UpdateEi+0x7b)[0x2b3d0c3cdc4b]
 /home/fal/Downloads/ParaView-3.14.1/lib/paraview-3.14/libvtkPVServerImplementationCS.so(_Z23vtkSISourceProxyCommandP26vtkClientServerInterpreterP13vtkObjectBasePKcRK21vtkClientServerStreamRS5_+0x522)[0x2b3cfd00c8b2]
 /home/fal/Downloads/ParaView-3.14.1/lib/paraview-3.14/libvtkPVServerImplementationCS.so(_Z33vtkSIFileSeriesReaderProxyCommandP26vtkClientServerInterpreterP13vtkObjectBasePKcRK21vtkClientServerStreamRS5_+0x19b)[0x2b3cfd006ecb]
 

Re: [Paraview] MPI Socket in use

2012-04-17 Thread Utkarsh Ayachit
Are there multiple version of MPI installed by any chance?

Utkarsh

On Tue, Apr 17, 2012 at 2:51 PM, Adam Dershowitz
adershow...@exponent.com wrote:
 Attached are the results of ldd libvtkParallel.so (looks to me like it is
 linking MPI stuff).  And also CMakeCache.txt





 -Original Message-
 From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
 Sent: Tue 4/17/2012 6:14 AM
 To: Adam Dershowitz
 Cc: paraview@paraview.org
 Subject: Re: [Paraview] MPI Socket in use

 Do you mind posting your CMakeCache.txt file? Also do a ldd
 libvtkParallel.so. Let's verify that vtkParallel is linking against
 MPI libs.

 Utkarsh

 On Tue, Apr 17, 2012 at 12:26 AM, Adam Dershowitz, Ph.D., P.E.
 adershow...@exponent.com wrote:
 I am sure that I use ccmake and changed PARAVIEW_USE_MPI to ON, (I also
 enabled python and pointed to the open mpi compiler, so that it then filled
 in most of the variables for MPI, as the note explains).  Then I did
 configure and generate.  Finally I did make, and sudo make install.  All
 seemed to work fine, and paraview runs fine, with a single processor.
 I even went so far and to make a new, empty directory, and rebuilt it
 there.  With the same results.
 I have also tried to explicitly put in the correct path, just to make sure
 that there isn't some other pvserver around:
 mpirun -np 3 /home/dersh/projects/ParaView-bin/bin/pvserver
 with exactly the same results.
 I have gone back, and now I see that MPIEXEC_MAX_NUMPROCS and
 VTK_MPI_MAX_NUMPROCS are set to 2.  But, I get the same error if I try to
 run it with -np 2, so clearly just using MPI is failing.  A

 I realized that the problem is consistent with it not being built with
 MPI, but I definitely set it on.  Are there some other variables that have
 to be set?  Clearly something is not being built correctly, but I am not
 sure what it is.

 Thanks,

 --Adam



 On Apr 16, 2012, at 7:09 PM, Utkarsh Ayachit wrote:

 You may want to verify PARAVIEW_USE_MPI flag again and ensure that the
 pvserver you're running is indeed the one that has PARAVIEW_USE_MPI
 set to ON. The problem you're seeing is typical when ParaView not
 built with MPI.

 Utkarsh

 On Mon, Apr 16, 2012 at 8:10 PM, Adam Dershowitz
 adershow...@exponent.com wrote:
 I just built paraview on an opensuse linux box.  When I use the GUI, and
 a
 single connection it seems to work fine.  But, if I try to use multiple
 CPUs, or run with mpi, it fails.
 I do have OpenMPI installed.
 When I first started getting the error, I googled around some and found
 that
 maybe make install would help (I had been running it just in the build
 directory).  But I am getting the same error after installing.  I also
 added
 my openmpi libraries to LD_LIBRARY_PATH (when I first tried to run it I
 had
 other errors about a shared library).

 I did build with PARAVIEW_USE_MPI set to on.  It looks as though one
 pvserver will run, but any additional ones finds a port in use.  Clearly
 something is not right about how MPI is being handled, but I am not sure
 how
 to fix it.


 If I try mpirun, here is error I get:


 mpiexec -np 3  pvserver
 Waiting for client...
 Connection URL: cs://cfd:1
 Accepting connection(s): cfd:1
 Waiting for client...
 Connection URL: cs://cfd:1
 ERROR: In
 /home/dersh/projects/ParaView-3.14.1-Source/VTK/Common/vtkSocket.cxx,
 line
 206
 vtkServerSocket (0xebd970): Socket error in call to bind. Address
 already in
 use.

 ERROR: In

 /home/dersh/projects/ParaView-3.14.1-Source/ParaViewCore/ClientServerCore/vtkTCPNetworkAccessManager.cxx,
 line 343
 vtkTCPNetworkAccessManager (0x661800): Failed to set up server socket.

 Exiting...
 Waiting for client...
 Connection URL: cs://cfd:1
 ERROR: In
 /home/dersh/projects/ParaView-3.14.1-Source/VTK/Common/vtkSocket.cxx,
 line
 206
 vtkServerSocket (0xebd970): Socket error in call to bind. Address
 already in
 use.

 ERROR: In

 /home/dersh/projects/ParaView-3.14.1-Source/ParaViewCore/ClientServerCore/vtkTCPNetworkAccessManager.cxx,
 line 343
 vtkTCPNetworkAccessManager (0x661800): Failed to set up server socket.

 Exiting...

 -
 It seems that [at least] one of the processes that was started with
 mpirun did not invoke MPI_INIT before quitting (it is possible that
 more than one process did not invoke MPI_INIT -- mpirun was only
 notified of the first one, which was on node n0).

 mpirun can *only* be used with MPI programs (i.e., programs that
 invoke MPI_INIT and MPI_FINALIZE).  You can use the lamexec program
 to run non-MPI programs over the lambooted nodes.

 -
 mpirun failed with exit status 252

 And suggestions would be greatly appreciated.

 thanks,

 --Adam


 ___
 Powered by www.kitware.com

 Visit other Kitware open-source projects at
 http://www.kitware.com/opensource/opensource.html

 Please keep 

Re: [Paraview] MPI Socket in use

2012-04-17 Thread John Patchett
Sometimes, depending on the process launcher being used by MPI you don't
get the same environment in your current shell as you get from the
mpiexeced environment, since interactive shells behave differently than
non-interactive shells in regards to what dot files they read and/or don't
read.

you should try an
ssh ldd /home/dersh/projects/ParaView-bin/bin/pvserver
or
rsh ldd /home/dersh/projects/ParaView-bin/bin/pvserver
if you get the same output as
ldd /home/dersh/projects/ParaView-bin/bin/pvserver
I'm barking up the wrong tree.

Good Luck,
--John.

On Tue, Apr 17, 2012 at 1:02 PM, Utkarsh Ayachit 
utkarsh.ayac...@kitware.com wrote:

 Are there multiple version of MPI installed by any chance?

 Utkarsh

 On Tue, Apr 17, 2012 at 2:51 PM, Adam Dershowitz
 adershow...@exponent.com wrote:
  Attached are the results of ldd libvtkParallel.so (looks to me like it is
  linking MPI stuff).  And also CMakeCache.txt
 
 
 
 
 
  -Original Message-
  From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
  Sent: Tue 4/17/2012 6:14 AM
  To: Adam Dershowitz
  Cc: paraview@paraview.org
  Subject: Re: [Paraview] MPI Socket in use
 
  Do you mind posting your CMakeCache.txt file? Also do a ldd
  libvtkParallel.so. Let's verify that vtkParallel is linking against
  MPI libs.
 
  Utkarsh
 
  On Tue, Apr 17, 2012 at 12:26 AM, Adam Dershowitz, Ph.D., P.E.
  adershow...@exponent.com wrote:
  I am sure that I use ccmake and changed PARAVIEW_USE_MPI to ON, (I also
  enabled python and pointed to the open mpi compiler, so that it then
 filled
  in most of the variables for MPI, as the note explains).  Then I did
  configure and generate.  Finally I did make, and sudo make install.  All
  seemed to work fine, and paraview runs fine, with a single processor.
  I even went so far and to make a new, empty directory, and rebuilt it
  there.  With the same results.
  I have also tried to explicitly put in the correct path, just to make
 sure
  that there isn't some other pvserver around:
  mpirun -np 3 /home/dersh/projects/ParaView-bin/bin/pvserver
  with exactly the same results.
  I have gone back, and now I see that MPIEXEC_MAX_NUMPROCS and
  VTK_MPI_MAX_NUMPROCS are set to 2.  But, I get the same error if I try
 to
  run it with -np 2, so clearly just using MPI is failing.  A
 
  I realized that the problem is consistent with it not being built with
  MPI, but I definitely set it on.  Are there some other variables that
 have
  to be set?  Clearly something is not being built correctly, but I am not
  sure what it is.
 
  Thanks,
 
  --Adam
 
 
 
  On Apr 16, 2012, at 7:09 PM, Utkarsh Ayachit wrote:
 
  You may want to verify PARAVIEW_USE_MPI flag again and ensure that the
  pvserver you're running is indeed the one that has PARAVIEW_USE_MPI
  set to ON. The problem you're seeing is typical when ParaView not
  built with MPI.
 
  Utkarsh
 
  On Mon, Apr 16, 2012 at 8:10 PM, Adam Dershowitz
  adershow...@exponent.com wrote:
  I just built paraview on an opensuse linux box.  When I use the GUI,
 and
  a
  single connection it seems to work fine.  But, if I try to use
 multiple
  CPUs, or run with mpi, it fails.
  I do have OpenMPI installed.
  When I first started getting the error, I googled around some and
 found
  that
  maybe make install would help (I had been running it just in the
 build
  directory).  But I am getting the same error after installing.  I also
  added
  my openmpi libraries to LD_LIBRARY_PATH (when I first tried to run it
 I
  had
  other errors about a shared library).
 
  I did build with PARAVIEW_USE_MPI set to on.  It looks as though one
  pvserver will run, but any additional ones finds a port in use.
  Clearly
  something is not right about how MPI is being handled, but I am not
 sure
  how
  to fix it.
 
 
  If I try mpirun, here is error I get:
 
 
  mpiexec -np 3  pvserver
  Waiting for client...
  Connection URL: cs://cfd:1
  Accepting connection(s): cfd:1
  Waiting for client...
  Connection URL: cs://cfd:1
  ERROR: In
  /home/dersh/projects/ParaView-3.14.1-Source/VTK/Common/vtkSocket.cxx,
  line
  206
  vtkServerSocket (0xebd970): Socket error in call to bind. Address
  already in
  use.
 
  ERROR: In
 
 
 /home/dersh/projects/ParaView-3.14.1-Source/ParaViewCore/ClientServerCore/vtkTCPNetworkAccessManager.cxx,
  line 343
  vtkTCPNetworkAccessManager (0x661800): Failed to set up server socket.
 
  Exiting...
  Waiting for client...
  Connection URL: cs://cfd:1
  ERROR: In
  /home/dersh/projects/ParaView-3.14.1-Source/VTK/Common/vtkSocket.cxx,
  line
  206
  vtkServerSocket (0xebd970): Socket error in call to bind. Address
  already in
  use.
 
  ERROR: In
 
 
 /home/dersh/projects/ParaView-3.14.1-Source/ParaViewCore/ClientServerCore/vtkTCPNetworkAccessManager.cxx,
  line 343
  vtkTCPNetworkAccessManager (0x661800): Failed to set up server socket.
 
  Exiting...
 
 
 -
  It seems that [at least] 

[Paraview] setting the Glyph filter' SetScaleFactor value in a macro

2012-04-17 Thread Hal Canary
I am writing a ParaView macro to apply several glyph filters on the same 
data set.  Each filter wants to set its own SetScaleFactor value, but I 
am trying to override the default to make each glyph filter scale 
correctly with the other filters.  I can't seem to get the expected 
behavior out of the filter.


Here's my test case, as a ParaView macro:
vector1 = 'vector1'
scalar1 = 'scalar1'
vector2 = 'vector2'
scalar2 = 'scalar2'

s = Wavelet()
Show(s)
Hide(s)
s = Calculator(
Function='RTData*5-6',
ResultArrayName=scalar1 )
Show(s)
Hide(s)
s = Calculator(
Function='RTData*sin(coordsX)',
ResultArrayName=scalar2)
Show(s)
Hide(s)
s = Gradient(
Dimensionality='Three',
SelectInputScalars=['POINTS', 'scalar2'] )
Show(s)
Hide(s)
s = Gradient(
Dimensionality='Three',
SelectInputScalars=['POINTS', 'scalar1'] )
Show(s)
Hide(s)
s = Calculator(
Function='scalar1Gradient',
ResultArrayName=vector1 )
Show(s)
Hide(s)
s =  Calculator(
Function='scalar2Gradient',
ResultArrayName=vector2 )
Show(s)
Hide(s)
arrowGlyph = Glyph(
Input=s,
ScaleMode='scalar',
MaskPoints=0,
Vectors=['POINTS', vector1],
Scalars=['POINTS', scalar1],
GlyphTransform=Transform2,
GlyphType=Arrow,
Orient=1 )
arrowGlyph.SetScaleFactor = 0.01
Show(arrowGlyph)
arrowGlyph = Glyph(
Input=s,
ScaleMode='scalar',
MaskPoints=0,
Vectors=['POINTS', vector2],
Scalars=['POINTS', scalar2],
GlyphTransform=Transform2,
GlyphType=Arrow,
Orient=1 )
arrowGlyph.SetScaleFactor = 0.01
Show(arrowGlyph)
Render()

Any idea what I can do differently?

Thanks,

--
Hal Canary
http://cs.unc.edu/~hal/
___
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

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview


Re: [Paraview] MPI Socket in use

2012-04-17 Thread Adam Dershowitz, Ph.D., P.E.
The addresses are different, but the shared objects seem to be the same.

--Adam



On Apr 17, 2012, at 12:17 PM, John Patchett wrote:

 Sometimes, depending on the process launcher being used by MPI you don't get 
 the same environment in your current shell as you get from the mpiexeced 
 environment, since interactive shells behave differently than non-interactive 
 shells in regards to what dot files they read and/or don't read.  
 
 you should try an
 ssh ldd /home/dersh/projects/ParaView-bin/bin/pvserver
 or
 rsh ldd /home/dersh/projects/ParaView-bin/bin/pvserver
 if you get the same output as 
 ldd /home/dersh/projects/ParaView-bin/bin/pvserver
 I'm barking up the wrong tree.
 
 Good Luck,
 --John.
 
 On Tue, Apr 17, 2012 at 1:02 PM, Utkarsh Ayachit 
 utkarsh.ayac...@kitware.com wrote:
 Are there multiple version of MPI installed by any chance?
 
 Utkarsh
 
 On Tue, Apr 17, 2012 at 2:51 PM, Adam Dershowitz
 adershow...@exponent.com wrote:
  Attached are the results of ldd libvtkParallel.so (looks to me like it is
  linking MPI stuff).  And also CMakeCache.txt
 
 
 
 
 
  -Original Message-
  From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
  Sent: Tue 4/17/2012 6:14 AM
  To: Adam Dershowitz
  Cc: paraview@paraview.org
  Subject: Re: [Paraview] MPI Socket in use
 
  Do you mind posting your CMakeCache.txt file? Also do a ldd
  libvtkParallel.so. Let's verify that vtkParallel is linking against
  MPI libs.
 
  Utkarsh
 
  On Tue, Apr 17, 2012 at 12:26 AM, Adam Dershowitz, Ph.D., P.E.
  adershow...@exponent.com wrote:
  I am sure that I use ccmake and changed PARAVIEW_USE_MPI to ON, (I also
  enabled python and pointed to the open mpi compiler, so that it then filled
  in most of the variables for MPI, as the note explains).  Then I did
  configure and generate.  Finally I did make, and sudo make install.  All
  seemed to work fine, and paraview runs fine, with a single processor.
  I even went so far and to make a new, empty directory, and rebuilt it
  there.  With the same results.
  I have also tried to explicitly put in the correct path, just to make sure
  that there isn't some other pvserver around:
  mpirun -np 3 /home/dersh/projects/ParaView-bin/bin/pvserver
  with exactly the same results.
  I have gone back, and now I see that MPIEXEC_MAX_NUMPROCS and
  VTK_MPI_MAX_NUMPROCS are set to 2.  But, I get the same error if I try to
  run it with -np 2, so clearly just using MPI is failing.  A
 
  I realized that the problem is consistent with it not being built with
  MPI, but I definitely set it on.  Are there some other variables that have
  to be set?  Clearly something is not being built correctly, but I am not
  sure what it is.
 
  Thanks,
 
  --Adam
 
 
 
  On Apr 16, 2012, at 7:09 PM, Utkarsh Ayachit wrote:
 
  You may want to verify PARAVIEW_USE_MPI flag again and ensure that the
  pvserver you're running is indeed the one that has PARAVIEW_USE_MPI
  set to ON. The problem you're seeing is typical when ParaView not
  built with MPI.
 
  Utkarsh
 
  On Mon, Apr 16, 2012 at 8:10 PM, Adam Dershowitz
  adershow...@exponent.com wrote:
  I just built paraview on an opensuse linux box.  When I use the GUI, and
  a
  single connection it seems to work fine.  But, if I try to use multiple
  CPUs, or run with mpi, it fails.
  I do have OpenMPI installed.
  When I first started getting the error, I googled around some and found
  that
  maybe make install would help (I had been running it just in the build
  directory).  But I am getting the same error after installing.  I also
  added
  my openmpi libraries to LD_LIBRARY_PATH (when I first tried to run it I
  had
  other errors about a shared library).
 
  I did build with PARAVIEW_USE_MPI set to on.  It looks as though one
  pvserver will run, but any additional ones finds a port in use.  Clearly
  something is not right about how MPI is being handled, but I am not sure
  how
  to fix it.
 
 
  If I try mpirun, here is error I get:
 
 
  mpiexec -np 3  pvserver
  Waiting for client...
  Connection URL: cs://cfd:1
  Accepting connection(s): cfd:1
  Waiting for client...
  Connection URL: cs://cfd:1
  ERROR: In
  /home/dersh/projects/ParaView-3.14.1-Source/VTK/Common/vtkSocket.cxx,
  line
  206
  vtkServerSocket (0xebd970): Socket error in call to bind. Address
  already in
  use.
 
  ERROR: In
 
  /home/dersh/projects/ParaView-3.14.1-Source/ParaViewCore/ClientServerCore/vtkTCPNetworkAccessManager.cxx,
  line 343
  vtkTCPNetworkAccessManager (0x661800): Failed to set up server socket.
 
  Exiting...
  Waiting for client...
  Connection URL: cs://cfd:1
  ERROR: In
  /home/dersh/projects/ParaView-3.14.1-Source/VTK/Common/vtkSocket.cxx,
  line
  206
  vtkServerSocket (0xebd970): Socket error in call to bind. Address
  already in
  use.
 
  ERROR: In
 
  /home/dersh/projects/ParaView-3.14.1-Source/ParaViewCore/ClientServerCore/vtkTCPNetworkAccessManager.cxx,
  line 343
  vtkTCPNetworkAccessManager (0x661800): Failed to 

Re: [Paraview] MPI Socket in use

2012-04-17 Thread Adam Dershowitz, Ph.D., P.E.
Got it
Yes, there were, but I had not realized it before (not sure why they were 
floating around).  If I use the correct runmpi it now works.

Thank you much!



--Adam



On Apr 17, 2012, at 12:02 PM, Utkarsh Ayachit wrote:

 Are there multiple version of MPI installed by any chance?
 
 Utkarsh
 
 On Tue, Apr 17, 2012 at 2:51 PM, Adam Dershowitz
 adershow...@exponent.com wrote:
 Attached are the results of ldd libvtkParallel.so (looks to me like it is
 linking MPI stuff).  And also CMakeCache.txt
 
 
 
 
 
 -Original Message-
 From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
 Sent: Tue 4/17/2012 6:14 AM
 To: Adam Dershowitz
 Cc: paraview@paraview.org
 Subject: Re: [Paraview] MPI Socket in use
 
 Do you mind posting your CMakeCache.txt file? Also do a ldd
 libvtkParallel.so. Let's verify that vtkParallel is linking against
 MPI libs.
 
 Utkarsh
 
 On Tue, Apr 17, 2012 at 12:26 AM, Adam Dershowitz, Ph.D., P.E.
 adershow...@exponent.com wrote:
 I am sure that I use ccmake and changed PARAVIEW_USE_MPI to ON, (I also
 enabled python and pointed to the open mpi compiler, so that it then filled
 in most of the variables for MPI, as the note explains).  Then I did
 configure and generate.  Finally I did make, and sudo make install.  All
 seemed to work fine, and paraview runs fine, with a single processor.
 I even went so far and to make a new, empty directory, and rebuilt it
 there.  With the same results.
 I have also tried to explicitly put in the correct path, just to make sure
 that there isn't some other pvserver around:
 mpirun -np 3 /home/dersh/projects/ParaView-bin/bin/pvserver
 with exactly the same results.
 I have gone back, and now I see that MPIEXEC_MAX_NUMPROCS and
 VTK_MPI_MAX_NUMPROCS are set to 2.  But, I get the same error if I try to
 run it with -np 2, so clearly just using MPI is failing.  A
 
 I realized that the problem is consistent with it not being built with
 MPI, but I definitely set it on.  Are there some other variables that have
 to be set?  Clearly something is not being built correctly, but I am not
 sure what it is.
 
 Thanks,
 
 --Adam
 
 
 
 On Apr 16, 2012, at 7:09 PM, Utkarsh Ayachit wrote:
 
 You may want to verify PARAVIEW_USE_MPI flag again and ensure that the
 pvserver you're running is indeed the one that has PARAVIEW_USE_MPI
 set to ON. The problem you're seeing is typical when ParaView not
 built with MPI.
 
 Utkarsh
 
 On Mon, Apr 16, 2012 at 8:10 PM, Adam Dershowitz
 adershow...@exponent.com wrote:
 I just built paraview on an opensuse linux box.  When I use the GUI, and
 a
 single connection it seems to work fine.  But, if I try to use multiple
 CPUs, or run with mpi, it fails.
 I do have OpenMPI installed.
 When I first started getting the error, I googled around some and found
 that
 maybe make install would help (I had been running it just in the build
 directory).  But I am getting the same error after installing.  I also
 added
 my openmpi libraries to LD_LIBRARY_PATH (when I first tried to run it I
 had
 other errors about a shared library).
 
 I did build with PARAVIEW_USE_MPI set to on.  It looks as though one
 pvserver will run, but any additional ones finds a port in use.  Clearly
 something is not right about how MPI is being handled, but I am not sure
 how
 to fix it.
 
 
 If I try mpirun, here is error I get:
 
 
 mpiexec -np 3  pvserver
 Waiting for client...
 Connection URL: cs://cfd:1
 Accepting connection(s): cfd:1
 Waiting for client...
 Connection URL: cs://cfd:1
 ERROR: In
 /home/dersh/projects/ParaView-3.14.1-Source/VTK/Common/vtkSocket.cxx,
 line
 206
 vtkServerSocket (0xebd970): Socket error in call to bind. Address
 already in
 use.
 
 ERROR: In
 
 /home/dersh/projects/ParaView-3.14.1-Source/ParaViewCore/ClientServerCore/vtkTCPNetworkAccessManager.cxx,
 line 343
 vtkTCPNetworkAccessManager (0x661800): Failed to set up server socket.
 
 Exiting...
 Waiting for client...
 Connection URL: cs://cfd:1
 ERROR: In
 /home/dersh/projects/ParaView-3.14.1-Source/VTK/Common/vtkSocket.cxx,
 line
 206
 vtkServerSocket (0xebd970): Socket error in call to bind. Address
 already in
 use.
 
 ERROR: In
 
 /home/dersh/projects/ParaView-3.14.1-Source/ParaViewCore/ClientServerCore/vtkTCPNetworkAccessManager.cxx,
 line 343
 vtkTCPNetworkAccessManager (0x661800): Failed to set up server socket.
 
 Exiting...
 
 -
 It seems that [at least] one of the processes that was started with
 mpirun did not invoke MPI_INIT before quitting (it is possible that
 more than one process did not invoke MPI_INIT -- mpirun was only
 notified of the first one, which was on node n0).
 
 mpirun can *only* be used with MPI programs (i.e., programs that
 invoke MPI_INIT and MPI_FINALIZE).  You can use the lamexec program
 to run non-MPI programs over the lambooted nodes.
 
 -
 mpirun failed with exit 

[Paraview] Fwd: Is it a BUG with temporal filters or I am missing something? [Developers, could you please verify if this is a bug or not?]

2012-04-17 Thread Mohamad M. Nasr-Azadani
Hi guys, I have asked this question few days ago. Has anyone seen the same
problem?


-- Forwarded message --
From: Mohamad M. Nasr-Azadani mmn...@gmail.com
Date: Mon, Apr 9, 2012 at 2:41 PM
Subject: Is it a BUG with temporal filters or I am missing something?
[Developers, could you please verify if this is a bug or not?]
To: paraview@paraview.org


Hi,

This is what I am doing:
Load a time-aware PVD file like this:

?xml version=1.0?
 VTKFile type=Collection version=0.1 byte_order=LittleEndian
compressor=vtkZLibDataCompressor
   Collection
DataSet timestep=0.0 group= part=0 file=vel_vec_0.vtr/
DataSet timestep=0.2 group= part=0 file=vel_vec_1.vtr/
DataSet timestep=0.4 group= part=0 file=vel_vec_2.vtr/
DataSet timestep=0.6 group= part=0 file=vel_vec_3.vtr/
DataSet timestep=0.8 group= part=0 file=vel_vec_4.vtr/
DataSet timestep=1.0 group= part=0 file=vel_vec_5.vtr/
DataSet timestep=1.2 group= part=0 file=vel_vec_6.vtr/
DataSet timestep=1.4 group= part=0 file=vel_vec_7.vtr/
DataSet timestep=1.6 group= part=0 file=vel_vec_8.vtr/
DataSet timestep=1.8 group= part=0 file=vel_vec_9.vtr/
DataSet timestep=2.0 group= part=0 file=vel_vec_10.vtr/
  /Collection
/VTKFile

Apply any of the 'temporal filters' including
-Temporal Cache w/ Cache size = 2
-Temporal Interpolator w/ Discrete Time Step Interval = 0.1
-Temporal Shift Scale w/ [default values]

to the loaded dataset.
I just press the play button on the the animation toolbar and it either
gives me this error message or crashes.

  ERROR: In
/home/utkarsh/Kitware/superbuild/paraview/src/paraview/VTK/Filtering/vtkStreamingDemandDrivenPipeline.cxx,
line 934

vtkPVPostFilterExecutive (0x2d5d190): No maximum number of pieces has been
set in the information for output port 0 on algorithm
vtkPVPostFilter(0x2d26830).

I am using PV 3.14.0 (and .1) on both Ubuntu and Windows.

Has anyone experienced the same problem?
If the developers are reading this, could you please let me know if that is
a bug or not? I really need to decide soon wether or not to use PV for
post-processing of some particle-tracing part.

Thanks in advance,
Mohamad


A follow up on this problem.
if anyone is interested, I think it is a bug with the *rectilinear* vtk
reader (or any derivatives).
I converted the same dataset to *.vtu format, and read the file series. Did
the same experiment with temporal filters and everything looked perfectly
fine. No error message or crashing.
___
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

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview