[Paraview] [Blog] Why is ParaView using all that memory?

Hi, I've written up a blog post on ParaView and memory usage[1]. If there are any questions or things that need clarifications, feel free to let me know. --Ben [1]http://www.kitware.com/blog/home/post/631 ___ Powered by www.kitware.com Visit other

Re: [Paraview] PV 4.1.0 ParaView-4.1.0-Linux-64bit/bin/paraview: cannot execute binary file

On Sat, Mar 08, 2014 at 16:07:58 +0100, Stephen Wornom wrote: I have ubuntu as the operating system ParaView-4.1.0-Linux-64bit/bin/paraview: cannot execute binary file ls -al /home/stephen/ParaView-4.1.0-Linux-64bit/bin/paraview -rwxr-xr-x 1 stephen stephen 79439 Jan 13 06:48

Re: [Paraview] PV 4.1.0 ParaView-4.1.0-Linux-64bit/bin/paraview: cannot execute binary file

On Sun, Mar 09, 2014 at 12:20:45 +0100, Stephen Wornom wrote: From: Ben Boeckel ben.boec...@kitware.com Is the filesystem mounted noexec? Not to my knowledge, how would I check? The output of 'mount' will show the flags for mounted filesystems. --Ben

Re: [Paraview] missing python filters from python Shell

On Wed, Mar 19, 2014 at 16:55:21 -0400, David E DeMarle wrote: Try this technique from Pat Marion. http://markmail.org/message/4kp7cxl2ani25cak It should give you access to most or all of VTK, not just the subset the ParaView exposes. For those who would like to avoid 'exec', here's the

Re: [Paraview] ParaView Digest, Vol 120, Issue 35

On Tue, Apr 22, 2014 at 11:05:24 -0600, Jack Vant wrote: /usr/bin/ld: /cm/shared/apps/mvapich2/gcc/64/1.9/lib/libmpich.a(setbotf.o): relocation R_X86_64_32 against `mpifcmb2_' can not be used when making a shared object; recompile with -fPIC ^

Re: [Paraview] ParaviewWeb Multiuser

On Mon, May 19, 2014 at 16:03:49 +0200, Daniel Zuidinga wrote: 'secret': 'katglrt54#%dfg', 'user': 'sebastien.jourdain', 'password': 'ousdfbdxldfgh', Hmm...might want to change these if they're real? --Ben ___ Powered by www.kitware.com Visit other

Re: [Paraview] Linking Catalyst example samples with Catalyst

On Fri, Jun 06, 2014 at 02:18:42 -0700, Praveen Narayanan wrote: I am examining the example code for catalyst from Andy Bauer’s git repository (https://github.com/acbauer/CatalystExampleCode). I am trying to learn about the catalyst workflow before using it in my own in situ examples.

Re: [Paraview] dlclose assertion error with boost::regex

On Fri, Jun 20, 2014 at 21:27:01 -0600, Andrew Ho wrote: The one thing I can do to get this message to go away is to change the target_link_libraries to INTERFACE, but then the code will crash on trying to run RequestData because it can't find the symbols. This tells CMake that anything that

Re: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON

On Tue, Sep 16, 2014 at 16:22:38 +, Su, Simon M CTR USARMY ARL (US) wrote: I would like to test out the xdmf3 writer in ParaView 4.2 RC to see if the file size is still increase 10 fold when saving pvd file to xmf format. However, when I configure ParaView v4.2.0-RC1-75-gf64ee7a with

Re: [Paraview] Failure plotting cell labels

On Sun, Sep 28, 2014 at 09:18:52 -0400, Bill Greene wrote: I'm trying to plot Cell labels in Paraview 4.1.0 by defining a string array of cell data. However, I get an error in Find Data dialog when I try to select the cells. This very simple vtu file demonstrates the problem.

Re: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED)

On Tue, Sep 30, 2014 at 14:18:19 +, Su, Simon M CTR USARMY ARL (US) wrote: Any help is much appreciated. I added the appdata stuff; looking into it. --Ben ___ Powered by www.kitware.com Visit other Kitware open-source projects at

Re: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED)

On Tue, Sep 30, 2014 at 11:03:56 -0400, Ben Boeckel wrote: On Tue, Sep 30, 2014 at 14:18:19 +, Su, Simon M CTR USARMY ARL (US) wrote: Any help is much appreciated. I added the appdata stuff; looking into it. Seems that the fact that ParaView's superbuild only builds the paraview

Re: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED)

On Tue, Sep 30, 2014 at 19:36:13 +, Su, Simon M CTR USARMY ARL (US) wrote: can I safely ignore the error? Can we assume the binary installation is complete? or are there additional installation steps after appdata step that is needed for a proper ParaView binary installation? If so, how do

Re: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED)

On Wed, Oct 01, 2014 at 17:15:34 +, Su, Simon M CTR USARMY ARL (US) wrote: I think your patch worked. Cmake not complaining all the way to the end. The patch has been merged into master now. --Ben ___ Powered by www.kitware.com Visit other

Re: [Paraview] ParaView Superbuild - changing default Paraciew cmake option

On Fri, Oct 17, 2014 at 15:18:00 +, Su, Simon M CTR USARMY ARL (US) wrote: CMake Warning: Manually-specified variables were not used by the project: Boost_NO_BOOST_CMAKE Module_vtkIOXdmf3 How do I go around that? The options need to be passed to the ParaView build itself,

Re: [Paraview] ParaView Superbuild - changing default Paraciew cmake option

On Fri, Oct 17, 2014 at 17:41:58 +, Su, Simon M CTR USARMY ARL (US) wrote: When I do both argument in the same -DPV_EXTRA_CMAKE_ARGS, cmake also didn't like it. -DPV_EXTRA_CMAKE_ARGS=-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON I am getting CMake Warning:

Re: [Paraview] ParaView Superbuild - changing default Paraciew cmake option

On Mon, Oct 20, 2014 at 15:15:59 +, Su, Simon M CTR USARMY ARL (US) wrote: I ran cmake with -DPV_EXTRA_CMAKE_ARGS:STRING=-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON and check it with ccmake. Looks like -DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON made it

[Paraview] [ANN] New 4.2.0 Release Binary for OS X 10.6 (Snow Leopard)

Hi all, We've tracked down the error with the Snow Leopard builds of ParaView 4.2.0 and new binaries have been uploaded to the website available through the normal download page. To ensure you have the new binary, the md5sum of the new dmg file is: b1289277d12563321212ed83b70c2f20 The

Re: [Paraview] ParaView Superbuild - changing default Paraciew cmake option

On Mon, Oct 20, 2014 at 15:57:26 +, Su, Simon M CTR USARMY ARL (US) wrote: Unfortunately, when I checked the CMakeCache.txt in the directory paraview/src/paraview-build after the cmake ran, I am still finding Sorry, this email went under my radar. //Request building vtkIOXdmf3

Re: [Paraview] 550 Neither MX nor MTA found for domain:paraview.org

On Wed, Oct 29, 2014 at 12:36:35 +, Anton Shterenlikht wrote: Delivery to the following recipient failed permanently: paraview@paraview.org Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the relay outbounds200.obsmtp.com by ou

Re: [Paraview] Compile error: unknown type name ‘sigjmp_buf’

On Wed, Feb 18, 2015 at 12:52:30 -0500, John Moore wrote: H5JMP_BUF is not found in CMakeCache.txt, but H5_HAVE_SETJMP_H is, as shown below: Ah, I see that H5JMP_BUF is defined at the top of the file, not by CMake and is controlled by H5_HAVE_SIGSETJMP (empty on my Fedora install) or

Re: [Paraview] Compile error: unknown type name ‘sigjmp_buf’

On Tue, Feb 17, 2015 at 15:14:13 -0500, John Moore wrote: I get the following error when compiling on Ubuntu 14.04 /home/john/local/ParaView/4.3.1/ParaView-v4.3.1-source/VTK/ThirdParty/hdf5/vtkhdf5/src/H5detect.c:149:1: error: unknown type name ‘sigjmp_buf’ static H5JMP_BUF jbuf_g; I've

Re: [Paraview] [Paraview-developers] Super build Problem

On Wed, Jan 28, 2015 at 13:01:30 -0700, Joshua Murphy wrote: I have posted this question once before, but everyone was probably busy with the 4.3.1 release… So here goes again. I am trying to build the superbuild on the NCAR visualization cluster Caldera for development work. I need to

Re: [Paraview] problem building ParaView Examples

On Mon, Jan 12, 2015 at 10:47:16 -0800, Jeff Becker wrote: Yes. I turned that off, and now it builds fine. Thanks. I'm tracking this part of it down; do you still have the CMakeCache.txt related to this failure? If the current build is the same one as here with just PARAVIEW_USE_UNIFIED_BINDINGS

Re: [Paraview] CPack issue with hdf5/libhdf5.settings

On Tue, Feb 10, 2015 at 13:10:01 +0100, Christoph Grüninger wrote: How are you building the packages? with openSuse's buildservice. I branched the official ParaView package which is still ParaView 4.2 and tried to update it. After I replaced the sources and adjusted the spec file, I got the

Re: [Paraview] CPack issue with hdf5/libhdf5.settings

On Thu, Feb 12, 2015 at 06:45:47 +0100, Christoph Grüninger wrote: let me rephrase my question: Is it save to add /usr/share/cmake/hdf5/ within the ParaView package? Or would it affect a HDF5 package? It would likely conflict with a native HDF5 package. Is there a reason the system HDF5 isn't

Re: [Paraview] EnSightReader: Change input file

On Sat, Dec 20, 2014 at 10:09:46 +0100, Ian Krukow wrote: Then I switched to my desktop PC with Windows 7, where I set up the building process. When I run the configuration in CMake, as soon as I enable python, I get the error CMake Error at VTK/CMake/ExternalData.cmake:176 (add_test):

Re: [Paraview] Load text file delimited by tab

On Tue, Nov 11, 2014 at 13:19:42 -0500, Utkarsh Ayachit wrote: Interesting! Alas, no, there isn't a direct way for setting this in the UI, currently. A tab could be pasted into the field, I imagine (works here in other fields). --Ben ___ Powered by

Re: [Paraview] Superbuild and code changes

On Fri, Mar 13, 2015 at 02:55:09 +, Scott, W Alan wrote: Is it possible to build ParaView with the superbuild, but change a few lines of code? I want to comment out a few warnings. These lines of source code keep getting written over. You could apply a patch[1] (using an ExternalData

Re: [Paraview] Superbuild and code changes

On Thu, Mar 12, 2015 at 23:18:54 -0400, Ben Boeckel wrote: Without looking, I can't remember the exact names of the cache variables, but they're something like paraview_GIT_URL and paraview_GIT_HASH. They are PARAVIEW_GIT_REPOSITORY and PARAVIEW_GIT_TAG (which is any git refname, not just

Re: [Paraview] [import error] Paraview Python on Windows

[ Adding the list back to CC. ] On Fri, May 01, 2015 at 15:55:26 +0200, Jonas Asche wrote: Thank you for the reply, Are you only using P:\ParaView 4.2.0\bin or do you link to other folders as well? I ran with the following from Git bash (so that the environment was more easily modified). All

Re: [Paraview] [import error] Paraview Python on Windows

On Fri, May 01, 2015 at 14:32:40 +0200, Jonas Asche wrote: Now i want to use those scripts on Windows 7 64bit. I downloaded ParaView-4.2.0-Windows-64bit and changed PythonPath and Path variable as described in this http://www.paraview.org/Wiki/ParaView/Python_Scriptingarticle: Are you running

Re: [Paraview] vtk_use_system_protobuf

On Thu, Apr 09, 2015 at 09:40:16 -0400, Ben Boeckel wrote: Doesn't seem so. Looks like ParaView will need changes for 2.6.0. Searching around, seems like the changes necessary for it are probably minor[1]. An attempt at this: https://gitlab.kitware.com/paraview/paraview/merge_requests/52

Re: [Paraview] vtk_use_system_protobuf

On Wed, Apr 08, 2015 at 19:36:28 -0700, Kevin Dean wrote: vtkPVMessage.proto:65:14: Message extensions cannot have required fields. vtkPVMessage.proto:68:14: Message extensions cannot have required fields. vtkPVMessage.proto:103:14: Message extensions cannot have required fields.

Re: [Paraview] Error building superbuild VS2010

On Fri, Jul 31, 2015 at 16:34:49 +, Bruce Jones wrote: I am trying to build the superbuild for x64 on windows. I have configured everything with cmake (i have only selected ENABLE_paraview and ENABLE_qt) and am trying to do a release build. The build fails with, 7 CMake Error at

Re: [Paraview] Error building superbuild VS2010

On Tue, Aug 04, 2015 at 00:55:16 +, Bruce Jones wrote: I followed your instructions and the build was successful in release mode. However, when I run the executable it crashes on load. Attempting to debug this I tried to build in debug mode using the same approach. Unfortunately the

Re: [Paraview] Qt

On Sat, Jul 11, 2015 at 00:16:19 +, Scott, W Alan wrote: I notice that the Superbuild is running Qt 5.4.1. Any idea where I can find the Windows installer (i.e., I don't want to build from source)? Also, Qt5 is currently experimental in that it is known that there are issues with it in

Re: [Paraview] Qt

On Sat, Jul 11, 2015 at 00:16:19 +, Scott, W Alan wrote: I notice that the Superbuild is running Qt 5.4.1. Any idea where I can find the Windows installer (i.e., I don't want to build from source)? Downloads are found here: http://download.qt.io/archive/qt/5.4/5.4.1/ The superbuild

[Paraview] ANN: ParaView 5.0.0-RC1 is available for download

Folks, ParaView 5.0.0-RC1 is now available for download. Checkout the release notes on the Kitware blog [1]. As always, we look forward to your feedback [2]. Also stay tuned to the Kitware Blog [3] for upcoming features and enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much more!

Re: [Paraview] Paraview 4.4.0 build error with osmesa on RHEL cluster at LLNL

On Fri, Oct 30, 2015 at 18:22:01 +, Cook, Rich wrote: > I'm seeing an error when trying to build the latest Paraview using > osmesa: > > The configuration step goes OK. In particular note that I set > -DOPENGL_glu_LIBRARY:FILEPATH=/usr/lib64/libGLU.so I think with OSMesa, this should be

Re: [Paraview] numpy build issues

On Fri, Oct 16, 2015 at 18:44:40 +, Scott, W Alan wrote: > I am having issues getting ParaView, remote cluster, working with my > own build of Python and numpy. Obviously, I don't have root on these > clusters, and I want to use my own Python. (Clusters often have 10 > year old python.) > >

Re: [Paraview] Successful SuperBuild on OSX 10.11?

On Wed, Oct 07, 2015 at 00:23:45 +0100, Mathew Guilfoyle wrote: > I have just upgraded to OS X 10.11 and am now unable to build Paraview > > I had successfully built the Suepbuild 4.4.0 on OS X 10.10 using my > installed Qt4.8 (I was unable to build against the Qt that comes with > the

Re: [Paraview] No module named paraview...

On Wed, Sep 09, 2015 at 09:18:26 +0800, Ruggiero Guida wrote: > I am trying to run paraview scripts from the command line without using the > specific pvpython from paraview (this one works). Look at the paths in the output of: >>> import sys >>> sys.path from pvpython. You may be

Re: [Paraview] /usr/bin/paraview not packaged with CPack in Paraview 4.3.1 Superbuild

On Mon, Sep 14, 2015 at 02:00:22 +, Anthony Crognale wrote: > After enabling qt and recompiling after a clean, I receive the following > error: "make clean" isn't really reliable in a superbuild. I usually do "rm -rf */"[1] in the build tree to keep the cache but kill any state related to

Re: [Paraview] /usr/bin/paraview not packaged with CPack in Paraview 4.3.1 Superbuild

On Sun, Sep 13, 2015 at 21:35:20 -0400, Ben Boeckel wrote: > I think qt was renamed to qt4 after 4.3.1 was released Just looked; this is indeed new for 4.4.0. --Ben ___ Powered by www.kitware.com Visit other Kitware open-source projects at h

Re: [Paraview] /usr/bin/paraview not packaged with CPack in Paraview 4.3.1 Superbuild

On Mon, Sep 14, 2015 at 14:15:26 +, Anthony Crognale wrote: > I had been using the system libpng version 1.2.52, but it appears > `png_set_longjmp_fn` was not introduced until 1.6, so I tried building > libpng 1.6.18 from source last night, which then allows Paraview to > continue building

Re: [Paraview] /usr/bin/paraview not packaged with CPack in Paraview 4.3.1 Superbuild

On Mon, Sep 14, 2015 at 00:55:42 +, Anthony Crognale wrote: > /usr/bin/paraview is not in this list, nor the other binaries that I > would expect when it is built. Usually means Qt wasn't enabled. > I've attached my CMakeCache.txt to this email as it would be rather > large to paste. > >

Re: [Paraview] /usr/bin/paraview not packaged with CPack in Paraview 4.3.1 Superbuild

On Mon, Sep 14, 2015 at 21:41:09 +, Anthony Crognale wrote: > Looks like building for release worked properly, the resulting > Paraview runs fine now. > > Thanks much for your help! Great! FYI, the release mode improvments are here:

Re: [Paraview] /usr/bin/paraview not packaged with CPack in Paraview 4.3.1 Superbuild

On Mon, Sep 14, 2015 at 19:05:27 +, Anthony Crognale wrote: > Another quick follow up (sorry!) > > [pid 360] > stat("/home/acrognale/paraview/build/qt/src/qt/src/3rdparty/libpng", > {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 > [pid 360] openat(AT_FDCWD, >

Re: [Paraview] /usr/bin/paraview not packaged with CPack in Paraview 4.3.1 Superbuild

On Mon, Sep 14, 2015 at 19:29:58 +, Anthony Crognale wrote: > I was indeed compiling in Debug mode! Is there a different recommended > way to compile the application in debug mode then? Not cleanly. I can add a flag for that as well. Currently, once ParaView is done configuring, stop the

Re: [Paraview] Direct link to ParaView sources not working with wget

On Mon, Sep 28, 2015 at 07:22:52 +, Schlottke-Lakemper, Michael wrote: > Thanks for the quick fix! I still end up with a file named > "download.php?submit=Download=v4.4=source=all=ParaView-v4.4.0-source.tar.gz” > (and that can be fixed using "-O filename”), but at least the > downloading works

Re: [Paraview] QT5/libxcb on RHEL5

On Wed, Sep 23, 2015 at 16:46:51 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > I’m doing some test build of PV 4.4.0, and if I try to build using > QT5, I need to have access to the libxcb libraries.It doesn’t look > like there’s an RPM for this for RHEL5 .Can the

Re: [Paraview] rpath error when compiling ParaView 5.0

On Sat, Dec 05, 2015 at 20:53:49 +0200, Armin Wehrfritz wrote: > I'm building ParaView (version 5.0 RC1) for openSUSE Tumbleweed (using > gcc 5.2.1) and get an error related to rpath (see below). I cannot say > much more about this, since don't really understand what's going wrong here. > > Does

Re: [Paraview] OpenGL Backend Identification

On Mon, Dec 07, 2015 at 14:49:51 -0500, Tim Thirion wrote: > I'm looking to provide run-time identification of the current OpenGL > backend in use. Some questions: > > 1. VTK #defines VTK_OPENGL2, but ParaView #defines VTKGL2. Is there a > particular reason we have both? VTK used to have both.

Re: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5

On Thu, Dec 10, 2015 at 17:20:35 +0100, Albina, Frank wrote: > Thank you for the reply. My idea was to run PV-5.0.0-RC1 in parallel on our > cluster, > therefore the need to recompile as the binaries do not usually ship with this > feature > and I guess that you do not necessarily know either

Re: [Paraview] Differences between OpenGL and OpenGL2 versions of ParaView

On Wed, Dec 16, 2015 at 13:22:09 -0600, Adam Lyon wrote: > I'm curious as to why I didn't have any of these problems in v4.4 -- or is > this two path multiblock rendering code all new for v5? Thanks again!! -- 4.4 defaults to the OpenGL1 backend (glBegin/glEnd); 5.0 is using the OpenGL2 backend

Re: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5

On Thu, Dec 10, 2015 at 09:18:44 -0500, Ken Martin wrote: > people on this list are more familiar with the specifics of setting up SWR > and Mesa on a cluster but I wanted to at least give you a quick response to > let you know we are working on it :-) The binaries built by our buildbots (and

Re: [Paraview] OpenGL Backend Identification

On Thu, Dec 10, 2015 at 09:29:27 -0500, Ken Martin wrote: > Maybe vtkRenderingOpenGLConfigure.h ? > > That header is configured from a .in file for both the old and new backend. > We could define VTK_OPENGL2 in that header and applications could include > it as needed. That header appears to get

Re: [Paraview] OpenGL Backend Identification

On Thu, Dec 10, 2015 at 10:08:14 -0500, David E DeMarle wrote: > And it should appear in a wrapped class so that we can get it at runtime > from python. In that case, there should probably be an enum in RenderingCore: enum vtkRenderingBackend { ... }; class

Re: [Paraview] How to stop a paraview python script on error (try-catch-ing) ?

On Sat, Jan 02, 2016 at 16:12:49 +0100, houssen wrote: > How to stop a paraview python script on error (try-catch-ing) ? > > I have a filter (which calls vtkErrorMacro when an error occurs). I > have a python script that uses this filter from paraview: how to stop > this script when an error

Re: [Paraview] What is the difference between pvbatch and pvpython ?

On Thu, Jan 07, 2016 at 16:50:16 +0100, houssen wrote: > What is the difference between pvbatch and pvpython ? (general purpose > question) > > My understanding is that one can always use python scripts (from > paraview, pvbatch, pvpython), paraview has the GUI, pvbatch is "paraview > in batch

Re: [Paraview] passing argument to pvpython script

On Wed, Nov 25, 2015 at 15:11:43 +0300, Gena Bug wrote: > And this works fine untill I tried new version. In 5rc1 I always get > Segmentation Fault: > Error running > "~/ParaView-5.0.0-RC1-Qt4-OpenGL2-Linux-64bit/lib/paraview-5.0/pvpython" > "myscript.py" "filename"Segmentation fault > >

Re: [Paraview] ParaView 5.0.0-RC1: two minor problems

On Fri, Nov 20, 2015 at 11:23:02 -0500, Hom Nath Gharti wrote: > In Linux 64-bit binary > 1) error while loading shared libraries: libbz2.so.1.0: cannot open > shared object file: No such file or directory > > ln -s /lib64/libbz2.so.1 libbz2.so.1.0 fixed the problem. Hmm, interesting. It seems

Re: [Paraview] [Non-DoD Source] ANN: ParaView 5.0.0-RC1 is available for download

On Wed, Jan 13, 2016 at 16:50:59 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Has anyone tried or been able to build ParaView 5.0 on RHEL5?Looks > like there may be compiler dependencies which exclude a successful build > on RHEL5? So far, I’ve not had any luck

Re: [Paraview] ANN: ParaView 5.1.0-RC1 available for download

On Mon, Jun 13, 2016 at 12:11:29 -0400, 曹智选 wrote: > It turned out that the operating system on my machine does not have the > library: GLIBCXX_3.4.15. And the linux system on my machine does not allow > me upgrading the library to GLIBCXX_3.4.15. > Is there any other way that I can still use the

Re: [Paraview] Required CMake version 3.5

On Wed, Jun 22, 2016 at 05:21:33 +0200, Christoph Grüninger wrote: > thanks for link to the developer mailing list discussion. I think CMake 3.3 > is better then > 3.5, because at least the last Leap 42.1 release provides that. > I patched ParaView to require CMake 3.0 and it builds fine. I will

Re: [Paraview] Required CMake version 3.5

On Fri, Jun 24, 2016 at 15:50:45 +0200, Christoph Grüninger wrote: > I don't think it is a good idea to ask for the latest version. Only > developers like us have > a current version of CMake installed. From already released distributions > nobody > provides CMake 3.5. My thought here is that

Re: [Paraview] Required CMake version 3.5

On Fri, Jun 24, 2016 at 09:28:29 -0400, Jim wrote: > Can you let me know how it goes? I just pulled the latest versions of > Paraview & cmake and want to build under VS2015. I'm going to work on it > over the weekend. If you're doing the same, I could use any > configuration tricks you

Re: [Paraview] Required CMake version 3.5

On Fri, Jun 24, 2016 at 00:25:00 +0200, Cory Quammen wrote: > @Utkarsh, any foreseeable problems reducing the CMake required version to 3.3? I think we'll want 3.5 in the (hopefully) near future, so if distributions don't have a new enough CMake, they can patch it down to 3.3 in the meantime. A

Re: [Paraview] [Non-DoD Source] ANN: ParaView 5.0.0-RC1 is available for download

On Wed, Jan 13, 2016 at 18:50:21 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > gcc on our RHEL5 systems is 4.1 and seemingly cannot be upgraded. I think there is also a "gcc44" package which contains a gcc4.4 binary (and is parallel installable). But I don't remember if

Re: [Paraview] compiling mdf error

On Tue, Feb 02, 2016 at 10:06:25 +, mersad mostaghimi via ParaView wrote: > Dear Cory Quammenthe first problem is solved but there is an other > problem  which is again an MD5 problem. this time is in VTK > installation during installing Paraview from source files. If you don't need testing

Re: [Paraview] Troubles building mathstuf/qhull subproject using PV 4.4.0 superbuild with Intel >14.x compilers

extern "C" { #include "qhull.h" } which won't work since qhull is a C++ header. Are there any 'extern "C"' bits around? Passing -E (or whatever Intel's equivalent is) to dump the preprocessed source would help to see. The __cplusplus check may be guardin

Re: [Paraview] [EXTERNAL] Symbol WinMain missing when compiling with Visual Studio

On Thu, Jun 30, 2016 at 19:20:58 +, Scott, W Alan wrote: > Try building without Ninja? If that also fails, I could try a build > of my own. Haven't done so in 6 months, but it seems to work. > > By the way, what version of Visual Studio? Also relevant: version of CMake and Qt. --Ben

Re: [Paraview] Query on ccmake for building Paraview

On Wed, Feb 08, 2017 at 02:10:27 -0500, Bishwajit Dutta wrote: > I had the below query. Thanks to pls help out. > > I wanted to build Paraview 4.0.1 source on my 64 bit ubuntu system. I need > to > configure options to build with mesa and I read that this is to be done > with ccmake. > > Now I

Re: [Paraview] Windows plugin compatibility with Paraview

On Wed, Jan 25, 2017 at 11:08:00 -0600, Chris Marsh wrote: > I would like to build and make available a pre-compiled windows binary for > a filter I have developed. I would like to avoid the (windows) user having > to compile the filter as well as paraview. Therefore I am wondering what > compiler

Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?

On Wed, Feb 22, 2017 at 13:10:04 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Cory - so I did a “git pull” and “git submodule update” in my existing > paraview-superbuild repository directory and that 5.3.0-RC1 information > was not in the versions.cmake file. I did a

Re: [Paraview] PVSB 5.2: missing modules and plugins after "make install"

On Fri, Feb 17, 2017 at 13:17:37 +, Michel Rasquin wrote: > Has anybody already tested successfully PVSB 5.2 from the install > directory without loosing plugins and other module down the road? Oh, running from the install directory? That's not really fully supported. The reason is that we

Re: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641

On Tue, Feb 21, 2017 at 17:57:37 +0100, Nabil Ghodbane wrote: > many thanks for the prompt reply. I should have hit the toggle option :). It's fine, that bug is elusive and a pain to deal with. > No i did not give it a try yet. I will try it and send feedback (I am using > miniconda) > Does this

Re: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641

> > On Tue, Feb 21, 2017 at 9:25 AM, Nabil Ghodbane > > wrote: > > > OK many thanks,; I am trying to use the Superbuild now. > > > I can see that it is downloading Python 2.7.11. Is there a particular > > reason > > > to use this version instead of the 2.7.12? Haven't

Re: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641

On Wed, Feb 22, 2017 at 09:37:47 +0100, Nabil Ghodbane wrote: > - I am requesting USE_SYSTEM_hdf5 = OFF > but looking as you suggested in superbuild/paraview/build/CMakeCache.txt, I > can see that VTK_USE_SYSTEM_HDF5:BOOL=TRUE > Shouldn't this be FALSE ? >From ParaView's point of view, it is

Re: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download

On Tue, Feb 14, 2017 at 10:04:50 -0500, Utkarsh Ayachit wrote: > Chuck, is this a CMake version related issue? Ufuk, which cmake > version are you using? It likely is. VTK is now using CMake's C++11 support detection and older versions of CMake do not have the required bits for Intel 16. These

Re: [Paraview] PVSB 5.2: missing modules and plugins after "make install"

On Sat, Feb 11, 2017 at 17:48:27 -0500, Cory Quammen wrote: > Will updating to the current superbuild master address the missing > plugins issue Michel is seeing? It looks like there have been some > minor changes on plugin handling in linux since > 4ec37480a6f1ad39c9aa3168c2f0e6a1b0147b16. Yes,

Re: [Paraview] (no subject)

On Mon, Feb 13, 2017 at 14:16:03 -0500, Bishwajit Dutta wrote: > http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download=b10bd3f7136ef809f1df7ad5c94c553f=MD5 > ("Couldn't connect to server") > > http://www.paraview.org/files/ExternalData/MD5/b10bd3f7136ef809f1df7ad5c94c553f >

Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?

On Thu, Feb 16, 2017 at 16:53:55 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Fabian - thank you - that was enough of a hint to get me over the hump. > Switched my build to qt5 AND based on some information from a previous > email thread, I added the following to my CMAKE

Re: [Paraview] Superbuild repo change?

On Wed, Feb 15, 2017 at 13:50:13 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > I did a fresh pull of the ParaView superbuild repository, and now I can’t do > a clean build of PV 5.2.0 on my Mac (OSX 10.9.5). > > First, I had to remove the entries for “qt” and “scipy" in

Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?

On Fri, Feb 17, 2017 at 12:43:17 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Cmake was complaining about CMAKE_OSX_SDK not being set … > I’m not sure if I needed to set both variables, but I recalled seeing this > in a mail thread, so I just set it! 8-) Ah, then you

Re: [Paraview] packing superbuild 5.2 fails on openSUSE due to ldconfig

On Tue, Jan 17, 2017 at 11:19:40 +0100, Fabian Wein wrote: > ldconfig is on openSUSE and Ubuntu /sbin/ldconfig but sbin in on > openSUSE not in the user path. For me a link in $HOME/bin helped but > maybe using the full path > would work on all unix systems?! I guess we'll go with the full

Re: [Paraview] Issues viewing PV5.0.0 Filters/Alphabetical submenu

On Tue, Feb 28, 2017 at 19:02:50 +0900, kenichiro yoshimi wrote: > Has this issue been resolved? > > I think that this might be caused by a bug in Qt 4.8.6: > https://bugreports.qt.io/browse/QTBUG-54921 I think we came to the same conclusion. Windows has used Qt4 4.8.4 since then to avoid the

Re: [Paraview] [vtkusers] Testing ITK/VTK/PV contributions with (kitware) Gitlab-CI

On Thu, Sep 08, 2016 at 12:36:40 +0200, Grothausmann, Roman Dr. wrote: > Just getting to know Gitlab-CI, I am wondering whether it is possible to test > contributions to ITK/VTK/PV with Gitlab-CI from gitlab.com or > gitlab.kitware.com. As far as I understand, this basically needs runners, in >

Re: [Paraview] [vtk-developers] Which Compilers and Operating Systems to you require for VTK and / ParaView?

On Mon, Sep 26, 2016 at 14:01:38 -0400, Chuck Atkins wrote: > Just as a follow-up, I will be leaving this survey open all week and stop > accepting responses on Friday, October 30. I assume you mean September 30? --Ben ___ Powered by www.kitware.com

Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.

On Wed, Sep 28, 2016 at 17:54:53 +0200, Albina, Frank wrote: > I had to recompile from scractch, which took a bit of time. Actually, > the GNU compiler requirement is coming from building the OSPRAY > project, as shown hereafter: > > [...] > CMake Error at cmake/gcc.cmake:48 (MESSAGE): > GCC

Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.

On Wed, Sep 28, 2016 at 10:06:15 +0200, Albina, Frank wrote: > In this regard, I would like to point out a few things I have found > while performing the build process on the aforementioned Linux > distribution. Note that my incentive is to help improve the ParaView > software suite as well as

Re: [Paraview] ParaView 5.2 Release Candidate 2 available for download

On Thu, Oct 20, 2016 at 15:13:51 +0300, Gena Bug via ParaView wrote: > Now, with RC2, fontconfig warns me about blank section: > > Fontconfig warning: line 160: blank doesn't take any effect anymore. > please remove it from your fonts.conf We're now using a newer fontconfig, so the fontconfig

Re: [Paraview] ParaView 5.2 Release Candidate 2 available for download

On Fri, Oct 21, 2016 at 10:31:00 -0400, David Thompson wrote: > Your attempt to set CMAKE_OSX_SDK=10.12 was probably on the superbuild > project, and it is not passed to the Qt subproject as QT_MAC_SDK. Try > passing the proper value to CMAKE_OSX_SDK (i.e., the full path which > is usually >

Re: [Paraview] ParaView 5.2 Release Candidate 2 available for download

On Thu, Oct 20, 2016 at 16:03:05 +0200, Fabian Wein wrote: > Are you interested in superbuild tests, too? Or do you want to skip > that issue for the time 5.2 is released? We're interested :) . > On macOS 10.12 Sierra I have problems building qt5: Hmm, we haven't done 10.12 yet; upgrading it

[Paraview] [ANN] Dropping 32bit binaries for 5.3 and beyond

Hi, We're planning on dropping 32bit binaries (currently only provided on Windows) for post-5.2 development. Any objections? --Ben ___ Powered by www.kitware.com Visit other Kitware open-source projects at

Re: [Paraview] ParaView 5.2 Release Candidate 1 available for download

On Wed, Oct 12, 2016 at 16:05:28 +0200, Albina, Frank wrote: > Issue being configuration messages. Oh, you're compiling 5.1.2 with the new superbuild; yes, that'd have the same thing. I'll look to see if there's a way to get FONTCONFIG_PATH default to the right place. Thanks for the hint. --Ben

Re: [Paraview] ParaView 5.2 Release Candidate 1 available for download

On Tue, Oct 11, 2016 at 23:30:16 +0300, Gena Bug via ParaView wrote: > I've just tried the 5.2rc and noticed this in the console: > > $ Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line > 72: non-double matrix element > Fontconfig error:

Re: [Paraview] ParaView 5.2 Release Candidate 1 available for download

On Wed, Oct 12, 2016 at 15:36:24 +0200, Albina, Frank wrote: > I have been having similar issue when compiling ParaView 5.1.2 from > source with QT4 support, which depends on the fontconfig project. > I could get rid of it by setting FONTCONFIG_PATH to /etc/fonts on my > system. "Issue" being

Re: [Paraview] ParaView 5.2 Release Candidate 1 available for download

On Wed, Oct 12, 2016 at 10:42:43 -0400, Ben Boeckel wrote: > Oh, you're compiling 5.1.2 with the new superbuild; yes, that'd have the > same thing. I'll look to see if there's a way to get FONTCONFIG_PATH > default to the right place. Thanks for the hint. Looks like updating to t

  1   2   >