[Paraview] Retire expected builds
I'm moving to a new job, and will no longer be able to maintain my nightly builds (even in their neglected state.) Please expect the expected builds from bubbles, murron, and k450e to dissapear. 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
[Paraview] Segfault in PLY reader
Paraview segfaults when attempting to read Armadillo.ply from Stanford: http://graphics.stanford.edu/pub/3Dscanrep/armadillo/Armadillo.ply.gz The segfault happens both with the system PV on Fedora 20 : $ rpm -q paraview paraview-4.1.0-1.fc20.x86_64 and with the nightly dashboard version. This system is bubbles on the dashboard. I'm recompiling the nightly version with debug options now, but here is a backtrace from the system PV and gdb : #0 0x7fffd9bb0746 in vtkPLYReader::RequestData (this=optimized out, outputVector=optimized out) at /usr/src/debug/ParaView-v4.1.0/VTK/IO/PLY/vtkPLYReader.cxx:294 #1 0x7fffe2b98740 in vtkExecutive::CallAlgorithm (this=0x1f763a0, request=0x1efd1c0, direction=optimized out, inInfo=0x0, outInfo=0x1edb720) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx:745 #2 0x7fffe2b93997 in vtkDemandDrivenPipeline::ExecuteData (this=this@entry=0x1f763a0, request=request@entry=0x1efd1c0, inInfo=inInfo@entry=0x0, outInfo=outInfo@entry=0x1edb720) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:497 #3 0x7fffe2b91639 in vtkCompositeDataPipeline::ExecuteData (this=0x1f763a0, request=0x1efd1c0, inInfoVec=0x0, outInfoVec=0x1edb720) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx:175 #4 0x7fffe2b96211 in vtkDemandDrivenPipeline::ProcessRequest (this=this@entry=0x1f763a0, request=request@entry=0x1efd1c0, inInfoVec=inInfoVec@entry=0x0, outInfoVec=outInfoVec@entry=0x1edb720) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:279 #5 0x7fffe2ba9169 in vtkStreamingDemandDrivenPipeline::ProcessRequest (this=0x1f763a0, request=request@entry=0x1efd1c0, inInfoVec=0x0, outInfoVec=outInfoVec@entry=0x1edb720) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx:346 #6 0x7fffe2b90bfa in vtkCompositeDataPipeline::ForwardUpstream (this=0x1f9a340, request=0x1efd1c0) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx:712 #7 0x7fffe2b961bb in vtkDemandDrivenPipeline::ProcessRequest (this=this@entry=0x1f9a340, request=request@entry=0x1efd1c0, inInfoVec=inInfoVec@entry=0x1538320, outInfoVec=outInfoVec@entry=0x1f4aa30) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:265 #8 0x7fffe2ba9169 in vtkStreamingDemandDrivenPipeline::ProcessRequest (this=this@entry=0x1f9a340, request=0x1efd1c0, inInfoVec=0x1538320, outInfoVec=outInfoVec@entry=0x1f4aa30) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx:346 #9 0x7fffe2b94e0d in vtkDemandDrivenPipeline::UpdateData (this=0x1f9a340, outputPort=optimized out) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:448 #10 0x7fffe2ba9cb5 in vtkStreamingDemandDrivenPipeline::Update (this=0x1f9a340, port=0) at /usr/src/debug/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx:399 #11 0x7301b2db in vtkSISourceProxyCommand (arlu=0xeacb40, ob=0x1f0b800, method=optimized out, msg=..., resultStream=...) at /usr/src/debug/ParaView-v4.1.0/fedora-openmpi/Wrapping/ClientServer/vtkSISourceProxyClientServer.cxx:113 #12 0x7fffedc2e867 in vtkClientServerInterpreter::CallCommandFunction (this=this@entry=0xeacb40, cname=0x7123a239 vtkSISourceProxy, ptr=ptr@entry=0x1f0b800, method=method@entry=0x1f50009 UpdatePipeline, msg=..., result=...) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:840 #13 0x7fffedc2ebb2 in vtkClientServerInterpreter::ProcessCommandInvoke (this=this@entry=0xeacb40, css=..., midx=midx@entry=0) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:437 #14 0x7fffedc2f54d in vtkClientServerInterpreter::ProcessOneMessage (this=this@entry=0xeacb40, css=..., message=message@entry=0) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:269 #15 0x7fffedc2f75d in vtkClientServerInterpreter::ProcessStream (this=0xeacb40, css=...) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:238 #16 0x711f3469 in vtkPVSessionCore::ExecuteStreamInternal (this=0xeacad0, stream=..., ignore_errors=optimized out) ---Type return to continue, or q return to quit--- at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:668 #17 0x711f328e in vtkPVSessionCore::ExecuteStream (this=0xeacad0, location=optimized out, stream=..., ignore_errors=optimized out) at /usr/src/debug/ParaView-v4.1.0/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:638 #18 0x711f1f74 in
Re: [Paraview] Building Paraview with OSMesa llvmpipe
Hi Burlen, On 05/02/2014 03:27 PM, Burlen Loring wrote: Is GLU required for PV? At any rate GLU is not distributed with mesa. It can be found here: http://www.mesa3d.org/download.html I install GLU into the mesa install directory on my OSMesa dashboard builds with the attached script. I doubt if I would have gone to the trouble if I wasn't forced to. I do not install GLUT. update_mesa.sh Description: application/shellscript 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
Re: [Paraview] Building Paraview with OSMesa llvmpipe
Chris, Thunderbird sandwiched your e-mail between two of Burlen's and I replied to his e-mail instead of yours. Also my reply may have been useless to you as the OP. On 05/02/2014 02:35 PM, Chris Sideroff wrote: However when I attempt configure ParaView using the instructions towards the bottom of the wiki page, it complains about libGLU missing. I build Paraview for the dashboard in basically the same way as the wiki, but I also build glu in it's own source directory with : ./configure \ --prefix=/home/kevin/mesa_nightly make -ij8 make install That is I just install it to the same place where I put mesa. It has very few configure options, and I use none of them. 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
Re: [Paraview] Build errors due to missing OSMesa include directory
On 08/06/2013 01:05 PM, Burlen Loring wrote: Hi Paul, Could it be that you didn't set OPENGL_gl_LIBRARY library? For a while at least, ParaView assumed there was going to be some sort of screen usage if OPENGL_gl_LIBRARY was set. The instruction is still at the bottom of the wiki : http://paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D 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] CMake Generating ParaView Slowly
My machines that build ParaView for the dashboard seem to be taking an extremely long time in CMake generate step. This started this week but I can't find evidence of the builds on the dashboard before then. Does anybody know what's going on? 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
Re: [Paraview] CMake Generating ParaView Slowly
On 05/31/2013 09:26 AM, Utkarsh Ayachit wrote: The CMake configure/generation time has indeed grown long since the modularization changes. 4 hours for this Mesa DRI build : http://open.cdash.org/buildSummary.php?buildid=2922351 3 hours for this OSMesa build : http://open.cdash.org/buildSummary.php?buildid=2922048 While looking at a few other builds I saw only times of a few minutes. I'll experiment with this... 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
Re: [Paraview] CMake Generating ParaView Slowly
On 05/31/2013 09:26 AM, Utkarsh Ayachit wrote: The CMake configure/generation time has indeed grown long since the modularization changes. We did some preliminary investigation and couldn't find any smoking guns, unfortunately. I think what I'm seeing is specific to nightly cmake and ParaView. If I configure ParaView with system CMake version 2.8.9 cmake takes just 1m24.100s. However nightly cmake takes forever. Configuring VTK with system cmake takes just 0m46.588s versus 2m52.422s for nightly cmake. 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
Re: [Paraview] CMake Generating ParaView Slowly
On 05/31/2013 10:52 AM, Utkarsh Ayachit wrote: Oh, that's something totally weird and unexpected. Maybe the disk is dying or something? I think the thread has moved past this but to address the suggestion of disk failure: the issue began simultaneously on two systems both systems have mirrored disks which /proc/mdstat says are good smartd has reported no errors. 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] Adapt to VTK ExternalData
VTK has switched from using VTKData to ExternalData. VTKData is now almost empty and Paraview tests are failing on my dashboard machines murron and bubbles. 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
Re: [Paraview] Adapt to VTK ExternalData
On 05/22/2013 08:51 AM, Utkarsh Ayachit wrote: ParaView is not using VTK-master yet. It will be switched to use VTK-master only after the 4.0 release. We will be updating the testing then. I have always done a 'git pull' on VTKData, VTKLargeData, and ParaViewData before I run my dashboard scripts. The last commits in VTKData and VTKLargeData emptied out these directories. Should I check out the versions just before the external data change and stop updating them? 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
Re: [Paraview] 2d dataset, can i use paraview to interpolate values on x, y surface?
On 02/14/2013 05:57 PM, Ben Harrison wrote: I have been trying to see if I can use paraview to do some analysis and plotting of a 2d dataset exported in csv format. I believe csv files are imported as a sort of spreadsheet table. Use the Table To Points filter to convert them to points. My version even has a 2d option. I just want to know if paraview is the right choice (or even a decent choice) to do some basic visualisation of the data. I have a set of x,y points with about 6 attributes. for example, one field/attribute is temperature, another is heat flow in x direction, another heat flow in y direction. I am failing to understand how to create for example a 'surface' or contour plot of the temperature, or an 'arrow plot' of the 2d heat flow. Are your points triangulated? That is do they have connectivity information already, or are they just points with associated data? Without connectivity information ParaView does not know which points to interpolate between. The Delaunay2d filter will add a very reasonable triangulation of your date. Paraview will then display the data as a surface. Because the csv reader does not know that let's say columns 3 and four form a vector : Use the Calculator to combine fields into a vector Field 3*iHat + Field 4 * jHat should do it. Use the Glyph filter to display vectors. My efforts are also frustrated by regular but inconsistent segmentation faults when I try to 'apply' filters. Ubuntu Linux x86_64 paraview 3.14.1 installed from repositories I know inconsistent failures are very frustrating. If you can figure out when they occur we can help figure out why they occur and hopefully fix the problem. Is your system fully updated? Have you installed any software not from the repositories like graphics drivers? What graphics card do you have? What graphics driver do you have? Does Ubuntu have the equivalent of debuginfo packages? These restore all the information that is useful only to developers to the binaries and can make the output of a segfault _very_ informative. 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
Re: [Paraview] Is there any point to compiling with MPI but without offscreen rendering?
On 02/12/2013 04:44 PM, Utkarsh Ayachit wrote: Oops sorry, use pvbatch. You'll have to specify the script in a file on the command line however. $ export LD_LIBRARY_PATH=/home/kevin/drm_nightly/lib/:$LD_LIBRARY_PATH $ export LIBGL_DEBUG=verbose $ kitware/ParaView_Dual_Build/bin/pvbatch segpv.py libGL: OpenDriver: trying /home/kevin/mesa_dual/lib/dri/nouveau_dri.so libGL: Can't open configuration file /etc/drirc: No such file or directory. libGL: Can't open configuration file /home/kevin/.drirc: No such file or directory. libGL: Can't open configuration file /etc/drirc: No such file or directory. libGL: Can't open configuration file /home/kevin/.drirc: No such file or directory. $ unset DISPLAY $ kitware/ParaView_Dual_Build/bin/pvbatch --use-offscreen-rendering segpv.py :-) 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
Re: [Paraview] Is there any point to compiling with MPI but without offscreen rendering?
On 02/12/2013 12:16 PM, Utkarsh Ayachit wrote: I think I remember, try running pvpython with --use-offscreen-rendering It does not have this option. 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
Re: [Paraview] Is there any point to compiling with MPI but without offscreen rendering?
On 01/21/2013 02:35 PM, Utkarsh Ayachit wrote: Kevin, I gave using GL and OSMesa together using Mesa-9.0.1 with a ParaView 3.14.1 a try and unfortunately it still segfaults when creating a context when using OSMesa -- consistent with the behavior before glapi library was created. So alas, doesn't look like we can use onscreen and offscreen Mesa together as in the pre Mesa-7.9 days. Drat. I monitor the mesa-dev list (In bursts between projects) and it still sounds like mesa and it's build system are gradually becoming more flexible. 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
Re: [Paraview] Is there any point to compiling with MPI but without offscreen rendering?
On 01/21/2013 02:35 PM, Utkarsh Ayachit wrote: Kevin, I gave using GL and OSMesa together using Mesa-9.0.1 with a ParaView 3.14.1 a try and unfortunately it still segfaults when creating a context when using OSMesa How did you generate the segfault? Did you do an Xlib build or DRI? (shared glapi is disabled for xlib builds) I just did this build: http://open.cdash.org/buildSummary.php?buildid=2804770 which has hardware accelerated rendering and OSMesa. Mesa was built with the script : update_mesa_dual.sh. It fared no worse than my other DRI Mesa ( neither xlib nor OSMesa) builds. update_mesa_dual.sh Description: application/shellscript 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
Re: [Paraview] [EXTERNAL] Re: Still cannot add to selection with Crtl key
On 11/13/2012 12:05 PM, Scott, W Alan wrote: Utkarsh, I tried this on Linux, and it works fine. I just tried to Ctrl select multiple sets of points with the version of ParaView on Fedora 17. I was able to select multiple sets of points with the Select Points On button but not with the Select Points Through button. 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
Re: [Paraview] Is there any point to compiling with MPI but without offscreen rendering?
On 10/19/2012 03:54 PM, Utkarsh Ayachit wrote: and the resulting GL and OSMesa libraries both link glapi which was the source of the trouble with conflicting/hidden symbols : That's unfortunate. Guess we are still stuck with keep the two builds separate then. I'm sorry, I was sloppy in my use of the word link. I believe it may now be possible to build ParaView once with accelerated mesa and offscreen rendering in software. The GL and OSMesa libraries built as I described now link to the shared library glapi which was the source of missing symbols in the OSMesa library when the glapi object was compiled into the GL library and its symbols were hidden, and the source of conflicting symbols when the glapi object was compiled into both the GL and OSMesa libraries. Now that glapi is a stand alone shared library it should be no different than two shared libraries both linking the math library. 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
Re: [Paraview] Is there any point to compiling with MPI but without offscreen rendering?
On 10/22/2012 10:15 AM, Utkarsh Ayachit wrote: Ah..cool. What version of Mesa is this 9.0 or 8.0.*? I compiled mesa from git. 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
Re: [Paraview] Is there any point to compiling with MPI but without offscreen rendering?
On 10/18/2012 10:49 AM, Utkarsh Ayachit wrote: So we have onscreen and offscreen rendering and what type of offscreen rendering is used depends on whether we built with OSMesa. That was the case for the longest time. Now, with Mesa 7.9, Mesa folks decided that applications could no longer link against libOSMesa and libGL at the same time. That means that we can no longer support onscreen and offscreen with OSMesa in the same build of ParaView (http://paraview.org/Wiki/ParaView_And_Mesa_3D). Of course, if someone has ideas on overcoming this issue, I'm all ears. There has been some chatter on the Mesa developers list that sounds like this may be fixed. 1. The mesa build system underwent a _major_ overhaul. 2. building glapi as a shared object sounds like it _might_ overcome the mess that involved hidden/duplicate symbols, needed by both GL and OSMesa. 3. Then there's this resolved bug: https://bugs.freedesktop.org/show_bug.cgi?id=6980 that seems to say go ahead -lGL -lOSMesa I'll give it a try again. 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
Re: [Paraview] Is there any point to compiling with MPI but without offscreen rendering?
On 10/19/2012 10:25 AM, Utkarsh Ayachit wrote: Interesting. Although I am not sure if the mesa developers simply mean that you can build libGL and libOSMesa at the same time (which is indeed possible). But worth a try. I will test it out with the latest mesa and get back to the list. I am positive this didn't work with the 7.* series. Utkarsh I have to go do a physiological experiment in a few minutes but I just built mesa with: env PKG_CONFIG_PATH=/home/kevin/drm_nightly/lib/pkgconfig/ ./configure --prefix=/home/kevin/mesa_dual/ --enable-osmesa --with-gallium-drivers=r300,r600,nouveau,swrast --with-dri-drivers=swrast and the resulting GL and OSMesa libraries both link glapi which was the source of the trouble with conflicting/hidden symbols : [kevin@bubbles lib]$ ldd libOSMesa.so | grep glapi libglapi.so.0 = /home/kevin/mesa_dual/lib/libglapi.so.0 (0x7f6aea46) [kevin@bubbles lib]$ ldd libGL.so | grep glapi libglapi.so.0 = /home/kevin/mesa_dual/lib/libglapi.so.0 (0x7f352f8c2000) 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
Re: [Paraview] Is there any point to compiling with MPI but without offscreen rendering?
On 10/08/2012 01:21 PM, Cook, Rich wrote: I'm also personally unsure about where there is a switch for --use-offscreen-rendering. If I compile with OSMesa, I'm always going to want that, right? I think that depending on how you built OSMesa it's all you _can_ do. And if OpenGL, I'm always going to disable that, right? Why is there a command line switch for that? You can render off screen with X and graphics hardware but without the render window actually showing up on screen. 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] Image Slice Rep XZ/YZ Slice Slider Range Bug
There is a bug in the image slice representation in ParaView from git. In slice directions other than XY the slice slider range is limited to the number of XY slices. To see the bug use the wavelet source with extent: -100 100 -100 100 -10 10 Change the representation to slice, the slice direction to XY, and the camera viewto the -Z direction. Use the slider to view all the slices orthogonal to the Z axis. Now change the slice direction to XZ (or YZ), and the camera view to the -Y (or -X) direction. Use the slider to try and see all the slices orthogonal to the Y (or X) axis. Observe that the slider range is limited to the first 20 slices. Other slices can be seen by entering their number in the text entry box. Enter 100 and see a slice through the middle that could not be reached using the slider. I reported this as : http://paraview.org/Bug/view.php?id=13421 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
Re: [Paraview] No GUI Build
On 08/24/2012 11:25 AM, Utkarsh Ayachit wrote: Kevin, Fixes for the python tests have gone into paraview master today. We should see the failures go down a bit by tommorrow -- fingers crossed. Utkarsh I think this build : http://open.cdash.org/buildSummary.php?buildid=2531668 should be more or less what will happen tonight. 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] No GUI Build
I'm trying a server only build without QT : http://open.cdash.org/buildSummary.php?buildid=2524686 I'm trying to build against OSMesa so there should be no paraview GUI. There's a configure error that seems to be about the missing paraview. Did I miss something in the configuration? 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
Re: [Paraview] No GUI Build
On 08/20/2012 10:44 AM, Utkarsh Ayachit wrote: Just pushed a fix to git-next. Attached is the patch. This patch is built here: http://open.cdash.org/buildSummary.php?buildid=2525467 There still seems to be a build error in ParticlesViewer example. 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
Re: [Paraview] No GUI Build
On 08/20/2012 12:43 PM, Utkarsh Ayachit wrote: Thanks again. Pushed a fix (patch attached). Your very welcome :-) An OSMesa build with both patches is here : http://open.cdash.org/buildSummary.php?buildid=2525527 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
Re: [Paraview] No GUI Build
On 08/20/2012 01:23 PM, Utkarsh Ayachit wrote: Just pushed a fix for the IceT tests. Let's see how those fare. Sorry, git is not being kind to me. When I checkout next and update submodules I get: $ git submodule update fatal: reference is not a tree: 5592cbda186f42afec7b3299059975af868423a3 Unable to checkout '5592cbda186f42afec7b3299059975af868423a3' in submodule path 'VTK' 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
Re: [Paraview] No GUI Build
On 08/20/2012 03:02 PM, Utkarsh Ayachit wrote: You'll have to manually fetch pvvtk remote. Start by calling Utilities/SetupForDevelopment.sh from ParaView source dir and that will set up all remotes. Then cd into VTK and do a git fetch pvvtk. You won't need this once the changes make into PAraView mater. Utkarsh My mental image of the source tree just got a little more complex. Here is a build with those changes : http://open.cdash.org/buildSummary.php?buildid=2525588 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
Re: [Paraview] 3.12.0-RC3: could not open source file GL/gl.h compiling vtkIceTSynchronizedRenderers.cxx
On 11/05/2011 06:13 AM, Takuya OSHIMA wrote:
Hi,
I tried to build the 3.12.0 RC3 with MesaLib-7.11 (OSMesa) on a RHEL
5.1 headless cluster and got an error:
/nfs/work2/v14/v14006/src/ParaView-3.12.0-RC3/VTK/Rendering/vtkOpenGL.h(26):
catastrophic error: could not open source file GL/gl.h
# include GL/gl.h // Include OpenGL API.
^
compilation aborted for
/nfs/work2/v14/v14006/src/ParaView-3.12.0-RC3/ParaViewCore/ClientServerCore/vtkIceTSynchronizedRenderers.cxx
(code 4)
make[2]: ***
[ParaViewCore/ClientServerCore/CMakeFiles/vtkPVClientServerCore.dir/vtkIceTSynchronizedRenderers.cxx.o]
Error 4
Looking into ParaViewCore/ClientServerCore/CMakeLists.txt I found
nothing that specifies ${OPENGL_INCLUDE_DIR} as opposed to the old
ParaView-3.10.1/Servers/Filters/CMakeLists.txt (where
vtkIceTSynchronizedRenderers.cxx had been in) having
I build PareView with OSMesa from their git repositories every
night.
Could you please post your CMakeCache.txt to a public server or
tell us the CMake variables you set?
The OSMesa related variables I set are :
OPENGL_INCLUDE_DIR:PATH=/home/kevin/mesa_osmesa/include
OPENGL_gl_LIBRARY:FILEPATH=
OPENGL_glu_LIBRARY:FILEPATH=/home/kevin/mesa_osmesa/lib/libGLU.so
VTK_OPENGL_HAS_OSMESA:BOOL=ON
OSMESA_INCLUDE_DIR:PATH=/home/kevin/mesa_osmesa/include
OSMESA_LIBRARY:FILEPATH=/home/kevin/mesa_osmesa/lib/libOSMesa.so
VTK_USE_OFFSCREEN:BOOL=ON
VTK_USE_X:BOOL=OFF
# This file began with the notes from dash21.kitware and was edited
# by Kevin Hobbs h b s @ h o . d
# o b k o i u e u
###
# The values in this section must always be provided
###
set(CTEST_SITE murron.hobbs-hancock)
set(CTEST_BUILD_NAME Fedora-15-MesaDevel_OSMesa-x86_64)
set(source_dir ParaView)
set(build_dir ParaView_OSMesa_Build)
SET(CTEST_DASHBOARD_ROOT $ENV{HOME}/kitware)
set(CTEST_BUILD_CONFIGURATION Release)
set(CTEST_CMAKE_GENERATOR Unix Makefiles)
set(CTEST_NOTES_FILES ${CTEST_SCRIPT_DIRECTORY}/${CTEST_SCRIPT_NAME})
set(CTEST_SOURCE_DIRECTORY ${CTEST_DASHBOARD_ROOT}/${source_dir})
set(CTEST_BINARY_DIRECTORY ${CTEST_DASHBOARD_ROOT}/${build_dir})
set(CTEST_BUILD_COMMAND make -i -j8)
#set(CTEST_GIT_COMMAND git)
set(CTEST_GIT_COMMAND ${CTEST_DASHBOARD_ROOT}/gitmod.sh)
ctest_empty_binary_directory(${CTEST_BINARY_DIRECTORY})
# Write initial cache.
file(WRITE ${CTEST_BINARY_DIRECTORY}/CMakeCache.txt
CMAKE_BUILD_TYPE:STRING=${CTEST_BUILD_CONFIGURATION}
BUILD_EXAMPLES:BOOL=ON
BUILD_SHARED_LIBS:BOOL=ON
OPENGL_INCLUDE_DIR:PATH=/home/kevin/mesa_osmesa/include
OPENGL_gl_LIBRARY:FILEPATH=
OPENGL_glu_LIBRARY:FILEPATH=/home/kevin/mesa_osmesa/lib/libGLU.so
PARAVIEW_BUILD_ParaView:BOOL=OFF
PARAVIEW_BUILD_QT_GUI:BOOL=OFF
PARAVIEW_ENABLE_PYTHON:BOOL=ON
PARAVIEW_USE_MPI:BOOL=ON
VTK_OPENGL_HAS_OSMESA:BOOL=ON
#MPIEXEC_PREFLAGS:STRING=-mca btl ^sm
OSMESA_INCLUDE_DIR:PATH=/home/kevin/mesa_osmesa/include
OSMESA_LIBRARY:FILEPATH=/home/kevin/mesa_osmesa/lib/libOSMesa.so
VTK_USE_OFFSCREEN:BOOL=ON
VTK_USE_X:BOOL=OFF
)
ctest_start(Nightly)
ctest_update(SOURCE ${CTEST_SOURCE_DIRECTORY})
ctest_configure(BUILD ${CTEST_BINARY_DIRECTORY})
ctest_read_custom_files(${CTEST_BINARY_DIRECTORY})
ctest_build(BUILD ${CTEST_BINARY_DIRECTORY})
ctest_test(BUILD ${CTEST_BINARY_DIRECTORY})
ctest_submit()
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
Re: [Paraview] Doubt regarding the installation of Paraview in Unix like systems.
On 10/26/2011 11:09 AM, Sriram Ragav wrote: Dear Jean, I ahve downloaded and installed a newer version in a separate folder. The installation guide says Use ccmake (Curses CMake GUI) from the CMake installed location. CCMake is a Curses based GUI for CMake. To run it go to the build directory and specify as an argument the src directory. I am not sure what it means. I have used the same set of commands available. But still only cmake version 2.6 is called. Can you pls explain me what the sentence means!! I usually do this: cd ~/ # Go to my home directory # Download CMake source wget http://www.cmake.org/files/v2.8/cmake-2.8.6.tar.gz tar -xzvf cmake-2.8.6.tar.gz # Extract CMake mkdir cmake-2.8.6_build # make a cmake build directory cd cmake-2.8.6_build # go into the build directory ccmake ../cmake-2.8.6 # configure cmake with system cmake make -j8 # build cmake in parallel # you can run it from the build directory without installing cd ~/ # Go to my home directory # Download ParaView source wget http://paraview.org/files/v3.12/ParaView-3.12.0-RC2.tar.gz tar -xzvf ParaView-3.12.0-RC2.tar.gz # extract paraview mkdir ParaView-3.12.0-RC2_build # make a ParaView build directory cd ParaView-3.12.0-RC2_build/ # go into the build directory # now this is the part where you seem to be confused # configure ParaView with the CMake we just built ../cmake-2.8.6_build/bin/ccmake ../ParaView-3.12.0-RC2 make -j8 # build ParaView in parallel bin/paraview # run paraview from the build directory 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] 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
Re: [Paraview] 3.10.1 Issues with resizing with OSMesa
On 05/05/2011 04:09 PM, Utkarsh Ayachit wrote: Folks, Recently an issue was noticed by some of our users. Evidently, when resizing ParaView client that is connected to a pvserver using OSMesa, the server would hang if there were any text items (such as Text source) in the view. I am trying to gauge if any other users have seem similar issues. Utkarsh _ I can not reproduce the problem with the development versions of ParaView and Mesa on murron. I will try again with ParaView-3.10.1 and Mesa-7.10.2 when I get to work. 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
Re: [Paraview] 3.10.1 Issues with resizing with OSMesa
On 05/05/2011 04:09 PM, Utkarsh Ayachit wrote: Folks, Recently an issue was noticed by some of our users. Evidently, when resizing ParaView client that is connected to a pvserver using OSMesa, the server would hang if there were any text items (such as Text source) in the view. I am trying to gauge if any other users have seem similar issues. I was not able to reproduce the problem using ParaView-3.10.1 and Mesa-7.10.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
Re: [Paraview] Paraview v3.10.1/0 segmentation fault with MPI and MESA support on.
On 04/20/2011 11:42 AM, Albina, Frank wrote: I think I should be able to fix the issue by building correctly the MESA libs for my purpose then. Have you succeeded? 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
Re: [Paraview] Paraview v3.10.1/0 segmentation fault with MPI and MESA support on.
On 04/20/2011 05:22 AM, Albina, Frank wrote: Hi Kevin! Thank you very much for the support so far. What I am trying to achieve is to have: a) the whole paraview suite, i.e. paraview, pvbatch, pvserver built from scratch. b) with X, independently of offscreen or onscreen rendering c) with Mesa using xlib drivers: ./configure --prefix=/code/CFD/develop/opt/share/Mesa-7.9.2 --with-x --enable-gl-osmesa --build=x86_64-suse-linux --with-driver=xlib --enable-glu --enable-glw --enable-pic --enable-opengl If you are going to use X with all of ParaView then you will need to link against libGL.so from mesa-7.9.2 which conflicts with libOSMesa.so from mesa-7.9.2 so there is no point in adding the --enable-gl-osmesa flag. What I'd like to achieve is a stand-alone paraview version with X support, from which one can start pvserver for performing offscreen rendering via MESA. If one does not start the pvserver remotely, one should still be able to use paraview with onscreen rendering, still using MESA as the rendering engine (i.e. without system OpenGL support, in other words without GPU rendering). Please let me know if this is still unclear. You can have this but it's more complicated : even though your pvserver will use offscreen rendering it will still open a window, you will need an X server running on each of the compute nodes, you will have to have the display variable set to point to the X server on each compute node, and each pvserver process will have to have permissions to use the server on its node. The the windows that each pvserver process renders into will not be visible on monitors ( if there are any ) connected to the compute nodes. They will not be covered or cover any other window so you won't get random bits of other programs showing up in the final output. But they will exist. Following the steps on the paraview WIKI does not seem to work, unless I am mistaken, which I guess I am at the time being. The steps on the wiki are a bit of a mix of what you can do with old and new versions of Mesa. Again, I had had no issues building and running paraview v3.8.1, whereas paraview v3.10.x is giving me a segmentation fault at screen start. I can not comment on what might have changed. Thank you very much for the script anyway. I sure will make good use of it. Cheers, Frank. 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
Re: [Paraview] Paraview v3.10.1/0 segmentation fault with MPI and MESA support on.
On 04/19/2011 12:29 PM, Albina, Frank wrote: Thank you very for your help anyway and please let me know if you have made any progress with building paraview on your cluster. The script I will use to update the software in /opt on our cluster is attached. I'm about to try it (I've done bits but not the whole thing) you might want to replace all of the /opts with something that does not require root privileges... You'll want to pare the script down as you may not want ITK, VTK, and CMake. I'll get back to you after I test the install. build_opt_software.sh Description: application/shellscript 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
Re: [Paraview] Paraview v3.10.1/0 segmentation fault with MPI and MESA support on.
This one runs as user and sudo's the right things... build_opt_software.sh Description: application/shellscript 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] git bisect results hooperlab OSMesa build failures
The hooperlab OSMesa builds have been failing for two days. I did a git bisect on ParaView (VTK OSMesa isn't failing) and came up with : 25ea37421df423f132e014da31d6cbdca5caad2a is the first bad commit commit 25ea37421df423f132e014da31d6cbdca5caad2a Author: Utkarsh Ayachit utkarsh.ayac...@kitware.com Date: Mon Oct 18 13:08:27 2010 -0400 Forwarding VTK to bring in latest paraview_views_refactoring merge. :16 16 b1683b8880964f69d7ecb3f918618c6422897d8b 91e89e83dbc2a317f08f0715cafffa7f10ce7841 M VTK I'll redo the bisection on the VTK in ParaView. 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
Re: [Paraview] [paraview] compiling Mesa with paraview
On 10/14/2010 10:13 AM, Joshua Wu wrote: I'm recently started to install paraview on a new machine, OS is Ubuntu, a 64 bit machine. Mesa itself is built smoothly and my cmake configuration is the same as I built before (I successfully built Mesa with PV many times), I've tried three versions of Mesa to be integrated into PV, 7.9, 7.6.1 and 7.0.4. About 48% of building PV, I get the following consistent error --- /home/joshuawu/remoteparaview/mesa/Mesa-7.0.4/lib64/libOSMesa.so.6: undefined reference to `_mesa_create_framebuffer' Mesa has suffered some turmoil lately as far as OSMesa is concerned. The end result is that the most recent version of mesa and the development version can not have libOSMesa.so and libGL.so (not even the one produced along with OSMesa) linked by the same application. My OSMesa build configuration is here : http://www.cdash.org/CDash/viewNotes.php?buildid=748789 I build Mesa from git every night like this : rm -rf /home/kevin/mesa_osmesa/* cd /home/kevin/mesa make realclean git pull origin ./autogen.sh \ --prefix=/home/kevin/mesa_osmesa/ \ --with-driver=osmesa \ --disable-gallium make -j8 make install 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] OSMesa Build FindQt4 Error
This build : http://www.cdash.org/CDash/buildSummary.php?buildid=747901 and the hooperlab builds like it, all report a build error related to FindQt4.cmake. CMake is the development version from git. These builds use OSMesa and should not be using the GUI. They have CMake variables set which I think mean QT should not be touched at all : PARAVIEW_BUILD_ParaView:BOOL=OFF PARAVIEW_BUILD_QT_GUI:BOOL=OFF In any case I told CMake where to find qmake : QT_QMAKE_EXECUTABLE:FILEPATH=/usr/bin/qmake-qt4 and the error persists. 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
Re: [Paraview] Error building paraview server without X server support: vtkXdmf fails
Hi Jorge, On 09/27/2010 05:21 AM, Jorge Gerardo Peña Pastor wrote: Hello everybody, I am trying to compile the paraView server to use inside a cluster withou rendering hardware. I have configured the CMakeLists to use the following options: PARAVIEW_BUILD_QT_GUI = OFF VTK_OPENGL_HAS_OSMESA = ON VTK_USE_DISPLAY = OFF VTK_USE_OFFSCREEN = ON VTK_USE_QT = OFF VTK_USE_X = OFF Nevertheless, when I run make pvserver I get an error compiling vtkXdmf: X11/StringDefs.h: file not found when trying to compile vtkXdmfRenderWindowIteractor and also other files/declarations are missing: Widget, XtPointer, XEvent, XtIntervalId, XtappContext, and more... I think that these objects are trying to compile against the X libraries, but according to my CMakeLists, they shouldn't. I guess I missed flag or need to install some extra libraries, but I cannot realize which one. Do you know where the error comes from? Thak you, I think I had to set OPENGL_gl_LIBRARY to an empty string, that is : OPENGL_gl_LIBRARY:FILEPATH= 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
Re: [Paraview] pvbatch (3.8.0) rendering through OSmesa does not work on multiple nodes
On 09/22/2010 12:06 PM, Van Mierlo K. wrote: I have compiled osmesa 7.5.2 and the newest release candidate osmesa 7.8.3-rc1. Unfortunately pvbatch 3.8.0 using either of these libraries gives the same output and the render error persists. I use the following command to configure / compile the osmesa library: ./configure --with-driver=osmesa --without-x --disable-glu --disable-egl --disable-gallium --prefix=/home/kvm/mesa752 --exec_prefix=/home/kvm/mesa752 Allthough it would be nice to solve this error it will not have my priority since I can easily render my dataset on a single node of the cluster. Koen If you could provide the dataset or a complete example using data from ParaViewData or a source I'll give it a try on our cluster which has (or will have PV and Mesa from git now that Mesa's git seems to be back in order). 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
Re: [Paraview] pvbatch (3.8.0) rendering through OSmesa does not work on multiple nodes
On 09/16/2010 09:12 AM, Dave Partyka wrote: I would recommend using mesa 7.0.4 or 7.5.x until the issue is fixed upstream. My dashboard builds from *.hooperlab and murron.hobbs-hancock use mesa from the git repository. Is there any test that shows whether this bug has been fixed? 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
Re: [Paraview] pvbatch (3.8.0) rendering through OSmesa does not work on multiple nodes
On 09/16/2010 09:39 AM, Dave Partyka wrote: Humm, it must be fixed then in their git repo as all the rendering tests would fail. Which was the case, on those dashboards about a month ago if I remember correctly? You do remember correctly, but there were many reasons why large numbers of tests were failing. 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] Dashboard build changes
Due to changes in the way Mesa is built since 7.8.2 Mesa's OSMesa and software GL libraries cannot be linked in the same application. My dashboard builds were failing because of this change. So instead of submitting a single MesaDevel build all of my machines are now submitting three separate builds : MesaDevel_Xlib using mesa's software GL only MesaDevel_OSMesa using mesa's OSMesa only MesaDevel_MGL using mesa's software GL and mangled OSMesa 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] Murron OS Update
The operating system on the dashboard site murron.hobbs-hancock has been updated from fedora 12 to fedora 13 and all of the build names have been changed to show the new OS. 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] Dashboard Site OS Update
The operating system on the dashboard site bubbles.hooperlab has been updated from Fedora 11 to Fedora 12 and the build name has been changed accordingly. 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] Parallel Testing
I just tried an experimental build on bubbles with testing done in parallel. This is the result : http://www.cdash.org/CDash/viewTest.php?onlyfailedbuildid=597827 I did another test without the dreaded PV_TEST_INIT_COMMAND:STRING=killall -9 pvserver;... line but the results weren't much better. http://www.cdash.org/CDash/viewTest.php?onlyfailedbuildid=597827 The solutions I can think of are to set the RUN_SERIAL CTest property for these tests or to adjust the ports used for these tests. 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
Re: [Paraview] Dashboards submitted but missing
On 04/26/2010 10:53 AM, Dave Partyka wrote: We switched to git! Most of the dashboards are switched over using a new paraview_common script (very similar to the cmake_common one you may be familiar with). Though it seems the rewritten scripts aren't functional on many machines. I will resume getting them to submit over the comming days as I get a chance to spend time and see whats wrong on each of them. Where do I get paraview_common.cmake and vtk_common.cmake? I can get my builds to work with git but I noticed that parallel building is broken for my old scripts so I guess it's time for an update. 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
Re: [Paraview] Dashboards submitted but missing
On 04/27/2010 01:39 PM, Dave Partyka wrote: If you look here you can see vtk_common. http://www.cdash.org/CDash/viewNotes.php?buildid=595568 http://www.cdash.org/CDash/viewNotes.php?buildid=595568And here is paraview_common. http://www.cdash.org/CDash/viewNotes.php?buildid=595953 What! Copy and paste from a web page! With all this talk of the CVS to git transition I forgot I could do that until just after I sent that last e-mail. Though if you have you're own simpler script that is perfectly fine. The common scripts attempt to make things easier by deleting your source tree if it is using CVS still doing the initial commit and submodule updates. OK, I try a little harder to find the right combination variables to get the parallel build to work. Thank you! 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] Parallel build/test and git
This is probably a cmake issue but... I can not get cmake-2.8.1 or cmake built from cvs to build ParaView (VTK, or ITK) in parallel. I have tried setting both set(CTEST_BUILD_FLAGS -i -j8) and set(CTEST_BUILD_COMMAND /usr/bin/gmake -i -j8) but neither has any effect. The old CMakeCache.txt variable MAKECOMMAND:STRING=/usr/bin/gmake -i -j8 works only for cmake-2.6 ( and earlier. ) cmake-2.6 does not support git. cmake-2.6 does not support parallel testing. 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
Re: [Paraview] Parallel build/test and git
On 04/27/2010 03:40 PM, David E DeMarle wrote:
Hmm, I believe kargad is building its submission in parallel:
cmake-2.8.1
set (CTEST_BUILD_FLAGS -j 8)
Do you actually see 8 compiler processes?
The time seems right but I don't trust the times on the dashboard right now.
Maybe there is something to be gleaned from:
http://www.cdash.org/CDash/viewNotes.php?buildid=596035
?
I don't see anything new there unless paraview_common.cmake is changing
very rapidly and everybody has a different version.
This is what makes me the most doubtful :
$ find CMake/ -exec grep -l CTEST_BUILD_FLAGS '{}' \;
CMake/Source/CTest/cmCTestBuildCommand.cxx
$ grep CTEST_BUILD_FLAGS CMake/Source/CTest/cmCTestBuildCommand.cxx
: this-Makefile-GetDefinition(CTEST_BUILD_FLAGS);
[ke...@bubbles kitware]$
CTEST_BUILD_FLAGS is mentioned only once in all of CMake!
It's not mentioned at all in ParaView.
$ find ParaView/ -exec grep -l CTEST_BUILD_FLAGS '{}' \;
$
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
Re: [Paraview] Parallel build/test and git
On 04/27/2010 04:40 PM, David E DeMarle wrote:
I just confirmed that it does spawn 8 compiler instances, I do not
pretend to understand the cmake magic behind it.
I just got 12 compiler instances out of a test cmake script that just has :
# Client maintainer: hob...@ohiou.edu
set(CTEST_SITE bubbles.hooperlab)
set(CTEST_BUILD_NAME ParallelBuildTest)
set(CTEST_BUILD_CONFIGURATION Debug)
set(CTEST_CMAKE_GENERATOR Unix Makefiles)
set(CTEST_BUILD_FLAGS -i -j 12)
include(${CTEST_SCRIPT_DIRECTORY}/paraview_common.cmake)
I guess it's time to start adding lines one at a time...
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] Dashboards submitted but missing
For seven days all of my builds have been missing from the dashboard. I just looked at ParaView3_Build/Testing/Temporary/LastSubmit_20100426-0100.log on bubbles and murron and they say that the submission was successful. Does anybody know what's going on? 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
Re: [Paraview] Dashboards submitted but missing
On 04/26/2010 10:53 AM, Dave Partyka wrote: We switched to git! Since I'll be spending the afternoon re-configuring my dashboard scripts, is there a page detailing how to make a dashboard submission the with git and the new paraview_common scripts? 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
Re: [Paraview] Fullscreen Screenshot/Animation
On 04/21/2010 09:27 AM, Utkarsh Ayachit wrote: You can already specify the resolution explicitly when saving screenshots as well as exporting animation movies. Doesn't simply specifying the same resolution as your monitor do the same thing? Utkarsh If you aren't in full screen mode won't you then be exposed to the tiling bugs with volume rendering and wireframes that happen when the output image is larger than the render window? Or have these been cleared up? 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
Re: [Paraview] Experience with hanging OpenMPI
On 04/09/2010 02:44 PM, pat marion wrote: Hi, just thought I'd share this in case someone else runs into the same issue- After upgrading my computer to dual quad-core intel xeons, and installing Ubuntu Karmic (9.10), pvserver with mpi would hang after a few renders. It turns out it was this bug: https://bugs.launchpad.net/ubuntu/+source/openmpi/+bug/504659 https://svn.open-mpi.org/trac/ompi/ticket/2043 I removed the openmpi-bin and libopenmpi-dev packages and installed libmpich2-dev and mpich2. Now everything is stable! Pat You can work around this bug by increasing the number of fifos open mpi uses. This avoids the race condition where all the fifos seem to be in use. Add : -mca btl_sm_num_fifos 16 to the mpirun command line. 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] Dashboard Failures from *.hooperlab
What can I do to help with the 5 tests that have been failing on all of my dashboard submissions? These account for 20 / 35 of the test failures in Nightly expected and 25 / 217 in Nightly. 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
Re: [Paraview] Dashboard Failures from *.hooperlab
On 03/26/2010 09:55 AM, Dave Partyka wrote: Hey Kevin, For those 5 can you run them by hand and see if you notice why they are hanging/failing? On some of them it looks like pvserver might be crashing? Can you attach a debugger and see if you can get a stack trace? Thank you very much for offering to help. pv.XdmfReadStructuredGrid.XdmfReadStructuredGridCollection.XdmfGridAttributes I got an Output Messages window that says : ERROR: In /home/kevin/kitware/ParaView3/VTK/IO/vtkPNGReader.cxx, line 53 vtkPNGReader (0x4bdb950): Unknown file type! Not a PNG file! This text appeared on the console but I could not reproduce it. I tried to narrow the problem down so I ran each of the three parts separately. The XdmfGridAttributes.xml part is failing. 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
Re: [Paraview] Dashboard Failures from *.hooperlab
On 03/26/2010 09:55 AM, Dave Partyka wrote: Hey Kevin, For those 5 can you run them by hand and see if you notice why they are hanging/failing? On some of them it looks like pvserver might be crashing? Can you attach a debugger and see if you can get a stack trace? Thank you very much for offering to help. pvcrs.ExodusIIPanel.ExodusModeShapes The two data servers are spinning which reminded me of an openmpi bug so I stuck btl_sm_num_fifos = 15 in ~/.openmpi/mca-params.conf but that didn't help. I got back traces for the render server and the two data servers: (gdb) attach 4998 [Thread debugging using libthread_db enabled] 0x0032456d6f73 in __select_nocancel () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install e2fsprogs-libs-1.41.9-2.fc11.x86_64 expat-2.0.1-8.fc11.x86_64 fontconfig-2.8.0-1.fc11.x86_64 freetype-2.3.9-5.fc11.x86_64 glib2-2.20.5-1.fc11.x86_64 glibc-2.10.2-1.x86_64 keyutils-libs-1.2-5.fc11.x86_64 krb5-libs-1.6.3-27.fc11.x86_64 libICE-1.0.4-7.fc11.x86_64 libSM-1.1.0-4.fc11.x86_64 libX11-1.2.2-1.fc11.x86_64 libXau-1.0.4-5.fc11.x86_64 libXcursor-1.1.9-4.fc11.x86_64 libXext-1.0.99.1-3.fc11.x86_64 libXfixes-4.0.3-5.fc11.x86_64 libXi-1.2.1-1.fc11.x86_64 libXinerama-1.0.3-4.fc11.x86_64 libXrandr-1.2.99.4-3.fc11.x86_64 libXrender-0.9.4-5.fc11.x86_64 libXt-1.0.5-2.fc11.x86_64 libgcc-4.4.1-2.fc11.x86_64 libpng-1.2.43-1.fc11.x86_64 libselinux-2.0.80-1.fc11.x86_64 libstdc++-4.4.1-2.fc11.x86_64 libxcb-1.2-5.fc11.x86_64 openmpi-1.4-5.fc11.x86_64 openssl-0.9.8k-5.fc11.x86_64 python-libs-2.6-12.fc11.x86_64 qt-4.6.2-8.fc11.x86_64 qt-x11-4.6.2-8.fc11.x86_64 zlib-1.2.3-22.fc11.x86_64 (gdb) bt #0 0x0032456d6f73 in __select_nocancel () from /lib64/libc.so.6 #1 0x7fa5150d08cb in vtkSocket::SelectSockets(int const*, int, unsigned long, int*) () from /home/kevin/kitware/ParaView3_Build/bin/libvtkCommon.so.pv3.7 #2 0x7fa5150d1044 in vtkSocketCollection::SelectSockets(unsigned long) () from /home/kevin/kitware/ParaView3_Build/bin/libvtkCommon.so.pv3.7 #3 0x7fa51f491584 in vtkProcessModuleConnectionManager::MonitorConnections(unsigned long) () from /home/kevin/kitware/ParaView3_Build/bin/libvtkPVServerCommon.so #4 0x7fa51f497cdc in vtkProcessModule::StartServer(unsigned long) () from /home/kevin/kitware/ParaView3_Build/bin/libvtkPVServerCommon.so #5 0x7fa51f4997c7 in vtkProcessModule::Start(int, char**) () from /home/kevin/kitware/ParaView3_Build/bin/libvtkPVServerCommon.so #6 0x7fa51f09e246 in vtkPVMain::Run(vtkPVOptions*) () from /home/kevin/kitware/ParaView3_Build/bin/libvtkPVFilters.so #7 0x0040112c in main () (gdb) detach (gdb) attach 5001 [Thread debugging using libthread_db enabled] 0x7f19b2bd1b6b in opal_class_initialize () from /usr/lib64/openmpi/lib/openmpi/mca_btl_sm.so (gdb) bt #0 0x7f19b2bd1b6b in opal_class_initialize () from /usr/lib64/openmpi/lib/openmpi/mca_btl_sm.so #1 0x0033c3a123aa in opal_progress () from /usr/lib64/openmpi/lib/libopen-pal.so.0 #2 0x0033c42363c5 in ?? () from /usr/lib64/openmpi/lib/libmpi.so.0 #3 0x7f19b1b10b6a in opal_class_initialize () from /usr/lib64/openmpi/lib/openmpi/mca_coll_tuned.so #4 0x7f19b1b1906f in opal_class_initialize () from /usr/lib64/openmpi/lib/openmpi/mca_coll_tuned.so #5 0x7f19b1d2890b in opal_class_initialize () from /usr/lib64/openmpi/lib/openmpi/mca_coll_sync.so #6 0x0033c4253f39 in PMPI_Gatherv () from /usr/lib64/openmpi/lib/libmpi.so.0 #7 0x7f19bb55ceb7 in vtkMPICommunicator::GatherVVoidArray(void const*, void*, long long, long long*, long long*, int, int) () from /home/kevin/kitware/ParaView3_Build/bin/libvtkParallel.so.pv3.7 #8 0x7f19c279b111 in vtkMPIMoveData::DataServerGatherToZero(vtkDataObject*, vtkDataObject*) () from /home/kevin/kitware/ParaView3_Build/bin/libvtkPVFilters.so #9 0x7f19c279b9b6 in vtkMPIMoveData::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () from /home/kevin/kitware/ParaView3_Build/bin/libvtkPVFilters.so #10 0x7f19b8d73c44 in vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) () from /home/kevin/kitware/ParaView3_Build/bin/libvtkFiltering.so.pv3.7 #11 0x7f19b8d667ac in vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () from /home/kevin/kitware/ParaView3_Build/bin/libvtkFiltering.so.pv3.7 #12 0x7f19b8d44d01 in vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () from /home/kevin/kitware/ParaView3_Build/bin/libvtkFiltering.so.pv3.7 #13 0x7f19b8d69819 in vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () from /home/kevin/kitware/ParaView3_Build/bin/libvtkFiltering.so.pv3.7 #14 0x7f19b8eb1751 in vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () from
Re: [Paraview] Dashboard Failures from *.hooperlab
On 03/26/2010 10:52 AM, Kevin H. Hobbs wrote: On 03/26/2010 09:55 AM, Dave Partyka wrote: Hey Kevin, For those 5 can you run them by hand and see if you notice why they are hanging/failing? pv.XdmfReadStructuredGrid.XdmfReadStructuredGridCollection.XdmfGridAttributes I tried to narrow the problem down so I ran each of the three parts separately. The XdmfGridAttributes.xml part is failing. XdmfGridAttributes.xml mentions only one file : $PARAVIEW_DATA_ROOT/Data/RodPlate/RodPlate.xmf When I load this file in paraview there are many data arrays but they are all zeros except for MaterialID which is all ones. 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] Dashdoard Breakage
Since March 17 all of my dashboard submissions that use CTest from CVS show many build errors. The submissions that use CTest 2.6 are relatively fine. These are my submissions : http://www.cdash.org/CDash/index.php?project=ParaView3filtercount=2showfilters=1filtercombine=orfield1=site/stringcompare1=63value1=hooperlabfield2=site/stringcompare2=63value2=hobbs-hancock 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
Re: [Paraview] Dashdoard Breakage
On 03/19/2010 12:05 PM, Clinton Stimpson wrote: I'll fix it. I missed a few places with yesterday's fixes. Thanks, Clint If you send me a note when you're done, then I'll happily submit a test build. 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
Re: [Paraview] Paraview 3.6.2 / Open MPI 1.4.1: Server Connection Closed! / Server failed to gather information./cslog
On 03/12/2010 09:40 AM, Utkarsh Ayachit wrote: Is it possible to attach a debugger to the server processes and see where it crashes? On Fri, Mar 12, 2010 at 7:03 AM, SCHROEDER, Martin martin.schroe...@mtu.de wrote: Hello when I'm trying to run paraview (pvserver) on a single host using mpirun with 4 -8 processes, it works. The problem is : when i'm trying to spread pvserver over multiple hosts, using mpirun and a hostfile, the server processes and the client crash when I connect the client to the server. If you have more than one processor core per node, and the problem only occurs when you use more than one process per node, then try adding -mca btl_sm_num_fifos 16 to your mpirun/mpiexec/orterun command line. Replace 16 with a number grater than or equal to twice the number of processes per node. Open MPI has this bug with certain compilers : https://svn.open-mpi.org/trac/ompi/ticket/2043 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
Re: [Paraview] Paraview 3.6.2 / Open MPI 1.4.1: Server Connection Closed! / Server failed to gather information./cslog
On 03/15/2010 12:48 PM, SCHROEDER, Martin wrote: Thanks a lot, You are welcome. I've tried this option, but it seems that this wasn't the source of the problem. Dang. Are there any more parameters that influence the behaviour of resetting a connection ? I do not know. 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
Re: [Paraview] How to install PV 3.6.2 on Red Hat Enterprise?
On 02/03/2010 10:44 AM, bassaidai wrote:
Hi,
can someone tell me the rpm packages list (mpi, python, ...) to install
ParaView 3.6.2 on Red Hat Enterprise?
Thank you very much
Luis
I can not answer specifically for Red Hat Enterprise but as it shares a
lot with Fedora I'm going to answer for Fedora 11 using :
$ yum deplist paraview | grep provider: | awk '{print $2}' | sort |
sort -u
bash.x86_64
desktop-file-utils.x86_64
expat.x86_64
fontconfig.x86_64
freetype-freeworld.x86_64
freetype.x86_64
glibc.i586
glibc.i686
glibc.x86_64
hdf5.x86_64
libgcc.x86_64
libICE.x86_64
libjpeg.x86_64
libpng.x86_64
libSM.x86_64
libstdc++.x86_64
libtiff.x86_64
libX11.x86_64
libXcursor.x86_64
libXext.x86_64
libXfixes.x86_64
libXinerama.x86_64
libXi.x86_64
libXrandr.x86_64
libXrender.x86_64
libXt.x86_64
mesa-libGL.x86_64
mesa-libOSMesa.x86_64
openssl.x86_64
paraview-data.noarch
paraview-doc.noarch
paraview-mpi.x86_64
paraview.x86_64
python-libs.x86_64
qt-x11.i586
qt-x11.x86_64
qt.x86_64
readline.x86_64
zlib.x86_64
$ yum deplist paraview-mpi | grep provider: | awk '{print $2}' | sort
| sort -u
desktop-file-utils.x86_64
expat.x86_64
fontconfig.x86_64
freetype-freeworld.x86_64
freetype.x86_64
glibc.i586
glibc.i686
glibc.x86_64
hdf5.x86_64
lam-libs.x86_64
libgcc.x86_64
libICE.x86_64
libjpeg.x86_64
libpng.x86_64
libSM.x86_64
libstdc++.x86_64
libtiff.x86_64
libX11.x86_64
libXcursor.x86_64
libXext.x86_64
libXfixes.x86_64
libXinerama.x86_64
libXi.x86_64
libXrandr.x86_64
libXrender.x86_64
libXt.x86_64
mesa-libGLU.x86_64
mesa-libGL.x86_64
mesa-libOSMesa.x86_64
openmpi.i586
openmpi-libs.x86_64
openmpi.x86_64
openssl.x86_64
paraview-data.noarch
paraview-mpi.x86_64
paraview.x86_64
python-libs.x86_64
qt-x11.x86_64
qt.x86_64
readline.x86_64
zlib.x86_64
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
Re: [Paraview] screenshot artifacts
On 01/31/2010 02:14 PM, David Doria wrote: Sometimes when I use Save Screenshot, there are lines in the image. You can see here: http://rpi.edu/~doriad/Paraview_List/combined.jpg that there is a vertical and a horizontal line. Is this rendered as multiple images and there is a problem with stitching it into a single image? Thanks, David These have been discussed before, and I believe there was at least a partial solution proposed. As I recall, there are two related issues, volume rendering in parallel, and when saving a screen shot that is larger than the regular render window. In both cases empty lines appear at the edges of the sub-volume that was volume rendered as part of the larger image. When I get to the lab today I'll search my e-mail archive for these threads... Pester me if I don't get back to you. 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
Re: [Paraview] screenshot artifacts
On 01/31/2010 02:14 PM, David Doria wrote: Sometimes when I use Save Screenshot, there are lines in the image. You can see here: http://rpi.edu/~doriad/Paraview_List/combined.jpg that there is a vertical and a horizontal line. Is this rendered as multiple images and there is a problem with stitching it into a single image? Thanks, David There is this bug : http://www.paraview.org/Bug/view.php?id=7858 This thread : http://www.paraview.org/pipermail/paraview/2008-October/009830.html 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] New Nightly Dashboard Sites
I have added 4 new nightly dashboard submissions from hooperlab the sites are : teddy bunny cherry lance These nightly builds could be marked as expected. 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
Re: [Paraview] Possible Bug: cross drawn over upsampled screenshot
On 09/07/2009 05:55 PM, Olumide wrote: 2. Change the representation of the object to wireframe 3. Open the save screenshot dialog (File - Save screenshot), and increase the default width or height of the output image by at least one pixel. Utkarsh talked about this in a recent e-mail. http://www.paraview.org/pipermail/paraview/2009-July/013003.html 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
Re: [Paraview] Suppress X display while saving images from Python script
On Fri, 2009-07-24 at 10:14 +0200, M. Nawijn wrote: Hello, I have Python script that generates PNG images from a Paraview session. This in essence works very well. The one problem that I have is that an OpenGL window is created whenever I save the image. When you do this in a loop, it becomes a little annoying, since the window (at least on my Fedora box) automatically gets focus. Is there a way to generate the PNG images without popping up a window? Yes, there are several. Is it hardware/driver/platform dependent? Yes. I am using Paraview 3.7 (CVS) and Fedora FC11, NVIDIA proprietary drivers. You should be able to : 1) use pvbatch yourscript.py --use-offscreen-rendering Though I just tried this and I still get a window popping up even though I use the mesa driver with osmesa. This may be a bug. 2) Connect to a pvserver --use-offscreen-rendering Though I just tried this and I still get a window popping up even though I use the mesa driver with osmesa. This may be a bug. 3) Use another X server such as Xvfb or vncserver which isn't shown on your display. vncserver :99 -geometry 1280x1024 -depth 24 vncserver.txt 21 pvbatch pvtestscript.py vncserver -kill :99 This works for me. signature.asc Description: This is a digitally signed message part ___ 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: paraview3.6.1/OSMesa rendering issue
On Thu, 2009-08-13 at 08:43 +0100, Lucy Gagliardi wrote: Hi, I’ve recently installed Paraview3.6.1 with OSMesa 7.4.4 on a linux based workstation (64bit). However, when running python scripts to set up and output jpg (or png) files using pvbatch with the --use-offscreen-rendering flag, the scripts run perfectly with no error, however the output picture is garbled. Can you describe exactly how the output is garbled, or post one of the garbled images? Does it look like the red green and blue values are assigned to alternating pixels? Does the same thing happen when you save a screenshot from the paraview gui? signature.asc Description: This is a digitally signed message part ___ 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
On Fri, 2009-07-10 at 16:35 +0200, ibk wrote: Hi, I have seen You have two years ago a problem with reading of csv file. I try to do the same. I have csv with xyz, radius and maybe some values of ceratin property. I would like to show that in paraview, but the csv dont work, I need to know how schould be the cvs file writen. can You help me with file example? Many thanks You will probably get better responses on the list. I am copying the list. ParaView will read a file named data.csv that looks like : 1.1,2.2,3.3 5.5,6.6,7.7 Then you can use the Plot Data filter or the Table to Points filter to display the data. signature.asc Description: This is a digitally signed message part ___ 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] [vtkusers] New QT on Fedora
On Fri, 2009-04-24 at 11:19 -0400, Kevin H. Hobbs wrote: In order to get CTest to configure ParaView with the Qt on Fedora 10 I made some changes to the top level CMakeLists.txt. I tried to repeat the warning for Qt-4.4 nested in with the error I was getting for Qt-4.5. I'm running an experimental build on gargon now. Gargon has been submitting builds with Qt-4.5 from Fedora 10 for several days now. It has rather more test failures than the other builds. There are several errors that look like this: -- client output -- Couldn't find object pqClientMainWindow/lookmarkInspectorDock/1QDockWidgetTitleButton1 Found up to pqClientMainWindow/lookmarkInspectorDock pvTestDriver: client process exited with code 1 signature.asc Description: This is a digitally signed message part ___ 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] [vtkusers] New QT on Fedora
On Fri, 2009-04-24 at 21:20 +1000, Andrew Maclean wrote: I am running QT 4.5 on Windows , both ParaView and VTK compile Ok. The only thing I had to do was to delete the build directory and re-run CMake. Andrew My ctest scripts have # should ctest wipe the binary tree before running SET (CTEST_START_WITH_EMPTY_BINARY_DIRECTORY TRUE) So the build should be starting with empty build directories. signature.asc Description: This is a digitally signed message part ___ 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] [vtkusers] New QT on Fedora
Francois Bertel wrote: Hi Kevin, I don't see the errors you are talking about on the VTK dashboard, I only see them only on the ParaView dashboard. You're absolutely right. The errors are only on the ParaView Dashboard. Apparently I can't baby-wrangle and line up the dashboard columns at the same time. 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] Why is PKdTree used for IMAGE Volume Rendering?
I just tried to use ParaView from Tuesday's CVS (The network was down last night.) on both CPU cores to volume render a large (1/4 the size of available RAM) image. As soon as I selected volume render for the representation I saw the status bar show PKdTree and moments later all of the system memory was consumed and the system started swapping. I had to kill paraview and the pvserver processes from the console to end the swap-death. I reran paraview with only one CPU core and proceeded as normal. My question is: why is PKdTree needed at all for image data? For unstructured data it of course makes sense but for image data it just wastes a lot of RAM. I haven't tried parallel image volume rendering in a while so I don't know when this showed up. signature.asc Description: This is a digitally signed message part ___ 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] Why is PKdTree used for IMAGE Volume Rendering?
On Thu, 2009-02-12 at 14:26 -0500, Utkarsh Ayachit wrote: Do you have any unstructured data being rendering in the scene? No, just one big .vti image. signature.asc Description: This is a digitally signed message part ___ 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] Why is PKdTree used for IMAGE Volume Rendering?
On Thu, 2009-02-12 at 17:27 -0500, Utkarsh Ayachit wrote: Kevin, Attached is a patch. Can you verify that it works after applying the patch? If so, I'll commit it to CVS. Thanks Utkarsh Yup that fixed it. The PKdTree completes immediately and then I get my volume rendering. Thank you! signature.asc Description: This is a digitally signed message part ___ 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] PVPython where is PiecewiseFunction
I'm trying to make a ParaView python script to do some volume rendering. I can load my data, set the representation to volume rendering, and set the color scale the way I want, but I can't figure out how to set the opacity. I found rep.ScalarOpacityFunction, but what do I set it to? I created a simple ParaView session with a volume rendering. Poking around there I found that there is a PiecewiseFunction that I think is created. How do I make a PiecewiseFunction? signature.asc Description: This is a digitally signed message part ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Compiling Paraview
On Sunday 09 November 2008 11:56:42 am Rakesh Hammond wrote: I am at the moment, compiling PV using gcc - in order to link against the PGI compiled MPI library, I need to link a couple of extra libraries, other than libmpich.so Can you please tell me, where and how I need to add these extra libraries into CMakeLists.txt in paraview? You may link as many libraries as you need. You don't need to edit the CMakeList.txt. What you need to do is add the MPI libraries while you are configuring with with ccmake. You'll find only two places to add libraries I believe they are MPI_LIBRARY and MPI_EXTRA_LIBRARY. If you only want to link two libraries use these. Otherwise you can add as many as you need to either of these variables separated by semicolons. The entries in my CMakeCache.txt look like this : MPI_LIBRARY:FILEPATH=/usr/lib64/openmpi/1.2.4-gcc/libmpi_cxx.so MPI_EXTRA_LIBRARY:STRING=/usr/lib64/openmpi/1.2.4-gcc/libmpi.so;/usr/lib64/openmpi/1.2.4-gcc/libopen-rte.so;/usr/lib64/openmpi/1.2.4-gcc/libopen-pal.so;/usr/lib64/libdl.so;/usr/lib64/libnsl.so;/usr/lib64/libutil.so;/usr/lib64/libm.so;/usr/lib64/libdl.so signature.asc Description: This is a digitally signed message part. ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Empty Lines in Screenshot
On Monday 27 October 2008 11:28:42 am Moreland, Kenneth wrote: That looks like a bug. I submitted a report. http://www.paraview.org/Bug/view.php?id=7858 Thank you, I'll monitor that bug. I think the problem is with the fixed point volume renderer. If your data is small enough, you can work around the problem by converting the data to an unstructured grid That will cause the volume rendering algorithm to switch to projected tetrahedra, which works in this regard. Unfortunately no, the data are too bid too big. signature.asc Description: This is a digitally signed message part. ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Devel CMake does not configure PV on linux
On Mon, 2008-10-20 at 11:40 -0600, [EMAIL PROTECTED] wrote: Its fixed in CVS CMake now. Its a regression that appeared when modifying FindQt4.cmake to support re-finding Qt when changing the qmake pointed to. Clint Thank you! I am now able to build with the development version of cmake. gargon's dashboard should be nearly fine and murron's should be back to its usual mess by morning. signature.asc Description: This is a digitally signed message part ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Mesa tests failing
( Berk, sorry for the dupe' 4096x2048 makes for a big PNG that was too big for the list ) I am continuing a thread from July since I have new information. http://www.paraview.org/pipermail/paraview/2008-July/008707.html The original problem was that the mesa builds of VTK and ParaView on murron.hobbs-hancock can not save the output of render windows to files correctly. In messing around with one of my VTK programs that saves a render window to a PNG file I was able to create correct output. When I tell the vtkWindowToImageFilter to SetInputBufferTypeToRGB the output is incorrect but whel i tell it to SetInputBufferTypeToRGBA the output is what I expect. The source, RGB, and RGBA images are posted at: http://crab-lab.zool.ohiou.edu/kevin/OSMIPVolumeRender.cxx http://crab-lab.zool.ohiou.edu/kevin/out_rgb.png http://crab-lab.zool.ohiou.edu/kevin/out_rgba.png signature.asc Description: This is a digitally signed message part. ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
