Re: [Paraview] SuperBuild errors with VS2008 win32 (On Win7 Ult x64)

2012-05-02 Thread Bruno Santos
I had problems with this as well and documented the process here: http://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes3141 There you might also find answers for your other question. On 02-05-2012 01:49, paraview-requ...@paraview.org wrote: From: Michael

[Paraview] 3D scalar field contour visualisation not working from CSV

2012-05-02 Thread Oliver Zeldin
Hi, I have been trying to create contour and slice maps from a csv file (x,y,z,data1,data2) where x,y,z form a regular 3d array. I have no problems importing and visualising the data by selecting open--table to points, then displaying and colouring the points by data1 or data2. The problem is

Re: [Paraview] 3D scalar field contour visualisation not working from CSV

2012-05-02 Thread David E DeMarle
Apply the Delauney filter to fill in space between the infinately small point samples you've got, then the slice and contour filters will have something to cut into. David E DeMarle Kitware, Inc. RD Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, May 2, 2012

Re: [Paraview] SuperBuild errors with VS2008 win32 (On Win7 Ult x64)

2012-05-02 Thread Michael Jackson
I took a look at that page a it struck me that at least one of the errors (ncconfig.h.in) is clearly a bug. From the wiki page are your hints: • Problems with vtkNetCDF when building win32 with MSVC2008: • The error message was paraview-3.14.1-superbuild\include\H5public.h(133) : error C2632:

Re: [Paraview] SuperBuild errors with VS2008 win32 (On Win7 Ult x64)

2012-05-02 Thread Michael Jackson
That didn't work. I think because in H5public.h ssize_t is a typedef and NetCDF is using a #define instead? My c fu isn't that strong to figure it out. I'll just comment it out and move on. -- Mike Jackson www.bluequartz.net On May 2, 2012, at 9:46 AM, Michael Jackson wrote: I took a look at

Re: [Paraview] Calculating rms values using the Temporal Statistics filter

2012-05-02 Thread Janusz Michalik
Hello all, I would like to calculate rms values for my simulations. For example, for the calculations of the axial velocity u'rms = sqr( ( (u')^2)_ave ) I first need to calculate the fluctuations, u'_x = u_x - u_x_ave. I obtain: 1) u_x via the calculator. 2) u_x_ave using the temporal

Re: [Paraview] [EXTERNAL] Re: Calculating rms values using the Temporal Statistics filter

2012-05-02 Thread Moreland, Kenneth
You should be able to use method (a) and then use the append attributes filter to combine the fields in the two branches into one dataset. -Ken From: Janusz Michalik janusz.micha...@epfl.chmailto:janusz.micha...@epfl.ch Date: Wed, 2 May 2012 14:29:00 + To:

Re: [Paraview] SuperBuild errors with VS2008 win32 (On Win7 Ult x64)

2012-05-02 Thread Robert Maynard
Hi, I use Visual Studio 2008 Professional to generate the ParaView binaries and have to do no modification of Silo or NetCDF. I feel the problem might be related to using a older version of CMake that isn't properly executing all the custom build steps. We have a custom step for Silo that does

[Paraview] animation view: change from surface to wireframe

2012-05-02 Thread Chr. Rossmanith
Hi, is it possible to change the representation from 'surface' to 'wireframe' in an animation similar e.g. to changing the visibility from 'off' to 'on'? Christina Rossmanith -- Dept. of Neurology University Medical Center Mannheim ___ Powered by

[Paraview] paraview plugins and python

2012-05-02 Thread Paul Edwards
Hi, Do my VTK classes get wrapped when I create a paraview plugin? If so, how do I access them? And, if not, is it possible to do this? Thanks, Paul ___ Powered by www.kitware.com Visit other Kitware open-source projects at

Re: [Paraview] SuperBuild errors with VS2008 win32 (On Win7 Ult x64)

2012-05-02 Thread Michael Jackson
I am running CMake 2.8.7 for these builds. I am also using VS2008 SP1 for the build because I need it match exactly the Kitware build environment. I didn't do anything special in the install of Visual Studio. I did put the CMake installation in C:/Applications (where I put some other items).

Re: [Paraview] paraview plugins and python

2012-05-02 Thread Sebastien Jourdain
Hi Paul, your vtk class are not python wrapped automatically when provided from plugin. But you might be able to use a CMake macro that has been defined in ParaView to force your vtk classes to be Python wrapped. Although, I'm not fully certain that will just work. Unfortunately I don't have much

Re: [Paraview] paraview plugins and python

2012-05-02 Thread Paul Edwards
I'm actually wanting the VTK classes rather than the proxy. Sebastian: are you referring to the VTK_WRAP_PYTHON_SIP option? I don't have that enabled atm but could try... Thanks, Paul On 2 May 2012 16:43, Andy Bauer andy.ba...@kitware.com wrote: I'm not sure this is what you're looking for

Re: [Paraview] paraview plugins and python

2012-05-02 Thread Sebastien Jourdain
Hi Paul, it is not a CMake option but a CMake macro/function that need to be called inside your Plugin CMake file... But I have no clue how, has I took another path when I solved that exact same problem. In my case, I simply extended ParaView itself instead of relying on a plugin... Seb On Wed,

Re: [Paraview] headless paraview installation

2012-05-02 Thread Cagatay Bilgin
http://paraview.org/Wiki/ParaViewWeb_Building 1) There is no field CORE_SERVICE_URL CORE_SERVICE_URL http://localhost:8080/PWService Use the deployment address otherwise the sample 2) The following fields have different names. This was not that hard to figure anyway.

Re: [Paraview] paraview plugins and python

2012-05-02 Thread Pat Marion
This will do it: # CMakeLists.txt include(wrap-python.cmake) add_paraview_plugin(${library_name} ...) target_link_libraries(${library_name} ${deps}) if(VTK_WRAP_PYTHON) wrap_python(${library_name} ${sources}) endif() # wrap-python.cmake if(NOT DEFINED VTK_CMAKE_DIR) message(SEND_ERROR

Re: [Paraview] headless paraview installation

2012-05-02 Thread Sebastien Jourdain
Thank Cagatay for your feedback, I'll update the wiki. For the point 4: we do have a super build now that automate all that process and the point of that documentation was to illustrate each pieces independently from each other instead of explaining the setup for a monolithic system. But I agree