Re: [Paraview] 2D contours on a slice for a 3D data

[Pradeep Jha]

Hello,I have a follow up question on similar lines. In the 3D cube that I have, I have a velocity vector data. Is it possible that I can show the vector field coming out of the sliced plane? i.e. at each point of the sliced plane, an arrow coming out of the sliced plane representing the magnitude and direction of the velocity vector at the particular point on the plane. Something like the attached image. I hope I made myself clear.  Thanks in advance,PradeepLe 8 janv. 2013 à 10:06, Pradeep Jha  a écrit :Hello,thanks everyone. It seems like it is working.PradeepLe 8 janv. 2013 à 02:58, "Moreland, Kenneth"  a écrit :






I'd like to expand upon on Sebastian's correct but short answer.




The contour filter is not going to give you the contours that you are asking for.  The contour filter is going to extract the geometry representing exactly the locations of the contours and nothing else.  As such, if you contour a slice through your data
 (or somewhat equivalently take a slice through your contour), you will get a bunch of lines representing where in the plane the field equals the isovalue you gave. So rather than getting a plane of colors as in your second example, you get the lines at the
 interface between colors.


The representation of contours you are asking for is a bit different.  You want the entire geometry of the plane drawn and colored in such a way that the contours are represented as sharp transitions in the colors.  Since you are never actually extracting
 the geometry of the contours themselves, running the contour filter is not appropriate for this.  Instead, as Sebastian said, you want to make a slice through the data and provide a coloring that represents the contours.  To set up these colors, first make
 sure the slice is colored by the scaler value you want contours of.  Then click the edit color map button to pull up the color scale editor.  Click on the "Use Discrete Colors" option (you will need to turn on the "advanced" properties if you are using the
 most recent version of ParaView) and then set the resolution to be set to the number of color bands you want.


-Ken




From: Sebastien Jourdain 
Date: Monday, January 7, 2013 6:53 AM
To: Pradeep Jha 
Cc: "paraview@paraview.org" 
Subject: [EXTERNAL] Re: [Paraview] 2D contours on a slice for a 3D data






It seems that you just want to slice your data and eventually reduce the number of color in your lookup table so you see distinct color bands.


Seb



On Sun, Jan 6, 2013 at 10:16 PM, Pradeep Jha 
 wrote:

Hello,


I have a 3D data (the geometry is a simple cube). I am interested in looking at the 2D contour plots of a variable on a sliced plane.  Below I have attached two figures. The first figure shows the slice. It only shows the cross-section of the iso-surfaces
 of the variable I loaded in 3D. I am interested in getting a contour plot, like the 2nd figure (I got this image randomly from the net), of the variable values on the slice. 


I hope I made myself clear :) Any ideas how I can do it?
Thank you,
Pradeep








___
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 subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] HDF5 and Paraview

[Pradeep Jha]

Hello,

thanks for the replies. I managed to get it working.

Pradeep

Le 7 janv. 2013 à 18:27, Jens Kleimann  a écrit :

> On 04.01.2013 04:19, Pradeep Jha wrote:
>> Hello Jens,
>> thanks for the response. It explained a lot. 
> 
> Pleasure!
> 
>> I have been reading up about XDMF and am trying to implement it. My 
>> filename.h5 file just contains a scalar value for 512*512*512 grid points in 
>> a structured uniform cube. I don't store any grid coordinates information in 
>> any files. But all the material I have been reading for XDMF mention that I 
>> have to give grid information. Is there a simple way of conveying my uniform 
>> grid structure to XDMF or should I create a file with grid coordinates and 
>> make XDMF read it?
> 
> In this simple case, you do not need a grid file with coordinates, but you 
> need to specify the type of grid and its origin and cell size so PV knows 
> where to locate the cells and what numbers to draw along the axes. The 
> (untested) sample file below should give you an idea of what is needed. This 
> grid cube has its origin at [0,0,0] and uses dx=dy=dz=0.1, i.e. it occupies 
> the cubic volume [0, 51.2]^3 in 3D space. Note that the grid size (513^3) has 
> to be larger than the number of data elements by one per direction because it 
> specifies the location of _nodes_ (corner vertices) of a cell.
> You will need to adapt the path and name of the HDF5 file and the location of 
> your scalar data field within that file, the former being separated from the 
> latter by a ":".
> 
> Good luck!
> Jens.
> 
>  BEGIN file scalar_sample.xmf ===
> 
> 
> 
>  
>
>  
>  
>  
>   
> 0 0 0
>
>
> 0.1 0.1 0.1
>
>  
>  
>   
> my_HDF_file.h5:/name_of_scalar_in_h5
>   
>  
>
>  
> 
> = END file scalar_sample.xmf 

___
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] Linker error with OpenMPI 1.6.2

[Stephan Rogge]

Utkarsh,

Thank you for that hint. I've added openlib-pal.lib and openlib-rte.lib to
the linker list.  No success. The linker error remains.

But after some research I found an advice to add the definition
"OMPI_IMPORTS" to pre-processor:

CMAKE_CXX_FLAGS = ... /D "OMPI_IMPORTS"
CMAKE_C_FLAGS = ... /D "OMPI_IMPORTS"  => Maybe not required

This solves my problem and ninja is running until the end :-).

Is this an individual problem? I wonder if someone else had this error too.

Best regards,
Stephan


___
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

[Paraview] Error building ParaView with OSMesa and Python

[Ian Krukow]

Hello,

I am trying to build ParaView 3.98.0 with OSMesa and Python 2.7 on a 
Linux cluster (Red Hat Enterprise). According to the Wiki 
(http://paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D), I do the 
following:


ccmake -D PARAVIEW_BUILD_QT_GUI:BOOL=OFF -D VTK_USE_X:BOOL=OFF -D 
VTK_OPENGL_HAS_OSMESA:BOOL=ON {PARAVIEW_SOURCE_DIR}

Specify OSMesa paths
configure
generate
make

So far, Python is disabled, and everything works fine. Then I turn on 
the parameter PARAVIEW_ENABLE_PYTHON. On my laptop (Ubuntu 12.04), 
everything is still fine. But on the cluster, I run into the following 
error with the make command:


[iankruko@dnode192 ParaView-3.98.0-OSMesa]$ make
[  0%] Built target vtksys
[  0%] Built target vtkWrappingTools
[  0%] Built target vtkWrapHierarchy
[  1%] Built target vtkCommonCore
[  1%] Built target vtkWrapPythonInit
Linking CXX shared library ../../../lib/libvtkWrappingPython27-pv3.98.so
CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function 
`vtkPythonArgs::BuildValue(vtkUnicodeString const&)':
/home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.h:692: 
undefined reference to `PyUnicodeUCS2_DecodeUTF8'
CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function `bool 
vtkPythonGetUnsignedLongLongValue(_object*, unsigned 
long long&)':
/home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.cxx:106: 
undefined reference to `PyErr_WarnEx'
CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function 
`vtkPythonGetValue(_object*, long&)':
/home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.cxx:50: 
undefined reference to `PyErr_WarnEx'
CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function `bool 
vtkPythonGetLongLongValue(_object*, long long&)':
/home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.cxx:92: 
undefined reference to `PyErr_WarnEx'
CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function 
`vtkPythonGetValue(_object*, unsigned long&)':
/home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.cxx:59: 
undefined reference to `PyErr_WarnEx'
CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function `bool 
vtkPythonGetStringValue(_object*, char const*&, char const*)':
/home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.cxx:161: 
undefined reference to `_PyUnicodeUCS2_AsDefaultEncodedString'
CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function `bool 
vtkPythonGetStringValue(_object*, char*&, char const*)':
/home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.cxx:161: 
undefined reference to `_PyUnicodeUCS2_AsDefaultEncodedString'
CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function 
`vtkPythonGetValue(_object*, vtkUnicodeString&)':
/home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.cxx:311: 
undefined reference to `PyUnicodeUCS2_AsUTF8String'
CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function 
`vtkPythonGetStdStringValue(_object*, std::basic_stringstd::char_traits, std::allocator >&, char const*)':
/home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.cxx:196: 
undefined reference to `_PyUnicodeUCS2_AsDefaultEncodedString'
CMakeFiles/vtkWrappingPython.dir/vtkPythonUtil.cxx.o: In function 
`vtkPythonUtil::VariantHash(vtkVariant const*)':
/home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonUtil.cxx:850: 
undefined reference to `PyUnicodeUCS2_DecodeUTF8'
CMakeFiles/vtkWrappingPython.dir/PyVTKMutableObject.cxx.o: In function 
`PyVTKMutableObject_Index':
/home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/PyVTKMutableObject.cxx:464: 
undefined reference to `PyNumber_Index'
CMakeFiles/vtkWrappingPython.dir/PyVTKMutableObject.cxx.o: In function 
`PyVTKMutableObject_Hex':
/home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/PyVTKMutableObject.cxx:385: 
undefined reference to `PyNumber_ToBase'
CMakeFiles/vtkWrappingPython.dir/PyVTKMutableObject.cxx.o: In function 
`PyVTKMutableObject_Oct':
/home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/PyVTKMutableObject.cxx:403: 
undefined reference to `PyNumber_ToBase'
CMakeFiles/vtkWrappingPython.dir/PyVTKMutableObject.cxx.o:(.data.rel+0x78): 
undefined reference to `PyObject_HashNotImplemented'

collect2: ld gab 1 als Ende-Status zurück
make[2]: *** [lib/libvtkWrappingPython27-pv3.98.so.1] Fehler 1
make[1]: *** [VTK/Wrapping/Python/CMakeFiles/vtkWrappingPython.dir/all] 
Fehler 2

make: *** [all] Fehler 2

I do not know, where the essential difference between the two systems 
is, neither where to look for it. Can anybody help me?


Thanks,
Ian
___
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/Par

Re: [Paraview] Linker error with OpenMPI 1.6.2

[Utkarsh Ayachit]

Ah, yea, that makes sense. On Windows shared builds with OpenMPI
(built shared), those are indeed needed to be set.

On Tue, Jan 8, 2013 at 6:05 AM, Stephan Rogge
 wrote:
> Utkarsh,
>
> Thank you for that hint. I've added openlib-pal.lib and openlib-rte.lib to
> the linker list.  No success. The linker error remains.
>
> But after some research I found an advice to add the definition
> "OMPI_IMPORTS" to pre-processor:
>
> CMAKE_CXX_FLAGS = ... /D "OMPI_IMPORTS"
> CMAKE_C_FLAGS = ... /D "OMPI_IMPORTS"  => Maybe not required
>
> This solves my problem and ninja is running until the end :-).
>
> Is this an individual problem? I wonder if someone else had this error too.
>
> Best regards,
> Stephan
>
>
> ___
> 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 subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] ParaView from git, make fail on OpenSUSE 12.2

[Utkarsh Ayachit]

Not sure what could be going wrong. Try deleting your
"~/.config/ParaView" directory, you may want to copy it over to some
other place, just in case.

Utkarsh

On Mon, Jan 7, 2013 at 12:28 PM, Pei-Ying Hsieh  wrote:
> #0  0x76e4cc55 in pqApplicationCore::settings() () from
> /home/phsieh/projects/paraview-devel/lib/paraview-3.98/libvtkpqCore-pv3.98.so.1
___
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] 2D contours on a slice for a 3D data

[Moreland, Kenneth]

Try applying the glyph filter to the output of the slice filter.

-Ken

From: Pradeep Jha 
mailto:pradeep.kumar@gmail.com>>
Date: Tuesday, January 8, 2013 1:03 AM
To: Kenneth Moreland mailto:kmo...@sandia.gov>>
Cc: Sebastien Jourdain 
mailto:sebastien.jourd...@kitware.com>>, 
"paraview@paraview.org" 
mailto:paraview@paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] 2D contours on a slice for a 3D data

Hello,

I have a follow up question on similar lines.

In the 3D cube that I have, I have a velocity vector data. Is it possible that 
I can show the vector field coming out of the sliced plane? i.e. at each point 
of the sliced plane, an arrow coming out of the sliced plane representing the 
magnitude and direction of the velocity vector at the particular point on the 
plane. Something like the attached image.

I hope I made myself clear.
Thanks in advance,
Pradeep


[cid:03028CCC-C6DF-47CA-868E-0D61BA1B21C1]


Le 8 janv. 2013 à 10:06, Pradeep Jha 
mailto:pradeep.kumar@gmail.com>> a écrit :

Hello,

thanks everyone. It seems like it is working.

Pradeep

Le 8 janv. 2013 à 02:58, "Moreland, Kenneth" 
mailto:kmo...@sandia.gov>> a écrit :

I'd like to expand upon on Sebastian's correct but short answer.

The contour filter is not going to give you the contours that you are asking 
for.  The contour filter is going to extract the geometry representing exactly 
the locations of the contours and nothing else.  As such, if you contour a 
slice through your data (or somewhat equivalently take a slice through your 
contour), you will get a bunch of lines representing where in the plane the 
field equals the isovalue you gave. So rather than getting a plane of colors as 
in your second example, you get the lines at the interface between colors.

The representation of contours you are asking for is a bit different.  You want 
the entire geometry of the plane drawn and colored in such a way that the 
contours are represented as sharp transitions in the colors.  Since you are 
never actually extracting the geometry of the contours themselves, running the 
contour filter is not appropriate for this.  Instead, as Sebastian said, you 
want to make a slice through the data and provide a coloring that represents 
the contours.  To set up these colors, first make sure the slice is colored by 
the scaler value you want contours of.  Then click the edit color map button to 
pull up the color scale editor.  Click on the "Use Discrete Colors" option (you 
will need to turn on the "advanced" properties if you are using the most recent 
version of ParaView) and then set the resolution to be set to the number of 
color bands you want.

-Ken

From: Sebastien Jourdain 
mailto:sebastien.jourd...@kitware.com>>
Date: Monday, January 7, 2013 6:53 AM
To: Pradeep Jha 
mailto:pradeep.kumar@gmail.com>>
Cc: "paraview@paraview.org" 
mailto:paraview@paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] 2D contours on a slice for a 3D data

It seems that you just want to slice your data and eventually reduce the number 
of color in your lookup table so you see distinct color bands.

Seb


On Sun, Jan 6, 2013 at 10:16 PM, Pradeep Jha 
mailto:pradeep.kumar@gmail.com>> wrote:
Hello,

I have a 3D data (the geometry is a simple cube). I am interested in looking at 
the 2D contour plots of a variable on a sliced plane.  Below I have attached 
two figures. The first figure shows the slice. It only shows the cross-section 
of the iso-surfaces of the variable I loaded in 3D. I am interested in getting 
a contour plot, like the 2nd figure (I got this image randomly from the net), 
of the variable values on the slice.

I hope I made myself clear :) Any ideas how I can do it?
Thank you,
Pradeep





___
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 subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] Force remote rendering on pvserver

[Utkarsh Ayachit]

Kit,

> Am I correct in thinking that OSMesa is required if there is
> no graphics card on the server?

For the most part, yes.

> What about if there is a graphics card and
> display for the server but no one using the display (i.e. a remote
> workstation I can access through SSH)? This is one situation I have.
> I guess
> a similar situation might occur if the pvserver is in fact a remote HPC
> server with high end GPU's you would like to use for rendering?

In that case you shouldn't use OSMEsa, but then your user will need
access to X. Possibilities are using a Xvfb or VNC or something
similar.

Utkarsh
___
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] Linker error with OpenMPI 1.6.2

[Bruno Santos]

Greetings,

I've managed to get ParaView's SuperBuild working/building on Windows, 
which uses Open-MPI 1.6.2 by default on ParaView 3.98.0.


From ParaView's resulting "CMakeCache.txt", these were defined for the 
C and CXX flags: /DOMPI_IMPORTS /DOPAL_IMPORTS /DORTE_IMPORTS


These are the binaries and libraries that were included:

   MPIEXEC:FILEPATH=P:/install/bin/mpiexec.exe
   MPI_CXX_COMPILER:FILEPATH=P:/install/bin/mpicxx.exe
   MPI_CXX_INCLUDE_PATH:STRING=P:/install/include
   MPI_CXX_LIBRARIES:STRING=P:/install/lib/libmpi_cxx.lib
   MPI_C_COMPILER:FILEPATH=P:/install/bin/mpicc.exe
   MPI_C_INCLUDE_PATH:STRING=P:/install/include
   
MPI_C_LIBRARIES:STRING=P:/install/lib/libmpi.lib;P:/install/lib/libopen-rte.lib;P:/install/lib/libopen-pal.lib;advapi32.lib;Ws2_32.lib;shlwapi.lib
   MPI_LIBRARY:FILEPATH=P:/install/lib/libmpi_cxx.lib

Hope this helps!


For those who may be curious about the modifications: 
http://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes3980
When I've got some more time, I'll try to push some of these mods to the 
SuperBuild's Gerrit.


Best regards,
Bruno

On 08-01-2013 14:43, Utkarsh Ayachit wrote:

Ah, yea, that makes sense. On Windows shared builds with OpenMPI
(built shared), those are indeed needed to be set.

On Tue, Jan 8, 2013 at 6:05 AM, Stephan Rogge
 wrote:

Utkarsh,

Thank you for that hint. I've added openlib-pal.lib and openlib-rte.lib to
the linker list.  No success. The linker error remains.

But after some research I found an advice to add the definition
"OMPI_IMPORTS" to pre-processor:

CMAKE_CXX_FLAGS = ... /D "OMPI_IMPORTS"
CMAKE_C_FLAGS = ... /D "OMPI_IMPORTS"  => Maybe not required

This solves my problem and ninja is running until the end :-).

Is this an individual problem? I wonder if someone else had this error too.

Best regards,
Stephan


___
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 subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview





--
http://www.bluecape.com.pt

blueCAPE Lda - CAE solutions
Rua Fonte dos Corvos, n.29
Casais da Serra
2665-305 Milharado
PORTUGAL

(+351) 219 755 345  Tel.
(+351) 219 755 345  Fax
(+351) 926 008 657  Mob.

___
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] Linker error with OpenMPI 1.6.2

[Yumin Yuan]

Hi Bruno,

Just want to be clear on this. With Paraview's superbuild (pulling
openmpi-1.6.2 by default), do you still need to modify anything to
build? Looking at paraview's nightly dashboard
(http://open.cdash.org/index.php?project=ParaView), the superbuilds on
Windows work properly. I was also able to use paraview's superbuild
successfully with Ninja on Win7-vs9 for 3.98.0 without modifying
anything related to openmpi. Unless your building problems are due to
the MSVC express or the INSTALL_DEVELOPMENT you turned on?

ParaView_INSTALL_DEVELOPMENT:BOOL=ON
mpi_INSTALL_DEVELOPMENT:BOOL=ON
ParaView_INSTALL_FULL_DEVELOPMENT:BOOL=ON

Yumin

On Tue, Jan 8, 2013 at 10:30 AM, Bruno Santos
 wrote:
> Greetings,
>
> I've managed to get ParaView's SuperBuild working/building on Windows, which
> uses Open-MPI 1.6.2 by default on ParaView 3.98.0.
>
> From ParaView's resulting "CMakeCache.txt", these were defined for the C and
> CXX flags: /DOMPI_IMPORTS /DOPAL_IMPORTS /DORTE_IMPORTS
>
> These are the binaries and libraries that were included:
>
> MPIEXEC:FILEPATH=P:/install/bin/mpiexec.exe
> MPI_CXX_COMPILER:FILEPATH=P:/install/bin/mpicxx.exe
> MPI_CXX_INCLUDE_PATH:STRING=P:/install/include
> MPI_CXX_LIBRARIES:STRING=P:/install/lib/libmpi_cxx.lib
> MPI_C_COMPILER:FILEPATH=P:/install/bin/mpicc.exe
> MPI_C_INCLUDE_PATH:STRING=P:/install/include
> MPI_C_LIBRARIES:STRING=P:/install/lib/libmpi.lib;P:/install/lib/libopen-rte.lib;P:/install/lib/libopen-pal.lib;advapi32.lib;Ws2_32.lib;shlwapi.lib
> MPI_LIBRARY:FILEPATH=P:/install/lib/libmpi_cxx.lib
>
> Hope this helps!
>
>
> For those who may be curious about the modifications:
> http://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes3980
> When I've got some more time, I'll try to push some of these mods to the
> SuperBuild's Gerrit.
>
> Best regards,
> Bruno
>
>
> On 08-01-2013 14:43, Utkarsh Ayachit wrote:
>
> Ah, yea, that makes sense. On Windows shared builds with OpenMPI
> (built shared), those are indeed needed to be set.
>
> On Tue, Jan 8, 2013 at 6:05 AM, Stephan Rogge
>  wrote:
>
> Utkarsh,
>
> Thank you for that hint. I've added openlib-pal.lib and openlib-rte.lib to
> the linker list.  No success. The linker error remains.
>
> But after some research I found an advice to add the definition
> "OMPI_IMPORTS" to pre-processor:
>
> CMAKE_CXX_FLAGS = ... /D "OMPI_IMPORTS"
> CMAKE_C_FLAGS = ... /D "OMPI_IMPORTS"  => Maybe not required
>
> This solves my problem and ninja is running until the end :-).
>
> Is this an individual problem? I wonder if someone else had this error too.
>
> Best regards,
> Stephan
>
>
> ___
> 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 subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
>
>
>
> --
> http://www.bluecape.com.pt
>
> blueCAPE Lda - CAE solutions
> Rua Fonte dos Corvos, n.29
> Casais da Serra
> 2665-305 Milharado
> PORTUGAL
>
> (+351) 219 755 345  Tel.
> (+351) 219 755 345  Fax
> (+351) 926 008 657  Mob.
>
>
> ___
> 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 subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] Linker error with OpenMPI 1.6.2

[Bruno Santos]

Hi Yumin,

Not wanting to hijack this thread, the quick answer is this: the core of 
the modifications I needed to make were mostly due to using MSVC 2008 
Express and because I didn't have a compatible FORTRAN compiler installed.


I'll reply in higher detail on another mail with the subject "Unofficial 
development builds of ParaView 3.98.0 for Windows based on SuperBuild".


Best regards,
Bruno

On 08-01-2013 16:45, Yumin Yuan wrote:

Hi Bruno,

Just want to be clear on this. With Paraview's superbuild (pulling
openmpi-1.6.2 by default), do you still need to modify anything to
build? Looking at paraview's nightly dashboard
(http://open.cdash.org/index.php?project=ParaView), the superbuilds on
Windows work properly. I was also able to use paraview's superbuild
successfully with Ninja on Win7-vs9 for 3.98.0 without modifying
anything related to openmpi. Unless your building problems are due to
the MSVC express or the INSTALL_DEVELOPMENT you turned on?

ParaView_INSTALL_DEVELOPMENT:BOOL=ON
mpi_INSTALL_DEVELOPMENT:BOOL=ON
ParaView_INSTALL_FULL_DEVELOPMENT:BOOL=ON

Yumin

On Tue, Jan 8, 2013 at 10:30 AM, Bruno Santos
 wrote:

Greetings,

I've managed to get ParaView's SuperBuild working/building on Windows, which
uses Open-MPI 1.6.2 by default on ParaView 3.98.0.

 From ParaView's resulting "CMakeCache.txt", these were defined for the C and
CXX flags: /DOMPI_IMPORTS /DOPAL_IMPORTS /DORTE_IMPORTS

These are the binaries and libraries that were included:

MPIEXEC:FILEPATH=P:/install/bin/mpiexec.exe
MPI_CXX_COMPILER:FILEPATH=P:/install/bin/mpicxx.exe
MPI_CXX_INCLUDE_PATH:STRING=P:/install/include
MPI_CXX_LIBRARIES:STRING=P:/install/lib/libmpi_cxx.lib
MPI_C_COMPILER:FILEPATH=P:/install/bin/mpicc.exe
MPI_C_INCLUDE_PATH:STRING=P:/install/include
MPI_C_LIBRARIES:STRING=P:/install/lib/libmpi.lib;P:/install/lib/libopen-rte.lib;P:/install/lib/libopen-pal.lib;advapi32.lib;Ws2_32.lib;shlwapi.lib
MPI_LIBRARY:FILEPATH=P:/install/lib/libmpi_cxx.lib

Hope this helps!


For those who may be curious about the modifications:
http://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes3980
When I've got some more time, I'll try to push some of these mods to the
SuperBuild's Gerrit.

Best regards,
Bruno


On 08-01-2013 14:43, Utkarsh Ayachit wrote:

Ah, yea, that makes sense. On Windows shared builds with OpenMPI
(built shared), those are indeed needed to be set.

On Tue, Jan 8, 2013 at 6:05 AM, Stephan Rogge
 wrote:

Utkarsh,

Thank you for that hint. I've added openlib-pal.lib and openlib-rte.lib to
the linker list.  No success. The linker error remains.

But after some research I found an advice to add the definition
"OMPI_IMPORTS" to pre-processor:

CMAKE_CXX_FLAGS = ... /D "OMPI_IMPORTS"
CMAKE_C_FLAGS = ... /D "OMPI_IMPORTS"  => Maybe not required

This solves my problem and ninja is running until the end :-).

Is this an individual problem? I wonder if someone else had this error too.

Best regards,
Stephan


___
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 subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview




--
http://www.bluecape.com.pt

blueCAPE Lda - CAE solutions
Rua Fonte dos Corvos, n.29
Casais da Serra
2665-305 Milharado
PORTUGAL

(+351) 219 755 345  Tel.
(+351) 219 755 345  Fax
(+351) 926 008 657  Mob.


___
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






--
http://www.bluecape.com.pt

blueCAPE Lda - CAE solutions
Rua Fonte dos Corvos, n.29
Casais da Serra
2665-305 Milharado
PORTUGAL

(+351) 219 755 345  Tel.
(+351) 219 755 345  Fax
(+351) 926 008 657  Mob.

___
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

[Paraview] Unofficial development builds of ParaView 3.98.0 for Windows based on SuperBuild

[Bruno Santos]

Greetings,

Not wanting to hijack the thread "Linker error with OpenMPI 1.6.2", 
here's a more descriptive email.


I forgot to write an email on this the other day, but at the project 
http://code.google.com/p/unofficial-paraview-dev-install/ , a batch of 
development builds of ParaView 3.98.0 for Windows has been released, 
along with some notes on some of the changes made and how to reproduce 
these builds: 
http://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes3980
The objective of the project is to attempt to bring back the development 
builds that ParaView 3.8 had.


Since I used MSVC 2008 Express (with some minor changes for building for 
x64 as well), I wasn't as successful as the automated dashboard system.


Therefore, here is a summary of the mods for making things work:

 * The hacks on Open-MPI were because I only used MSVC 2008 Express and
   because I don't have a FORTRAN compiler...
   Reason: CMake configuration part on Open-MPI's side always stopped
   with something about a missing "mspdb" DLL...
 * Open-MPI was defaulting to building in debug mode...
 * I didn't use ninja, because it isn't strictly necessary, but there
   was a minor glitch on Windows when ninja isn't used.

Other hacks:

 * Upgrading SILO on MSVC Express has to be done manually, so I added
   an option to interactively upgrade the project.
 * Added options for independent installations of: ParaView's
   development files; OpenMPI; full development installation, which is
   a snapshot of the "install" folder used by the SuperBuild.
 * Added an option for building with Java wrapping, which wasn't very
   successful. The diagnosis this far was that VTK 6.0.0 that ParaView
   3.98.0 is still under development on this part.

The list of actual changes is browseable here: 
http://code.google.com/p/unofficial-paraview-dev-install/source/list?repo=superbuild3980&name=unofficial
But keep in mind that it hasn't got a very clean history, because of 
some iterations on trying to fix some things and to add features.


Best regards,
Bruno
___
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] [EXTERNAL] 2D contours on a slice for a 3D data

[Pradeep Jha]

Hello,

Thanks for the response. I was making a mistake. Its working fine now I think. 

Thanks a lot
Pradeep


Le 9 janv. 2013 à 01:42, "Moreland, Kenneth"  a écrit :

> In the Properties panel for the glyph filter, there should be an entry title 
> "Vectors".  Select the vector field you want to glyph by (in your case, 
> velocity).  If velocity is not listed there, it means your data does not have 
> a velocity point field.
> 
> -Ken
> 
> From: Pradeep Jha 
> Date: Tuesday, January 8, 2013 9:25 AM
> To: Kenneth Moreland 
> Cc: Sebastien Jourdain , 
> "paraview@paraview.org" 
> Subject: [EXTERNAL] Re: [Paraview] 2D contours on a slice for a 3D data
> 
>> Hello,
>> 
>> applying Glyph to the output of the slice filter just gives me arrows 
>> depending on the scalar field on the slice (figure attached). This is not 
>> what I want. I want arrows representing the magnitude and director of the 
>> vector at each point on the slice of a velocity vector which exits in the 3D 
>> cube. 
>> 
>> Thanks for the reply.
>> 
>> 
>> 
>> 
>> Le 9 janv. 2013 à 00:08, "Moreland, Kenneth"  a écrit :
>> 
>>> Try applying the glyph filter to the output of the slice filter.
>>> 
>>> -Ken
>>> 
>>> From: Pradeep Jha 
>>> Date: Tuesday, January 8, 2013 1:03 AM
>>> To: Kenneth Moreland 
>>> Cc: Sebastien Jourdain , 
>>> "paraview@paraview.org" 
>>> Subject: [EXTERNAL] Re: [Paraview] 2D contours on a slice for a 3D data
>>> 
 Hello,
 
 I have a follow up question on similar lines. 
 
 In the 3D cube that I have, I have a velocity vector data. Is it possible 
 that I can show the vector field coming out of the sliced plane? i.e. at 
 each point of the sliced plane, an arrow coming out of the sliced plane 
 representing the magnitude and direction  of the velocity vector at the 
 particular point on the plane. Something like the attached image.
  
 I hope I made myself clear.  
 Thanks in advance,
 Pradeep
 
 
 
 
 
 Le 8 janv. 2013 à 10:06, Pradeep Jha  a écrit 
 :
 
> Hello,
> 
> thanks everyone. It seems like it is working.
> 
> Pradeep
> 
> Le 8 janv. 2013 à 02:58, "Moreland, Kenneth"  a écrit :
> 
>> I'd like to expand upon on Sebastian's correct but short answer.
>> 
>> The contour filter is not going to give you the contours that you are 
>> asking for.  The contour filter is going to extract the geometry 
>> representing exactly the locations of the contours and nothing else.  As 
>> such, if you contour a slice through your data (or somewhat equivalently 
>> take a slice through your contour), you will get a bunch of lines 
>> representing where in the plane the field equals the isovalue you gave. 
>> So rather than getting a plane of colors as in your second example, you 
>> get the lines at the interface between colors.
>> 
>> The representation of contours you are asking for is a bit different.  
>> You want the entire geometry of the plane drawn and colored in such a 
>> way that the contours are represented as sharp transitions in the 
>> colors.  Since you are never actually extracting the geometry of the 
>> contours themselves, running the contour filter is not appropriate for 
>> this.  Instead, as Sebastian said, you want to make a slice through the 
>> data and provide a coloring that represents the contours.  To set up 
>> these colors, first make sure the slice is colored by the scaler value 
>> you want contours of.  Then click the edit color map button to pull up 
>> the color scale editor.  Click on the "Use Discrete Colors" option (you 
>> will need to turn on the "advanced" properties if you are using the most 
>> recent version of ParaView) and then set the resolution to be set to the 
>> number of color bands you want.
>> 
>> -Ken
>> 
>> From: Sebastien Jourdain 
>> Date: Monday, January 7, 2013 6:53 AM
>> To: Pradeep Jha 
>> Cc: "paraview@paraview.org" 
>> Subject: [EXTERNAL] Re: [Paraview] 2D contours on a slice for a 3D data
>> 
>>> It seems that you just want to slice your data and eventually reduce 
>>> the number of color in your lookup table so you see distinct color 
>>> bands.
>>> 
>>> Seb
>>> 
>>> 
>>> On Sun, Jan 6, 2013 at 10:16 PM, Pradeep Jha 
>>>  wrote:
 Hello,
 
 I have a 3D data (the geometry is a simple cube). I am interested in 
 looking at the 2D contour plots of a variable on a sliced plane.  
 Below I have attached two figures. The first figure shows the slice. 
 It only shows the cross-section of the iso-surfaces of the variable I 
 loaded in 3D. I am interested in getting a contour plot, like the 2nd 
 figure (I got this image randomly from the net), of the variable 
 values on the slice. 
 
 I hope I made myself 

Re: [Paraview] Extremely wide properties pane

[Anton Gladky]

Ok, the bug is 13772 [1] is reported.

Thanks,

Anton

[1] http://paraview.org/Bug/view.php?id=13772

2013/1/7 Utkarsh Ayachit :
>> Dear developers, should I file a bug on this issue?
>
> Yes please. This is definitely an oversight after the new panel
> changes and we should address it in the next release.
>
> Utkarsh
___
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] ParaView from git, make fail on OpenSUSE 12.2

[Pei-Ying Hsieh]

Hi, Utkarsh,

I moved ~/.config/ParaView to home folder, rebooted the computer, but, still 
received segmentation fault.

ERROR: In 
/home/phsieh/projects/ParaView/ParaView/VTK/GUISupport/Qt/vtkEventQtSlotConnect.cxx,
 line 68
vtkEventQtSlotConnect (0x2a2c220): Cannot connect NULL objects.


Pei-Ying




 From: Utkarsh Ayachit 
To: Pei-Ying Hsieh  
Cc: paraview  
Sent: Tuesday, January 8, 2013 10:06 AM
Subject: Re: [Paraview] ParaView from git, make fail on OpenSUSE 12.2
 
Not sure what could be going wrong. Try deleting your
"~/.config/ParaView" directory, you may want to copy it over to some
other place, just in case.

Utkarsh

On Mon, Jan 7, 2013 at 12:28 PM, Pei-Ying Hsieh  wrote:
> #0  0x76e4cc55 in pqApplicationCore::settings() () from
> /home/phsieh/projects/paraview-devel/lib/paraview-3.98/libvtkpqCore-pv3.98.so.1___
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] Error building ParaView with OSMesa and Python

[Utkarsh Ayachit]

I wonder if the problem is because the Python on RedHat is not built
with Unicode support. Can anyone confirm that? If so, I am assuming
there must be mechanisms of skipping corresponding code in
VTK/ParaView.

Utkarsh

On Tue, Jan 8, 2013 at 5:19 AM, Ian Krukow  wrote:
> Hello,
>
> I am trying to build ParaView 3.98.0 with OSMesa and Python 2.7 on a Linux
> cluster (Red Hat Enterprise). According to the Wiki
> (http://paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D), I do the
> following:
>
> ccmake -D PARAVIEW_BUILD_QT_GUI:BOOL=OFF -D VTK_USE_X:BOOL=OFF -D
> VTK_OPENGL_HAS_OSMESA:BOOL=ON {PARAVIEW_SOURCE_DIR}
> Specify OSMesa paths
> configure
> generate
> make
>
> So far, Python is disabled, and everything works fine. Then I turn on the
> parameter PARAVIEW_ENABLE_PYTHON. On my laptop (Ubuntu 12.04), everything is
> still fine. But on the cluster, I run into the following error with the make
> command:
>
> [iankruko@dnode192 ParaView-3.98.0-OSMesa]$ make
> [  0%] Built target vtksys
> [  0%] Built target vtkWrappingTools
> [  0%] Built target vtkWrapHierarchy
> [  1%] Built target vtkCommonCore
> [  1%] Built target vtkWrapPythonInit
> Linking CXX shared library ../../../lib/libvtkWrappingPython27-pv3.98.so
> CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function
> `vtkPythonArgs::BuildValue(vtkUnicodeString const&)':
> /home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.h:692:
> undefined reference to `PyUnicodeUCS2_DecodeUTF8'
> CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function `bool
> vtkPythonGetUnsignedLongLongValue(_object*, unsigned
> long long&)':
> /home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.cxx:106:
> undefined reference to `PyErr_WarnEx'
> CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function
> `vtkPythonGetValue(_object*, long&)':
> /home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.cxx:50:
> undefined reference to `PyErr_WarnEx'
> CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function `bool
> vtkPythonGetLongLongValue(_object*, long long&)':
> /home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.cxx:92:
> undefined reference to `PyErr_WarnEx'
> CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function
> `vtkPythonGetValue(_object*, unsigned long&)':
> /home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.cxx:59:
> undefined reference to `PyErr_WarnEx'
> CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function `bool
> vtkPythonGetStringValue(_object*, char const*&, char const*)':
> /home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.cxx:161:
> undefined reference to `_PyUnicodeUCS2_AsDefaultEncodedString'
> CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function `bool
> vtkPythonGetStringValue(_object*, char*&, char const*)':
> /home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.cxx:161:
> undefined reference to `_PyUnicodeUCS2_AsDefaultEncodedString'
> CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function
> `vtkPythonGetValue(_object*, vtkUnicodeString&)':
> /home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.cxx:311:
> undefined reference to `PyUnicodeUCS2_AsUTF8String'
> CMakeFiles/vtkWrappingPython.dir/vtkPythonArgs.cxx.o: In function
> `vtkPythonGetStdStringValue(_object*, std::basic_string std::char_traits, std::allocator >&, char const*)':
> /home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonArgs.cxx:196:
> undefined reference to `_PyUnicodeUCS2_AsDefaultEncodedString'
> CMakeFiles/vtkWrappingPython.dir/vtkPythonUtil.cxx.o: In function
> `vtkPythonUtil::VariantHash(vtkVariant const*)':
> /home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/vtkPythonUtil.cxx:850:
> undefined reference to `PyUnicodeUCS2_DecodeUTF8'
> CMakeFiles/vtkWrappingPython.dir/PyVTKMutableObject.cxx.o: In function
> `PyVTKMutableObject_Index':
> /home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/PyVTKMutableObject.cxx:464:
> undefined reference to `PyNumber_Index'
> CMakeFiles/vtkWrappingPython.dir/PyVTKMutableObject.cxx.o: In function
> `PyVTKMutableObject_Hex':
> /home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/PyVTKMutableObject.cxx:385:
> undefined reference to `PyNumber_ToBase'
> CMakeFiles/vtkWrappingPython.dir/PyVTKMutableObject.cxx.o: In function
> `PyVTKMutableObject_Oct':
> /home/iankruko/sources/ParaView-3.98.0-src/VTK/Wrapping/Python/PyVTKMutableObject.cxx:403:
> undefined reference to `PyNumber_ToBase'
> CMakeFiles/vtkWrappingPython.dir/PyVTKMutableObject.cxx.o:(.data.rel+0x78):
> undefined reference to `PyObject_HashNotImplemented'
> collect2: ld gab 1 als Ende-Status zurück
> make[2]: *** [lib/libvtkWrappingPython27-pv3.98.so.1] Fehler 1
> make[1]: *** [VTK/Wrapping/Python/CMakeFiles/vtkWrappingPython.dir/all]
> Fehler 2
> make: *** [all] Fehler 2
>
> I 

Re: [Paraview] ParaView from git, make fail on OpenSUSE 12.2

[Yumin Yuan]

A trial-and-error suggestion to debug the problem:
The segfault seems to be due to an uninitialized vtkProcessMoudule,
and to narrow down a bit more (if that is the issue), can you try to
set PARAVIEW_USE_MPI cmake variable to OFF, then run 'paraview -dr' to
see if that makes a difference?

Yumin

On Tue, Jan 8, 2013 at 3:05 PM, Pei-Ying Hsieh  wrote:
> Hi, Utkarsh,
>
> I moved ~/.config/ParaView to home folder, rebooted the computer, but, still
> received segmentation fault.
>
>
> ERROR: In
> /home/phsieh/projects/ParaView/ParaView/VTK/GUISupport/Qt/vtkEventQtSlotConnect.cxx,
> line 68
> vtkEventQtSlotConnect (0x2a2c220): Cannot connect NULL objects.
>
> Pei-Ying
>
> 
> From: Utkarsh Ayachit 
> To: Pei-Ying Hsieh 
> Cc: paraview 
> Sent: Tuesday, January 8, 2013 10:06 AM
>
> Subject: Re: [Paraview] ParaView from git, make fail on OpenSUSE 12.2
>
> Not sure what could be going wrong. Try deleting your
> "~/.config/ParaView" directory, you may want to copy it over to some
> other place, just in case.
>
> Utkarsh
>
> On Mon, Jan 7, 2013 at 12:28 PM, Pei-Ying Hsieh 
> wrote:
>> #0  0x76e4cc55 in pqApplicationCore::settings() () from
>>
>> /home/phsieh/projects/paraview-devel/lib/paraview-3.98/libvtkpqCore-pv3.98.so.1
>
>
>
> ___
> 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 subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] ParaView from git, make fail on OpenSUSE 12.2

[Pei-Ying Hsieh]

Hi, Yumin,

I turned off USE_MPI and ffmpeg in ccmake, re-did make and make install, still 
getting the same error:

hsieh@jali:~/projects/build-devel> paraview -dr
ERROR: In 
/home/hsieh/projects/ParaView-devel/ParaView/VTK/GUISupport/Qt/vtkEventQtSlotConnect.cxx,
 line 68
vtkEventQtSlotConnect (0x1be85b0): Cannot connect NULL objects.


Segmentation fault

qmake --version returned:

hsieh@jali:~/OpenFOAM/hsieh-2.1.x/run/damBreak> qmake --version
QMake version 2.01a
Using Qt version 4.8.1 in /usr/lib64

Pei-Ying






 From: Yumin Yuan 
To: Pei-Ying Hsieh  
Cc: Utkarsh Ayachit ; paraview 
 
Sent: Tuesday, January 8, 2013 5:04 PM
Subject: Re: [Paraview] ParaView from git, make fail on OpenSUSE 12.2
 
A trial-and-error suggestion to debug the problem:
The segfault seems to be due to an uninitialized vtkProcessMoudule,
and to narrow down a bit more (if that is the issue), can you try to
set PARAVIEW_USE_MPI cmake variable to OFF, then run 'paraview -dr' to
see if that makes a difference?

Yumin

On Tue, Jan 8, 2013 at 3:05 PM, Pei-Ying Hsieh  wrote:
> Hi, Utkarsh,
>
> I moved ~/.config/ParaView to home folder, rebooted the computer, but, still
> received segmentation fault.
>
>
> ERROR: In
> /home/phsieh/projects/ParaView/ParaView/VTK/GUISupport/Qt/vtkEventQtSlotConnect.cxx,
> line 68
> vtkEventQtSlotConnect (0x2a2c220): Cannot connect NULL objects.
>
> Pei-Ying
>
> 
> From: Utkarsh Ayachit 
> To: Pei-Ying Hsieh 
> Cc: paraview 
> Sent: Tuesday, January 8, 2013 10:06 AM
>
> Subject: Re: [Paraview] ParaView from git, make fail on OpenSUSE 12.2
>
> Not sure what could be going wrong. Try deleting your
> "~/.config/ParaView" directory, you may want to copy it over to some
> other place, just in case.
>
> Utkarsh
>
> On Mon, Jan 7, 2013 at 12:28 PM, Pei-Ying Hsieh 
> wrote:
>> #0  0x76e4cc55 in pqApplicationCore::settings() () from
>>
>> /home/phsieh/projects/paraview-devel/lib/paraview-3.98/libvtkpqCore-pv3.98.so.1
>
>
>
> ___
> 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 subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

[Paraview] Geometry attribute in PVX files

[Stephan Rogge]

Hello,

I've noticed the new geometry attribute in the PVX configure files to place
and size render windows for each render server process. GREAT!!! This makes
the life of ParaView in the CAVE mode under Windows much easier :).
 Adding this attribute to my PVX files works great under Windows, but I have
render windows with borders / decoration rather than real full screens. I
think in vtkPVSynchronizedRenderWindows (line 1161 - 1165) the activation of
the full screen mode is missing:
// Use the specified geometry
this->Internals->SharedRenderWindow->SetPosition(geometry[0],
   geometry[1]);
this->Internals->SharedRenderWindow->SetSize(geometry[2],
   geometry[3]);

Adding this line before helps me to get rid of these borders:
this->Internals->SharedRenderWindow->SetFullScreen(1); 

Is this a bug or an desired functionality?

Regards,
Stephan




___
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