[Paraview] Lookup table bug for the filter following a volume representation
Hi, I submitted a bug related to Lookup table here : http://paraview.org/Bug/view.php?id=12180 Basically, if you select a 'Volume' representation for a filter and plug another filter, the new representation lookup table freezes to a default red-to-purple scale. Can anyboy tell me if this is reproducible elsewhere than on my system (Linux, NVidia, PV-3.11.1 git-master)? Thanks a lot Jerome ___ 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 with python calculator tutorial
Hi Jonathan, It looks like we missed installing lapack in the binary and the machines we tested on likely already had it installed in the system. I'll look into slipping the missing .so into the binary shortly. On Thu, Jun 30, 2011 at 11:19 PM, Jonathan Regele jonathan.reg...@caltech.edu wrote: ** Hello, I've searched the web far and wide for an answer to this question, but can't find it. I'm running Ubuntu 10.04 and want to use the python calculator. I downloaded the paraview-3.10.1 binary and loaded paraview. When I follow the tutorial, create sphere assign the expression the value 5 and apply it gives the following error. Traceback (most recent call last): File string, line 4, in module File /usr/local/ParaView-3.10.1-Linux-x86_64/lib/paraview-3.10/site-packages/paraview/vtk/dataset_adapter.py, line 5, in module sure that it is installed properly.) RuntimeError: This module depends on the numpy module. Please makesure that it is installed properly. I have python 2.6.5 installed on my computer but my understanding is that the binary comes with its own set of python. I checked and it looks like there is python 2.7 in the package directory. It also looks like it comes with its own version of numpy here /usr/local/ParaView-3.10.1-Linux-x86_64/lib/paraview-3.10/lib/python2.7/site-packages/numpy/ If I delete the python calculator and try it again I get a different error message: Traceback (most recent call last): File string, line 4, in module File /usr/local/ParaView-3.10.1-Linux-x86_64/lib/paraview-3.10/site-packages/paraview/vtk/dataset_adapter.py, line 2, in module import numpy File /usr/local/ParaView-3.10.1-Linux-x86_64/lib/paraview-3.10/lib/python2.7/site-packages/numpy/__init__.py, line 136, in module import add_newdocs File /usr/local/ParaView-3.10.1-Linux-x86_64/lib/paraview-3.10/lib/python2.7/site-packages/numpy/add_newdocs.py, line 9, in module from numpy.lib import add_newdoc File /usr/local/ParaView-3.10.1-Linux-x86_64/lib/paraview-3.10/lib/python2.7/site-packages/numpy/lib/__init__.py, line 13, in module from polynomial import * File /usr/local/ParaView-3.10.1-Linux-x86_64/lib/paraview-3.10/lib/python2.7/site-packages/numpy/lib/polynomial.py, line 11, in module import numpy.core.numeric as NX AttributeError: 'module' object has no attribute 'core' It gives the same error after that. The error seems to occur when it tries to import numpy. In a linux terminal window, if I open python 2.6 and import numpy it doesn't give me any problems. If I open the python shell in paraview and try to import numpy I get the following output: Python 2.7.1 (r271:86832, Mar 17 2011, 09:15:47) [GCC 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)] on linux2 from paraview.simple import * paraview version 3.10.1, Date: 2011-01-28 import numpy Traceback (most recent call last): File console, line 1, in module File /usr/local/ParaView-3.10.1-Linux-x86_64/lib/paraview-3.10/lib/python2.7/site-packages/numpy/__init__.py, line 136, in module import add_newdocs File /usr/local/ParaView-3.10.1-Linux-x86_64/lib/paraview-3.10/lib/python2.7/site-packages/numpy/add_newdocs.py, line 9, in module from numpy.lib import add_newdoc File /usr/local/ParaView-3.10.1-Linux-x86_64/lib/paraview-3.10/lib/python2.7/site-packages/numpy/lib/__init__.py, line 13, in module from polynomial import * File /usr/local/ParaView-3.10.1-Linux-x86_64/lib/paraview-3.10/lib/python2.7/site-packages/numpy/lib/polynomial.py, line 17, in module from numpy.linalg import eigvals, lstsq File /usr/local/ParaView-3.10.1-Linux-x86_64/lib/paraview-3.10/lib/python2.7/site-packages/numpy/linalg/__init__.py, line 48, in module from linalg import * File /usr/local/ParaView-3.10.1-Linux-x86_64/lib/paraview-3.10/lib/python2.7/site-packages/numpy/linalg/linalg.py, line 23, in module from numpy.linalg import lapack_lite ImportError: liblapack.so: cannot open shared object file: No such file or directory I've tried several things, but it just doesn't make any sense. Any ideas? Jonathan ___ 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] Lookup table bug for the filter following a volume representation
I was able to reproduce. Thanks for reporting. I will take a look. Utkarsh On Fri, Jul 1, 2011 at 7:07 AM, Jérôme jerome.ve...@gmail.com wrote: Hi, I submitted a bug related to Lookup table here : http://paraview.org/Bug/view.php?id=12180 Basically, if you select a 'Volume' representation for a filter and plug another filter, the new representation lookup table freezes to a default red-to-purple scale. Can anyboy tell me if this is reproducible elsewhere than on my system (Linux, NVidia, PV-3.11.1 git-master)? Thanks a lot Jerome ___ 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] FW: FW: Coloured isosurfaces when running MPI
Thanks! The Compute Normals is checked in the contour filter after the CleanToGrid filter, however the Gouraud shading does not work. But using an additional Generate Surface Normals then does the trick, at least partially. The contours look nicer than without Gouraud shading, obviously, but the best result (and also the cheapest one, I will use it on large data sets) would still be obtained when directly doing a contour on the original rectilinear data without transforming it to unstructured. Thus, I was wondering whether I should submit the present case also as a bug report, as I guess also other people might need coloured isosurfaces when running MPI? Best regards, Philipp On Fri, 01 Jul 2011 15:53:18 +0200, pat marion pat.mar...@kitware.com wrote: Hi Philipp, You need to check the Compute Normals box on the properties panel of the contour filter. Alternatively, you can apply the Generate Surface Normals to any polydata dataset to enable correct Gouraud shading. Pat On Wed, Jun 29, 2011 at 11:24 AM, Philipp Schlatter pschl...@mech.kth.sewrote: Thanks a lot for the help! Concerning the suggested workaround, I have a follow-up question: How would one get the Gouraud shading of the isocontours working? In my case I will get properly coloured isocontours, but they seem to have uniform shade for each triangle as opposed to an interpolated shade. Thanks, philipp On Wed, 29 Jun 2011 14:34:34 +0200, Karl König kkoeni...@web.de wrote: Hi Philipp, It seems you have hit a bug in the Contour filter occurring with 1 pvserver process and rectilinear grid input. I can reproduce the issue you reported as such: Load ParaView, connect to 1 pvserver processes Open Data/RectGrid2.vtk (e.g. from git://vtk.org/VTKData.git) Calculator filter, operation: coordsX, Result Array Name: Result, Apply Contour filter, Contour by scalars, Compute Normals, Isosurface Value 0.5, Apply Representation Surface, Color by Result With 1 pvserver process the surface coloring is indeed a single smooth gradient while with more than 1 pvserver process the gradient starts anew at half the X range. If applying an additional Process ID Scalars filter, one can confirm that the reset happens at a process boundary. Converting the rectilinear grid to an unstructured grid prior to applying the contour filter may serve as as a workaround. The filters Clean to Grid, Tetrahedralize and Tesselate all do that trick (they are listed with increasing memory footprint). So, I recommend using Clean to Grid somewhere before applying the contour filter in the parallel case. Karl Philipp Schlatter wrote, On 29.06.2011 11:50: Hi! Thanks for the answer. Let me give some comments to your questions: - I am using the distributed 3.10.1 binaries (32 bit), and I tried it on a Ubuntu 11.04 system (older dualcore T60p) - I used now the sample dataset Data/RectGrid2.vtk. Using the calculator operation CoordsX, I can reproduce the behaviour I was originally describing. I simply use the Contour filter (Compute Scalars did not change the behaviour). I have uploaded 3 more screenshots: http://www.mech.kth.se/~**pschlatt/files/Screenshot3.pnghttp://www.mech.kth.se/%7Epschlatt/files/Screenshot3.png is the intended result, obtained using a single core (no Auto-MPI etc.) http://www.mech.kth.se/~**pschlatt/files/Screenshot2.pnghttp://www.mech.kth.se/%7Epschlatt/files/Screenshot2.png is the result obtained with Auto-MPI, running on my two cores. http://www.mech.kth.se/~**pschlatt/files/Screenshot1.pnghttp://www.mech.kth.se/%7Epschlatt/files/Screenshot1.png is the result obtained with explicitly initiating paraview and pvserver using a total of 16 MPI ranks. I tried all/most of the rendering options (LOD etc.), however it did not help. Also, I have run on 64 bit version at the computer centre (with older versions though), and the same problem appears there too. I am really puzzled by the fact that you could not reproduce the problem. Could there be some setting that is for some reason wrong in my setup? Best regards, Philipp On Tue, 28 Jun 2011 18:36:25 +0200, Karl König kkoeni...@web.de wrote: Hi Philipp, A couple of questions: * Are you using the distributed 3.10.1 binaries or did you compile PV 3.10.1 from source yourself? * Can you reproduce the behavior with the sample dataset Data/RectGrid2.vtk (part of both git://vtk.org/VTKData.git and http://www.paraview.org/files/**v3.10/ParaViewData-3.10.1.ziphttp://www.paraview.org/files/v3.10/ParaViewData-3.10.1.zip )**? That's also a Rectilinear Grid. Using the Calculator operation 1 + coordsX*coordsY followed by a Contour filter with Compute Scalars checked and 10 auto-chosen values, I got identical results with 1 and 16 cores (using PV 3.10.1 Linux 64-bit binaries and Windows 64-bit binaries, relying on Auto-MPI (Settings - Use Multi-Core) for the 16 core case) Karl Philipp Schlatter wrote, On 28.06.2011 17:50: Dear
Re: [Paraview] independent colorbar range in different views of same session?
Hello Emily, ParaView tries to use the same color transfer function for each variable in all views to ensure that one perceives the same value wherever they see a particular color. I expect this is what is happening here. What you might do then to get around this behavior is to create a copy of your array and color by that array in one view or the other. The simplest way I can thing to do that is to use the calculator filter. First choose either point or cell alignment to find the array you want, then set the calculator expression to be simply the name of the array you are making a copy of. Optionally set the output name if you don't want the copy to be called RESULT. Lastly choose the new array as the one to color by in one of the two views. hth, David E DeMarle Kitware, Inc. RD Engineer 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-371-3971 x109 On Fri, Jul 1, 2011 at 10:32 AM, Guzas, Emily L CIV NUWC NWPT emily.gu...@navy.mil wrote: Hello, I am a ParaView newbie trying to visualize two different types of time-varying data (let's say density and pressure) for the same analysis in two separate views of the same session of ParaView. I have set up the two views, where view 1 has the pressure data turned on and view 2 has the density data turned on. I made a colorbar for each view, and have changed the colorbar title to pressure for view 1 and density for view 2. (To make these colorbars, I first clicked on the pressure data in the pipeline browser, then clicked on view 1, then created the colorbar for pressure; then I clicked on the density data in the pipeline browser, then clicked on view 2, then created the colorbar for density). However, when I try to change the scale of each colorbar so that it only spans its data, then the colorbar for the other data is automatically changed. Does anyone know how to set the colorbar ranges independently for each view (say 1e5-2e7 Pa for pressure, in view 1, and 1-1000 g/cc for density, in view 2)? Thanks, Emily ___ 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] independent colorbar range in different views of same session?
Hah Eric so there! :) The calculator filter will do what you want. There are probably better ways but the calculator will only take a minute to try. David E DeMarle Kitware, Inc. RD Engineer 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-371-3971 x109 On Fri, Jul 1, 2011 at 2:29 PM, Guzas, Emily L CIV NUWC NWPT emily.gu...@navy.mil wrote: David and Eric, Thanks for the advice. Your responses have definitely helped me get closer to actually defining the problem more precisely. Here's some more background: Although I am working with two different attributes from the same analysis (pressure and fluidID), the exodusii converter that I'm using (written by someone else) only operates on one attribute at a time and defaults to calling this attribute resX in the *.exo file. So I run the converter twice on my data, once to get the pressure.exo file and once to get the fluidID.exo file, but yet both files have a common name, resX, for the data attribute that I'm interested in. In ParaView, I am coloring both views by resX, even though in view 1, resX represents pressure and in view 2, resX represents fluidID. See attached screenshot. So without having to get the exodusii converter fixed, is there a way to change the data name in ParaView from resX to something else, say pressure, so that I can color my two views by a different variable, which should probably fix my problem with the independent colorbar scales? Thanks! -Emily --- Emily L. Guzas, Ph.D. Naval Undersea Warfare Center, Division Newport Analysis and Technology Branch, Code 4121 Phone: 401.832.5577 Email: emily.gu...@navy.mil This signature line and my digital signature is the equivalent of a hard copy signature, serving to authenticate that I have the authority to send this e-mail and to indicate I have consciously decided that it should have the same legal authority normally accorded to an actual hard copy signature. From: Eric E. Monson Sent: Fri 7/1/2011 1:56 PM To: Guzas, Emily L CIV NUWC NWPT Cc: David E DeMarle; Paraview Mailing list (to use with ec-nantes) Subject: Re: [Paraview] independent colorbar range in different views of same session? Hey, David, Emily seems to be describing that she already has two different attributes, so I'm suspecting that somehow she's mistakenly coloring by the same attribute in both views... Emily, as David is saying, (at least my understanding of) what you're wanting should be the default behavior. Make sure that when you click on each view the color by combo box changes which attribute it's listing, and that each colormap has Automatically Rescale to Fit Data Range checked in the colormap editor. Attached is a screen shot that I made right out of the box with all default settings, just having the surface colored by different attributes in different windows, and choosing an alternative to the blue-white-red colormap for Elevation. If you're still having trouble, maybe let us know which version of ParaView you're using, and on which platform, and whether you built it yourself. -Eric ___ 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] independent colorbar range in different views of same session?
Thanks guys! The calculator filter does work. Kudos to both Eric and David for making me understand the actual problem I was having, and then for giving me a solution. Cheers, Emily From: David E DeMarle Sent: Fri 7/1/2011 2:35 PM To: Guzas, Emily L CIV NUWC NWPT Cc: Eric E. Monson; Paraview Mailing list (to use with ec-nantes) Subject: Re: [Paraview] independent colorbar range in different views of same session? Hah Eric so there! :) The calculator filter will do what you want. There are probably better ways but the calculator will only take a minute to try. David E DeMarle Kitware, Inc. RD Engineer 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-371-3971 x109 On Fri, Jul 1, 2011 at 2:29 PM, Guzas, Emily L CIV NUWC NWPT emily.gu...@navy.mil wrote: David and Eric, Thanks for the advice. Your responses have definitely helped me get closer to actually defining the problem more precisely. Here's some more background: Although I am working with two different attributes from the same analysis (pressure and fluidID), the exodusii converter that I'm using (written by someone else) only operates on one attribute at a time and defaults to calling this attribute resX in the *.exo file. So I run the converter twice on my data, once to get the pressure.exo file and once to get the fluidID.exo file, but yet both files have a common name, resX, for the data attribute that I'm interested in. In ParaView, I am coloring both views by resX, even though in view 1, resX represents pressure and in view 2, resX represents fluidID. See attached screenshot. So without having to get the exodusii converter fixed, is there a way to change the data name in ParaView from resX to something else, say pressure, so that I can color my two views by a different variable, which should probably fix my problem with the independent colorbar scales? Thanks! -Emily --- Emily L. Guzas, Ph.D. Naval Undersea Warfare Center, Division Newport Analysis and Technology Branch, Code 4121 Phone: 401.832.5577 Email: emily.gu...@navy.mil This signature line and my digital signature is the equivalent of a hard copy signature, serving to authenticate that I have the authority to send this e-mail and to indicate I have consciously decided that it should have the same legal authority normally accorded to an actual hard copy signature. From: Eric E. Monson Sent: Fri 7/1/2011 1:56 PM To: Guzas, Emily L CIV NUWC NWPT Cc: David E DeMarle; Paraview Mailing list (to use with ec-nantes) Subject: Re: [Paraview] independent colorbar range in different views of same session? Hey, David, Emily seems to be describing that she already has two different attributes, so I'm suspecting that somehow she's mistakenly coloring by the same attribute in both views... Emily, as David is saying, (at least my understanding of) what you're wanting should be the default behavior. Make sure that when you click on each view the color by combo box changes which attribute it's listing, and that each colormap has Automatically Rescale to Fit Data Range checked in the colormap editor. Attached is a screen shot that I made right out of the box with all default settings, just having the surface colored by different attributes in different windows, and choosing an alternative to the blue-white-red colormap for Elevation. If you're still having trouble, maybe let us know which version of ParaView you're using, and on which platform, and whether you built it yourself. -Eric smime.p7s Description: S/MIME cryptographic signature ___ 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] OSMesa Desired GL includes not used
When I build ParaView with OSMesa only GL/gl.h is not found. My build of mesa is installed in /home/kevin/mesa_osmesa. The system mesa headers are not installed. At the end of this e-mail, is the tail of the output of a verbose build There is no -I/home/kevin/mesa_osmesa to be found. If I install the system mesa-libGL-devel package ( required for qt-devel which I need for my mesa-xlib build ) the build succedes, so Paraview is not using the gl.h associated with the OSMesa library. [ 86%] Building CXX object ParaViewCore/ClientServerCore/CMakeFiles/vtkPVClientServerCore.dir/vtkIceTSynchronizedRenderers.cxx.o cd /home/kevin/kitware/ParaView_OSMesa_Build/ParaViewCore/ClientServerCore /usr/lib64/ccache/c++ -DvtkPVClientServerCore_EXPORTS -DVTK_PYTHON_BUILD -DMPICH_IGNORE_CXX_SEEK -D_HPUX_SOURCE -Wno-deprecated -O3 -DNDEBUG -fPIC -I/home/kevin/kitware/ParaView/ParaViewCore/ClientServerCore -I/home/kevin/kitware/ParaView_OSMesa_Build -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/Utilities -I/usr/include/python2.7 -I/home/kevin/kitware/ParaView/Utilities/IceT/src/include -I/home/kevin/kitware/ParaView_OSMesa_Build/Utilities/IceT/src/include -I/home/kevin/kitware/ParaView/Utilities/VTKPythonWrapping/Executable -I/home/kevin/kitware/ParaView/ParaViewCore/Common -I/home/kevin/kitware/ParaView_OSMesa_Build/ParaViewCore/Common -I/home/kevin/kitware/ParaView/ParaViewCore/VTKExtensions -I/home/kevin/kitware/ParaView_OSMesa_Build/ParaViewCore/VTKExtensions -I/home/kevin/kitware/ParaView_OSMesa_Build/ParaViewCore/ClientServerCore -I/home/kevin/kitware/ParaView/VTK -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK -I/home/kevin/kitware/ParaView/VTK/Utilities -I/home/kevin/kitware/ParaView/VTK/Wrapping -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/Wrapping -I/home/kevin/kitware/ParaView/VTK/Wrapping/Python -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/Wrapping/Python -I/home/kevin/kitware/ParaView/VTK/Common -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/Common -I/home/kevin/kitware/ParaView/VTK/Charts -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/Charts -I/home/kevin/kitware/ParaView/VTK/Filtering -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/Filtering -I/home/kevin/kitware/ParaView/VTK/GenericFiltering -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/GenericFiltering -I/home/kevin/kitware/ParaView/VTK/IO -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/IO -I/home/kevin/kitware/ParaView/VTK/Imaging -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/Imaging -I/home/kevin/kitware/ParaView/VTK/Rendering -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/Rendering -I/home/kevin/kitware/ParaView/VTK/Parallel -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/Parallel -I/home/kevin/kitware/ParaView/VTK/Graphics -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/Graphics -I/home/kevin/kitware/ParaView/VTK/Hybrid -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/Hybrid -I/home/kevin/kitware/ParaView/VTK/VolumeRendering -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/VolumeRendering -I/home/kevin/kitware/ParaView/VTK/Widgets -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/Widgets -I/home/kevin/kitware/ParaView/VTK/Infovis -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/Infovis -I/home/kevin/kitware/ParaView/VTK/Views -I/home/kevin/kitware/ParaView_OSMesa_Build/VTK/Views -I/usr/include/openmpi-x86_64 -I/home/kevin/kitware/ParaView/Utilities/VTKClientServer -I/home/kevin/kitware/ParaView_OSMesa_Build/Utilities/VTKClientServer -o CMakeFiles/vtkPVClientServerCore.dir/vtkIceTSynchronizedRenderers.cxx.o -c /home/kevin/kitware/ParaView/ParaViewCore/ClientServerCore/vtkIceTSynchronizedRenderers.cxx In file included from /home/kevin/kitware/ParaView_OSMesa_Build/VTK/Rendering/vtkgl.h:22:0, from /home/kevin/kitware/ParaView/ParaViewCore/ClientServerCore/vtkIceTSynchronizedRenderers.cxx:33: /home/kevin/kitware/ParaView/VTK/Rendering/vtkOpenGL.h:26:43: fatal error: GL/gl.h: No such file or directory compilation terminated. make[2]: *** [ParaViewCore/ClientServerCore/CMakeFiles/vtkPVClientServerCore.dir/vtkIceTSynchronizedRenderers.cxx.o] Error 1 make[2]: Leaving directory `/home/kevin/kitware/ParaView_OSMesa_Build' make[1]: *** [ParaViewCore/ClientServerCore/CMakeFiles/vtkPVClientServerCore.dir/all] Error 2 make[1]: Leaving directory `/home/kevin/kitware/ParaView_OSMesa_Build' make: *** [all] Error 2 signature.asc Description: OpenPGP digital signature ___ 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] Weird boost error during ccmake
I got this error. I hope it's obvious why I think it's weird. I'm building against boost 1.46. Or thought I was. This message seems to imply it's looking at the system boost in /usr/include/boost Your system is using an outdated version of Boost (1.33.1, found in /nfs/tmp2/rcook/ParaView/3.10/build/boost_1_46_1). Some of the graph processing filters require version 1.36.0 or later to build on 64-bit platforms. -- ✐Richard Cook ✇ Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ☎ (office) (925) 423-9605 ☎ (fax) (925) 423-6961 --- Information Management Graphics Grp., Services Development Div., Integrated Computing Communications Dept. (opinions expressed herein are mine and not those of LLNL) ___ 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
