[Paraview] Changing array names
I am a very new user of Paraview - and am just learning its capabilities. I am importing a series of CSV files - creating points and Delaunay polygons - and then using the Calculator filter to create vectors to plot with the Glyph tool. But when I use the calculator - one of the "Point Data" fields is not numeric - and when I write my formula (which does not use the non-numeric field) and hit "Apply" - thje Output message says ERROR: In ..\..\..\..\source\VTK\Graphics\vtkArrayCalculator.cxx, line 304 vtkPVArrayCalculator (0B39EAE0): Invalid array name: 'Name' (the name of the non numeric field is "name"). I tried renaming this field in the input file - and this didn't work. So I removed the non-numeric field completely from the input file - and the calculator did work. So, I have the option of editing all of my input files - so they don't have non-numeric fields - or there is some way of getting Paraview to not choke on this field - or I'm missing something obvious right in front of my nose? Any help is appreciated. Thanks. New2PV ___ 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 removing rpath
On 02/24/2012 01:22 PM, Peter Brady wrote: If I set my LD_LIBRARY_PATH to include my 7.5.2 Mesa libraries then offscreen rendering works fine. However, I don't want my system as a whole to use my separate Mesa libraries; only Paraview. Hi Peter, I don't know the rpath settings but I have a couple of easy alternatives if all you want to do is modify ld lib path for PV without affecting other installed apps. What about starting pv with a shell script? eg. #!/bin/bash export LD_LIBRARY_PATH=/path/to/your/osmesa:$LD_LIBRARY_PATH /path/to/your/pvpython $* the modules package is also very useful for changing paths on the fly. Burlen ___ 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 removing rpath
Hello all, I am trying to compile Paraview 3.12 on my x86_64 Fedora 15 workstation. My main interest is in offscreen rendering so I had to build my own Mesa libraries (7.5.2) with OSMesa. The system OSMesa libraries are not set up properly (or the wrong version) and so if I link to them, pvpython segfaults when attempting to do offscreen rendering. If I set my LD_LIBRARY_PATH to include my 7.5.2 Mesa libraries then offscreen rendering works fine. However, I don't want my system as a whole to use my separate Mesa libraries; only Paraview. Normally I would accomplish this using the -rpath option. However during the "make install" process, cmake strips the runtime path from the executables. How do I stop this? In my Cmake file, I have the flag //If set, runtime paths are not added when using shared libraries. CMAKE_SKIP_RPATH:BOOL=NO but this doesn't seem to do the trick. Based on this page http://www.cmake.org/cmake/help/cmake-2-8-docs.html#command:set_target_propertiesit seems there are additional variables I can set INSTALL_RPATH INSTALL_RPATH_USE_LINK_PATH SKIP_BUILD_RPATH BUILD_WITH_INSTALL_RPATH CMAKE_INSTALL_RPATH, CMAKE_INSTALL_RPATH_USE_LINK_ PATH, CMAKE_SKIP_BUILD_RPATH, CMAKE_BUILD_WITH_INSTALL_RPATH, and CMAKE_INSTALL_NAME_DIR As it takes a while to recompile each time I try a different combination of flags, can someone tell me the magic combination of variables which allow me set (and _keep_) my -rpath? Thanks, Peter. -- Peter Brady, Ph.D. Postdoctoral Research Associate Sibley School of Mechanical and Aerospace Engineering Cornell University 191 Grumman Hall Ithaca, NY 14853-7501 peter.br...@cornell.edu ___ 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 removing rpath
Hello all, I am trying to compile Paraview 3.12 on my x86_64 Fedora 15 workstation. My main interest is in offscreen rendering so I had to build my own Mesa libraries (7.5.2) with OSMesa. The system OSMesa libraries are not set up properly (or the wrong version) and so if I link to them, pvpython segfaults when attempting to do offscreen rendering. If I set my LD_LIBRARY_PATH to include my 7.5.2 Mesa libraries then offscreen rendering works fine. However, I don't want my system as a whole to use my separate Mesa libraries; only Paraview. Normally I would accomplish this using the -rpath option. However during the "make install" process, cmake strips the runtime path from the executables. How do I stop this? In my Cmake file, I have the flag //If set, runtime paths are not added when using shared libraries. CMAKE_SKIP_RPATH:BOOL=NO but this doesn't seem to do the trick. Based on this page http://www.cmake.org/cmake/help/cmake-2-8-docs.html#command:set_target_propertiesit seems there are additional variables I can set INSTALL_RPATH INSTALL_RPATH_USE_LINK_PATH SKIP_BUILD_RPATH BUILD_WITH_INSTALL_RPATH CMAKE_INSTALL_RPATH, CMAKE_INSTALL_RPATH_USE_LINK_PATH, CMAKE_SKIP_BUILD_RPATH, CMAKE_BUILD_WITH_INSTALL_RPATH, and CMAKE_INSTALL_NAME_DIR As it takes a while to recompile each time I try a different combination of flags, can someone tell me the magic combination of variables which allow me set (and _keep_) my -rpath? Thanks, Peter. -- Peter Brady, Ph.D. Postdoctoral Research Associate Sibley School of Mechanical and Aerospace Engineering Cornell University 191 Grumman Hall Ithaca, NY 14853-7501 peter.br...@cornell.edu ___ 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] Plotting Distances in Zoomed View
>From your description, I'm not entirely sure what you are intending to do. >What do you mean by "plot the distances"? Do you mean use the ruler filter? At any rate, what you want to do might not be very straightforward. First, there is an intentional disconnect between filter operations and camera view. There is no straightforward way to change the behavior of a filter based on the current camera view. However, it is possible in your Python script to get the current camera, query it, and based off of that change the parameters of the filters. That said, it still might not be straightforward because if your camera is in a perspective projection (the default), then the dimensions of the viewing plane (which I assume is what you mean by x and y axis in your description) is not well established. They change based on how far from the camera you consider the viewing plane to be. If you are viewing something flat at a known distance, then you can figure it out. Also, you could change to parallel projection, although that would remove the foreshortening that gives vital visual cues in the rendering. -Ken From: Alex Evanovic mailto:alex.evano...@googlemail.com>> Date: Thu, 23 Feb 2012 19:11:02 +0100 To: mailto:paraview@paraview.org>> Subject: [EXTERNAL] [Paraview] Plotting Distances in Zoomed View Hi, I am new to paraview python scripting. I wrote a script which can automate visualization of my .vtu file. Additionally, it can zoom into the view (which I need). Now, I need to plot the distances in x-axis & y-axis only for this zoomed part (not the whole domain). For example, if the domain is from -10 to 10, I need to plot the distances only for the -2 to 2 part. Can someone please tell me how to go about this (in a python script)? Thanks & Regards, Alex ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] PV 3.14 Linux crashes when trying to open a file
Utkarsh Ayachit a écrit : Thank you Utkarsh. Removing these libraries makes PV 314 able to open data files or load pvsm states. Please, let me know when the updated binaries will be available and I will make tests. Richard, the new binaries have now been uploaded. Utkarsh Utkarsh Thank you for the new Linux binaries. Now PV 314 can load state files and open data files. Richard. -- Richard GRENON ONERA Departement d'Aerodynamique Appliquee - DAAP/ACI 8 rue des Vertugadins 92190 MEUDON - FRANCE phone : +33 1 46 73 42 17 fax : +33 1 46 73 41 46 mailto:richard.gre...@onera.fr http://www.onera.fr ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] PV 3.14 Linux crashes when trying to open a file
> Thank you Utkarsh. Removing these libraries makes PV 314 able to open data > files or load pvsm states. > Please, let me know when the updated binaries will be available and I will > make tests. Richard, the new binaries have now been uploaded. Utkarsh ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] PV 3.14 Linux crashes when trying to open a file
Thanks Richard, I could reproduce both the issue. I've pushed a fix for the first and I'll track the second one down as well. FYI: http://paraview.org/Bug/view.php?id=12964 Utkarsh ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] PV 3.14 Linux crashes when trying to open a file
Richard, A state file without data would help too. Let's start there and see if we can address the issues. Thanks, Utkarsh On Fri, Feb 24, 2012 at 9:11 AM, Richard GRENON wrote: > Utkarsh Ayachit a écrit : > >>> For me, the state files from PV312 are almost compatible with PV 314: >>> when >>> opening an earlier version state file, PV 314 just proposes to create an >>> additional view that may be canceled and I recover the full saved state. >>> Maybe this is due to the new "Layout" feature ? >>> >> >> >> That shouldn't affect it. I remember ensuring that the layout xmls are >> compatible. >> Can you share a state file to reproduce this issue? I'd like to have >> it addressed. >> >> Utkarsh >> >> >> > > > Utkarsh, the state files that I used cannot be shared because they concern > confidential data and the datasets are heavy. Is the state file alone > without dataset useful for you ? > But I could also try to build a small pvsm test file with test data with PV > 312 and see what happens when reading with PV 314, and I will send it on > next Monday. > > In fact, it's not really important (for me) if PV 314 proposes to create an > additional view as you can cancel it. > > More annoying is another problem that I discovered with one of my PV 312 > pvsm state files with heavy data sets : PV 314 crashed after selecting the > state file while loading the data! I don't know if the crash occurs when PV > 314 is trying to create an additional view. But the state file is for a > complex pipeline that should produce a 3D view from full CFD data with some > surface grids and field cuts in surface mode and some surface grids in > surface LIC mode, and two spreadsheet views that show the data in > SurfaceFlow objects. I discovered that PV 314 could read a modified state > file that was saved by PV 312 after having deleted the two spreadsheet > views, and I could create again these two spreadsheet views within PV 314. > If the full state file without dataset is useful for you I will sent it on > next Monday. > > Best regards. > > > -- > Richard GRENON > ONERA > Departement d'Aerodynamique Appliquee - DAAP/ACI > 8 rue des Vertugadins > 92190 MEUDON - FRANCE > phone : +33 1 46 73 42 17 > fax : +33 1 46 73 41 46 > mailto:richard.gre...@onera.fr > http://www.onera.fr > ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] PV 3.14 Linux crashes when trying to open a file
Utkarsh Ayachit a écrit : For me, the state files from PV312 are almost compatible with PV 314: when opening an earlier version state file, PV 314 just proposes to create an additional view that may be canceled and I recover the full saved state. Maybe this is due to the new "Layout" feature ? That shouldn't affect it. I remember ensuring that the layout xmls are compatible. Can you share a state file to reproduce this issue? I'd like to have it addressed. Utkarsh Utkarsh, the state files that I used cannot be shared because they concern confidential data and the datasets are heavy. Is the state file alone without dataset useful for you ? But I could also try to build a small pvsm test file with test data with PV 312 and see what happens when reading with PV 314, and I will send it on next Monday. In fact, it's not really important (for me) if PV 314 proposes to create an additional view as you can cancel it. More annoying is another problem that I discovered with one of my PV 312 pvsm state files with heavy data sets : PV 314 crashed after selecting the state file while loading the data! I don't know if the crash occurs when PV 314 is trying to create an additional view. But the state file is for a complex pipeline that should produce a 3D view from full CFD data with some surface grids and field cuts in surface mode and some surface grids in surface LIC mode, and two spreadsheet views that show the data in SurfaceFlow objects. I discovered that PV 314 could read a modified state file that was saved by PV 312 after having deleted the two spreadsheet views, and I could create again these two spreadsheet views within PV 314. If the full state file without dataset is useful for you I will sent it on next Monday. Best regards. -- Richard GRENON ONERA Departement d'Aerodynamique Appliquee - DAAP/ACI 8 rue des Vertugadins 92190 MEUDON - FRANCE phone : +33 1 46 73 42 17 fax : +33 1 46 73 41 46 mailto:richard.gre...@onera.fr http://www.onera.fr ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Compiling Plugins for the Binary Release
I think I know the problem. Qt was built with libpng 1.2 and ParaView superbuild is building paraview with libpng 1.5 and hence the issue. You'lll have to build Qt telling it to link against libpng1.5. The new superbuild I used for ParaView 3.14 takes care of that, but I'm not sure it'll work out of the box for 3.12. You might be better off just building Qt with libpng 1.5. Also try running "readelf -d " on all shared libraries in your plugin. That should at the least tell you which "so" is bringing in a libpng. If none of your "so"s refer to libpng directly, I'd think that should work just fine. Utkarsh On Fri, Feb 24, 2012 at 8:48 AM, Oliver Behm wrote: > I have attached the CMakeCache.txt. I am using the SuperBuild > directory of the ParaView 3.12 source release from the ParaView > website, since we are still using version 3.12. > > I will try the new version though, if I can make that work that > will probably suffice. > > Thanks for the RPATH hint, that is actually quite helpful. > > Regards > Oliver > > On 02/24/2012 02:30 PM, Utkarsh Ayachit wrote: >> Can you post the CMakeCache.txt file you're using for building the >> plugin? For linux which super build did you use? The linux binaries >> were built using the following repo (checkout tag v3.14.0) : >> >> https://gitorious.org/paraview-collaboration/paraview-binaries-superbuild >> >> To influence the search path, you can use INSTALL_RPATH >> (http://www.cmake.org/cmake/help/cmake-2-8-docs.html#command:set_target_properties), >> however that's still won't help unless you know exactly where your >> users are going to install ParaView. Users either have to set >> LD_LIBRARY PATH, or simply put all the .so files under >> <..>/lib/paraview3.14/ directory. >> >> Utkarsh >> >> On Fri, Feb 24, 2012 at 6:50 AM, Oliver Behm >> wrote: >>> Hello, >>> >>> I am currently trying to compile a rather simple reader plugin so that >>> it works with the binary release (Linux, 64 Bit, 3.12). >>> >>> To this end I compiled the paraview sources with the SuperBuild function, >>> which seams to have worked just fine. But when I compile any plugins >>> using this build the resulting library is linked against libpng 1.5 from the >>> SuperBuild folder as well as libpng 1.2 from the system paths. >>> >>> Since we don't have libpng 1.5 installed globally it would be very nice >>> if I could prevent the plugin from linking it? Is that possible? >>> >>> I don't really see how this library can be necessary since the binary >>> distribution of paraview does not require it either and I certainly don't >>> do anything with my reader that the standard readers don't do too. >>> >>> Aside from that is there anyway I can easily influence the search paths >>> that are compiled into the library? I'd like to set them to the location >>> of that libraries that ship with the binary distribution instead of my >>> local SuperBuild. >>> >>> Best regards >>> Oliver Behm >>> ___ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://www.paraview.org/mailman/listinfo/paraview > ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] mpirun ./pvserver
To speed up Qt compilation, compile without example and demos and remember to use the j switch with the number of cores you want to build with. On Fri, Feb 24, 2012 at 5:12 AM, Kaster Might wrote: > Oh my freaking god :) > After 3 hours of building Qt from sources and then 1 hour for Paraview I > finally got pvserver to work. My longest linux software installation > challenge so far :) > > My only concern is each pvserver consumes 100% of CPU when no clients > connected and it's idle. Is it normal? Unfortunately that's not what I > expected. > > -- > Kaster Might > > On Feb 23, 2012, at 1:19 PM, Utkarsh Ayachit wrote: > > Your Qt is not built with WebKit. Did you build Qt from source as well? > > Utkarsh > > On Thu, Feb 23, 2012 at 3:13 PM, Kaster Might > wrote: > > OK, new version didn't help. So I tried to compile from source, again. > After spending another 3 hrs I got this error. I thing that's the error I > got last time. > > > ---code start--- > > > Building CXX object Qt/Widgets/CMakeFiles/pqWidgets.dir/pqHelpWindow.cxx.o > > ~/ParaView-3.14.0-Source/Qt/Widgets/pqHelpWindow.cxx(50): catastrophic > error: cannot open source file "QWebPage" > > #include > > ^ > > > compilation aborted for > /home/kaster/Downloads/ParaView-3.14.0-Source/Qt/Widgets/pqHelpWindow.cxx > (code 4) > > gmake[2]: *** [Qt/Widgets/CMakeFiles/pqWidgets.dir/pqHelpWindow.cxx.o] > Error 4 > > gmake[1]: *** [Qt/Widgets/CMakeFiles/pqWidgets.dir/all] Error 2 > > gmake: *** [all] Error 2 > > > ---code end --- > > > How can I get that header file, or whatever is. > > > Thanks. > > > -- > > Kaster Might > > > On Feb 22, 2012, at 12:27 PM, Utkarsh Ayachit wrote: > > > There are on http://www.paraview.org/paraview/resources/software.php, > > however you have to use mpiexec provided by the package. > > > Utkarsh > > > On Wed, Feb 22, 2012 at 1:53 PM, Kaster Might > wrote: > > Actually, I didn't build anything, because when I tried it took 3 hours and > > threw some error on 89%, so I just gave up and downloaded ready-to-go > > version. I believe that's the reason then. Is there any MPI enabled > > precompiled distro for linux? > > > Thanks. > > > -- > > Kaster Might > > > On Feb 22, 2012, at 7:03 AM, Utkarsh Ayachit wrote: > > > Verify that the paraview is built with mpi enabled (PARAVIEW_USE_MPI > > cmake flag must be ON). In most likelihood, it's not. > > > Utkarsh > > > On Wed, Feb 22, 2012 at 2:45 AM, Kaster Might > wrote: > > > Hi all, > > > > I have issues with running parallel pvserver on linux machine. When I try > > this `mpirun -np 3 ./pvserver` I get error `vtkServerSocket (0xe09640): > > Socket error in call to bind. Address already in use.` for every process > but > > first. I believe it's because each of `pvserver` processes tries to listen > > the same 1 port at the same time, but I couldn't find how to specify > > different ports depending on -np parameter for mpirun. Any help or advice > is > > appreciated. > > > > Thanks. > > > > -- > > > Kaster Might > > > ___ > > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > > http://www.paraview.org/mailman/listinfo/paraview > > > > > > > > ___ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview > > -- Robert Maynard ___ 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] Compiling Plugins for the Binary Release
I have attached the CMakeCache.txt. I am using the SuperBuild directory of the ParaView 3.12 source release from the ParaView website, since we are still using version 3.12. I will try the new version though, if I can make that work that will probably suffice. Thanks for the RPATH hint, that is actually quite helpful. Regards Oliver On 02/24/2012 02:30 PM, Utkarsh Ayachit wrote: > Can you post the CMakeCache.txt file you're using for building the > plugin? For linux which super build did you use? The linux binaries > were built using the following repo (checkout tag v3.14.0) : > > https://gitorious.org/paraview-collaboration/paraview-binaries-superbuild > > To influence the search path, you can use INSTALL_RPATH > (http://www.cmake.org/cmake/help/cmake-2-8-docs.html#command:set_target_properties), > however that's still won't help unless you know exactly where your > users are going to install ParaView. Users either have to set > LD_LIBRARY PATH, or simply put all the .so files under > <..>/lib/paraview3.14/ directory. > > Utkarsh > > On Fri, Feb 24, 2012 at 6:50 AM, Oliver Behm > wrote: >> Hello, >> >> I am currently trying to compile a rather simple reader plugin so that >> it works with the binary release (Linux, 64 Bit, 3.12). >> >> To this end I compiled the paraview sources with the SuperBuild function, >> which seams to have worked just fine. But when I compile any plugins >> using this build the resulting library is linked against libpng 1.5 from the >> SuperBuild folder as well as libpng 1.2 from the system paths. >> >> Since we don't have libpng 1.5 installed globally it would be very nice >> if I could prevent the plugin from linking it? Is that possible? >> >> I don't really see how this library can be necessary since the binary >> distribution of paraview does not require it either and I certainly don't >> do anything with my reader that the standard readers don't do too. >> >> Aside from that is there anyway I can easily influence the search paths >> that are compiled into the library? I'd like to set them to the location >> of that libraries that ship with the binary distribution instead of my >> local SuperBuild. >> >> Best regards >> Oliver Behm >> ___ >> 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 # This is the CMakeCache file. # For build in directory: /home/behm/stroemung/BinaryReader/build # It was generated by CMake: /usr/bin/cmake # You can edit this file to change values found and used by cmake. # If you do not want to change any of the values, simply exit the editor. # If you do want to change a value, simply edit, save, and exit the editor. # The syntax for the file is as follows: # KEY:TYPE=VALUE # KEY is the name of a variable in the cache. # TYPE is a hint to GUI's for the type of VALUE, DO NOT EDIT TYPE!. # VALUE is the current value for the KEY. # EXTERNAL cache entries //Path to a program. CMAKE_AR:FILEPATH=/usr/bin/ar //Choose the type of build, options are: None(CMAKE_CXX_FLAGS or // CMAKE_C_FLAGS used) Debug Release RelWithDebInfo MinSizeRel. CMAKE_BUILD_TYPE:STRING= //Enable/Disable color output during build. CMAKE_COLOR_MAKEFILE:BOOL=ON //CXX compiler. CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++ //Flags used by the compiler during all build types. CMAKE_CXX_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_CXX_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release minsize builds. CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds (/MD /Ob1 /Oi // /Ot /Oy /Gs will produce slightly less optimized but smaller // files). CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during Release with Debug Info builds. CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g //C compiler. CMAKE_C_COMPILER:FILEPATH=/usr/bin/gcc //Flags used by the compiler during all build types. CMAKE_C_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_C_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release minsize builds. CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds (/MD /Ob1 /Oi // /Ot /Oy /Gs will produce slightly less optimized but smaller // files). CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during Release with Debug Info builds. CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g //Flags used by the linker. CMAKE_EXE_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_EXE_LINKER_FLAGS_MIN
Re: [Paraview] PV 3.14 Linux crashes when trying to open a file
> For me, the state files from PV312 are almost compatible with PV 314: when > opening an earlier version state file, PV 314 just proposes to create an > additional view that may be canceled and I recover the full saved state. > Maybe this is due to the new "Layout" feature ? That shouldn't affect it. I remember ensuring that the layout xmls are compatible. Can you share a state file to reproduce this issue? I'd like to have it addressed. Utkarsh ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Compiling Plugins for the Binary Release
Can you post the CMakeCache.txt file you're using for building the plugin? For linux which super build did you use? The linux binaries were built using the following repo (checkout tag v3.14.0) : https://gitorious.org/paraview-collaboration/paraview-binaries-superbuild To influence the search path, you can use INSTALL_RPATH (http://www.cmake.org/cmake/help/cmake-2-8-docs.html#command:set_target_properties), however that's still won't help unless you know exactly where your users are going to install ParaView. Users either have to set LD_LIBRARY PATH, or simply put all the .so files under <..>/lib/paraview3.14/ directory. Utkarsh On Fri, Feb 24, 2012 at 6:50 AM, Oliver Behm wrote: > Hello, > > I am currently trying to compile a rather simple reader plugin so that > it works with the binary release (Linux, 64 Bit, 3.12). > > To this end I compiled the paraview sources with the SuperBuild function, > which seams to have worked just fine. But when I compile any plugins > using this build the resulting library is linked against libpng 1.5 from the > SuperBuild folder as well as libpng 1.2 from the system paths. > > Since we don't have libpng 1.5 installed globally it would be very nice > if I could prevent the plugin from linking it? Is that possible? > > I don't really see how this library can be necessary since the binary > distribution of paraview does not require it either and I certainly don't > do anything with my reader that the standard readers don't do too. > > Aside from that is there anyway I can easily influence the search paths > that are compiled into the library? I'd like to set them to the location > of that libraries that ship with the binary distribution instead of my > local SuperBuild. > > Best regards > Oliver Behm > ___ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Compiling Plugins for the Binary Release
Hello, I am currently trying to compile a rather simple reader plugin so that it works with the binary release (Linux, 64 Bit, 3.12). To this end I compiled the paraview sources with the SuperBuild function, which seams to have worked just fine. But when I compile any plugins using this build the resulting library is linked against libpng 1.5 from the SuperBuild folder as well as libpng 1.2 from the system paths. Since we don't have libpng 1.5 installed globally it would be very nice if I could prevent the plugin from linking it? Is that possible? I don't really see how this library can be necessary since the binary distribution of paraview does not require it either and I certainly don't do anything with my reader that the standard readers don't do too. Aside from that is there anyway I can easily influence the search paths that are compiled into the library? I'd like to set them to the location of that libraries that ship with the binary distribution instead of my local SuperBuild. Best regards Oliver Behm ___ 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] mpirun ./pvserver
Oh my freaking god :) After 3 hours of building Qt from sources and then 1 hour for Paraview I finally got pvserver to work. My longest linux software installation challenge so far :) My only concern is each pvserver consumes 100% of CPU when no clients connected and it's idle. Is it normal? Unfortunately that's not what I expected. -- Kaster Might On Feb 23, 2012, at 1:19 PM, Utkarsh Ayachit wrote: > Your Qt is not built with WebKit. Did you build Qt from source as well? > > Utkarsh > > On Thu, Feb 23, 2012 at 3:13 PM, Kaster Might wrote: >> OK, new version didn't help. So I tried to compile from source, again. After >> spending another 3 hrs I got this error. I thing that's the error I got last >> time. >> >> ---code start--- >> >> Building CXX object Qt/Widgets/CMakeFiles/pqWidgets.dir/pqHelpWindow.cxx.o >> ~/ParaView-3.14.0-Source/Qt/Widgets/pqHelpWindow.cxx(50): catastrophic >> error: cannot open source file "QWebPage" >> #include >> ^ >> >> compilation aborted for >> /home/kaster/Downloads/ParaView-3.14.0-Source/Qt/Widgets/pqHelpWindow.cxx >> (code 4) >> gmake[2]: *** [Qt/Widgets/CMakeFiles/pqWidgets.dir/pqHelpWindow.cxx.o] Error >> 4 >> gmake[1]: *** [Qt/Widgets/CMakeFiles/pqWidgets.dir/all] Error 2 >> gmake: *** [all] Error 2 >> >> ---code end --- >> >> How can I get that header file, or whatever is. >> >> Thanks. >> >> -- >> Kaster Might >> >> On Feb 22, 2012, at 12:27 PM, Utkarsh Ayachit wrote: >> >>> There are on http://www.paraview.org/paraview/resources/software.php, >>> however you have to use mpiexec provided by the package. >>> >>> Utkarsh >>> >>> On Wed, Feb 22, 2012 at 1:53 PM, Kaster Might wrote: Actually, I didn't build anything, because when I tried it took 3 hours and threw some error on 89%, so I just gave up and downloaded ready-to-go version. I believe that's the reason then. Is there any MPI enabled precompiled distro for linux? Thanks. -- Kaster Might On Feb 22, 2012, at 7:03 AM, Utkarsh Ayachit wrote: Verify that the paraview is built with mpi enabled (PARAVIEW_USE_MPI cmake flag must be ON). In most likelihood, it's not. Utkarsh On Wed, Feb 22, 2012 at 2:45 AM, Kaster Might wrote: Hi all, I have issues with running parallel pvserver on linux machine. When I try this `mpirun -np 3 ./pvserver` I get error `vtkServerSocket (0xe09640): Socket error in call to bind. Address already in use.` for every process but first. I believe it's because each of `pvserver` processes tries to listen the same 1 port at the same time, but I couldn't find how to specify different ports depending on -np parameter for mpirun. Any help or advice is appreciated. Thanks. -- Kaster Might ___ 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 >> smime.p7s Description: S/MIME cryptographic signature ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] PV 3.14 Linux crashes when trying to open a file
Paul McIntosh a écrit : My 2 cents (sorry for butting in without actually reading the full thread) - I have noticed that states from earlier version of PV are not compatible with 3.14 for some reason. If you resave the state then it works. Hello. For me, the state files from PV312 are almost compatible with PV 314: when opening an earlier version state file, PV 314 just proposes to create an additional view that may be canceled and I recover the full saved state. Maybe this is due to the new "Layout" feature ? -- Richard GRENON ONERA Departement d'Aerodynamique Appliquee - DAAP/ACI 8 rue des Vertugadins 92190 MEUDON - FRANCE phone : +33 1 46 73 42 17 fax : +33 1 46 73 41 46 mailto:richard.gre...@onera.fr http://www.onera.fr ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] PV 3.14 Linux crashes when trying to open a file
Utkarsh Ayachit a écrit : The offending line is: find library=libQtSvg.so.4 [0]; searching 7785: trying file=/usr/lib64/qt4/lib64/libQtSvg.so.4 Try the following. If that works, I'll update the binaries: Remove files ./lib/paraview-3.14/iconengines/libqsvgicon.so and ./lib/paraview-3.14/imageformats/libqsvg.so and try again. Utkarsh Thank you Utkarsh. Removing these libraries makes PV 314 able to open data files or load pvsm states. Please, let me know when the updated binaries will be available and I will make tests. Best regards. -- Richard GRENON ONERA Departement d'Aerodynamique Appliquee - DAAP/ACI 8 rue des Vertugadins 92190 MEUDON - FRANCE phone : +33 1 46 73 42 17 fax : +33 1 46 73 41 46 mailto:richard.gre...@onera.fr http://www.onera.fr ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
