On Thu, Oct 13, 2016 at 13:57:58 +0300, Gena Bug via ParaView wrote:
> I'm slightly confused with background color for the screenshots when
> trying to override palette. If I set Background to a Single color in the
> Properties tab (gray by default) then nothing can change it --
> background
On Fri, Dec 09, 2016 at 01:23:29 -0500, Luo Han wrote:
> I have a script to post processing data. It needs pvpython to call it. The
> script import multiprocessing module. But when I import the package, it
> shows:
Yeah, it isn't a full Python; I had tried stripping it down, but that
turns out to
On Thu, Jan 05, 2017 at 13:07:32 +0100, Fabian Wein wrote:
> I think there is still an issue building plugins via
> -DENABLE_paraviewpluginsexternal:BOOL=ON when building
> paraview-superbuild.
>
> cmake ../paraview-superbuild -DCMAKE_BUILD_TYPE:STRING=Release
> -DBUILD_TESTING=OFF
On Fri, Jan 06, 2017 at 14:36:53 -0500, Cory Quammen wrote:
> Thanks for the report. I looked into this and I think I know what is going on.
>
> In ParaView 5.2.0, we reduced the number of Python modules that
> shipped with the ParaView binaries. One of the modules not included
> was the
On Mon, Jan 02, 2017 at 21:36:51 +0100, Fabian Wein wrote:
> Then I do something wrong:
>
> cmake ../paraview-superbuild -DCMAKE_BUILD_TYPE:STRING=Release
> -DBUILD_TESTING=OFF -DENABLE_cxx11=ON -DENABLE_qt5=ON -DENABLE_boost:BOOL=ON
> -DENABLE_hdf5:BOOL=ON -DENABLE_zlib:BOOL=ON
On Fri, Dec 30, 2016 at 23:48:52 +0100, Fabian Wein wrote:
> • enable_paraviewexternalplugins:BOOL=ON: Enables building using external
> plugins.
Sorry, that should be ENABLE_paraviewexternalplugins. PR pushed:
https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/253
On Thu, Dec 22, 2016 at 21:10:04 +0100, Fabian Wein wrote:
> What is the relationship of paraview-superbuild and common-superbuild?
The common superbuild is updated via merge requests in
paraview-superbuild; it does not track master automatically. I'll make a
merge request here today.
You can
On Mon, Mar 20, 2017 at 11:31:28 -0700, Burlen Loring wrote:
> I had to apply to clang-format manually. it's up there now. changes were
> minimal so I squashed them into the patch.
The fixes would have had to had been squashed in anyways; the robot
checks each commit individually.
> System has
On Tue, Mar 14, 2017 at 17:58:18 -0400, Cory Quammen wrote:
> The superbuild was tagged with v5.3.0 this morning.
That may be, but it seems you missed pushing it to the main repository
:) .
--Ben
___
Powered by www.kitware.com
Visit other Kitware
On Fri, Mar 17, 2017 at 12:36:10 -0700, Burlen Loring wrote:
> fyi, https://gitlab.kitware.com/paraview/paraview/merge_requests/1476
>
> it complains about clang-format, but it seems that the source file was
> not formatted in that way to begin with.
When I enabled clang-format checking, I did
On Mon, Apr 10, 2017 at 16:18:21 +0200, Nabil Ghodbane wrote:
> it is not clear to me what you did. Did you build your own docker with
> Paraview on top of it and if this is the case could you share the
> Dockerfile you implemented to build the docker image?
The Dockerfile (and associated files)
On Fri, Apr 07, 2017 at 18:30:11 +0200, Florian Hoffmann wrote:
> does anybody out there would like to share some experience with a recent
> ParaView Superbuild (>=version 5.2) with *Docker* ?
>
> - Suggestions/recommendations for existing Dockerfiles ?
>
> - Suggestions for settings like: Qt
On Thu, Apr 13, 2017 at 08:26:22 -0400, David E DeMarle wrote:
> Turn on paraview_FROM_SOURCE_DIR
Note that the `master` and `5.3.0` branches now have
`paraview_SOURCE_SELECTION` and it should be set to `source`.
--Ben
___
Powered by www.kitware.com
On Thu, Apr 20, 2017 at 15:33:30 +0200, Patrick Begou wrote:
> This could be solved with disabling swr gallium driver and selecting only
> swrast, even if my cpu is from intel family and provides AVX :
>
> --with-gallium-drivers=swrast
You should be able to unset the `mesa_USE_SWR` option (it's
On Tue, Apr 18, 2017 at 09:57:49 +0200, Patrick Begou wrote:
> I've posted this email last week but I did not reveive it via the list. May
> be a
> mistake of myself. I appologize if some one reveive it twice.
>
> I'm trying to compile Paraview 5.3 on CentOS6 because I use a modified
> OpenMPI
On Tue, Apr 18, 2017 at 18:15:00 +0200, Patrick Begou wrote:
> Something additionnal to set ?
This was fixed in VTK here:
https://gitlab.kitware.com/vtk/vtk/commit/641fc17e5e63f7ae5c3654f86a4ac97a33a2c63a
HDF5 can be found with targets or with library paths. The VTK module
system does not
On Tue, Apr 18, 2017 at 13:23:36 -0400, Ben Boeckel wrote:
> We can fix this in the superbuild by setting that in `paraview.cmake`.
> I'll make that change.
https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/308
On Thu, Apr 20, 2017 at 14:44:47 -0700, Burlen Loring wrote:
> [100%] Freezing Python and ParaView Python packages and modules
> Removing
> /usr/common/software/ParaView/builds/ParaView-5.3.0/Utilities/PythonInitializer/FrozenPython
> Error: could not find python lib directory
> Use
>
On Tue, Mar 14, 2017 at 12:01:32 -0300, Rodnei Couto wrote:
> Python modules are different from 5.2 to 5.3
>
> For example, inside* lib/python2.7/site-packages, *the version 5.2 has the
> modules *autobahn, zope and twisted*, and the version 5.3 does not.
>
> I tried to copy the twisted and zope
On Tue, Aug 15, 2017 at 17:59:47 +0300, u.utku.turunco...@be.itu.edu.tr wrote:
> I solved the problem and i am able to run the simulation code with
> Catalyst support by installing PV (5.4.0 rc4 and 5.3.0) with newer version
> of protobuf library (3.3.0) and compiling the model code with this
On Mon, Aug 14, 2017 at 20:45:41 +0300, u.utku.turunco...@be.itu.edu.tr wrote:
> Again thanks for your help. I tried to use protobuf 3.3.0 with PV 5.4.0rc4
> but i am getting following error
>
> CMake Warning at
>
>
On Sun, Aug 13, 2017 at 21:44:41 +0300, u.utku.turunco...@be.itu.edu.tr wrote:
> I am trying to install a code with support ParaView, Catalyst (version
> 5.3) to a new system. In this case, the code crash (seg. fault) at the
> beginning without giving any valuable hint about the problem. If I run
On Mon, Aug 14, 2017 at 16:49:55 +0300, u.utku.turunco...@be.itu.edu.tr wrote:
> Thanks for your help. The server is Scientific Linux release 7.3
> (Nitrogen) and yes i install PV from source using NVIDIA EGL libraries. In
> this case, I set USE_X OFF and also QT_GUI OFF. I tried both Intel (2017)
On Thu, Jul 13, 2017 at 14:54:11 +0200, Nabil Ghodbane wrote:
> dear experts,
> on a CentOS6.8 x86_64 node, I used the Superbuild to compile Paraview
> 5.3.0-1 with dev tool 4 (which provides gcc 5.3 )
>
> As shown on the attached screen captures, In the CCMAKE configuration, I
> enabled Python
On Wed, Jul 12, 2017 at 19:23:20 +, Scott, W Alan wrote:
> I remember a thread from a few weeks ago that the current Linux
> distribution has built in MPI. Is this correct? Does this mean a
> user can use the Kitware binaries on a cluster, without rebuilding?
Theoretically, yes? Though I'd
On Thu, Jul 13, 2017 at 14:38:08 -0600, Martin Cuma wrote:
> I have been having trouble running the release binary of Paraview on
> relatively stock CentOS 7.2 using
> the OpenGL. It segfaults before it loads up the GUI window.. If I start
> Paraview with the --mesa option,
> it works fine.
>
>
On Fri, Jul 14, 2017 at 12:11:38 -0600, Martin Cuma wrote:
> I tried the backtrace but it does not show anything useful since there are
> no symbols in the binary. Do you have a binary build that includes symbols
> that I could download and try to run?
Not on hand, sorry. The backtrace might
On Fri, Jul 14, 2017 at 18:57:18 +, Martin Cuma wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
Run `bt` (short for `backtrace`) to get a trace. Though if this frame is
`NULL`, I suspect something went really badly somewhere :/ .
> So, as you can
On Thu, Jul 20, 2017 at 13:03:12 +, Amine Aboufirass wrote:
> It appears that the module is defined but it has trouble with some of
> the VTK submodules. I tried to import VTK on its own but since the
> modules inside make use of the old print statement (no parentheses)
> there is not a way to
On Fri, Apr 21, 2017 at 12:10:36 -0700, Burlen Loring wrote:
> That file lives in: lib/python2.7/config/config.c.in
OK, it looks like the freeze_paraview.py file can't find it. Could you
debug around line 250 to see what it is actually doing?
> -set(ENV{PYTHONPATH} "${PACKAGE_ROOT}")
>
On Thu, Apr 27, 2017 at 17:04:24 +, Lawson, Joel M. wrote:
> It worked! Thank you very much.
> Out of curiousity, what does the --mesa option do?
We build Mesa as part of our packages and place the required libraries
under `lib/paraview-5.3/mesa`. The `--mesa` flag just adds that
directory to
On Wed, May 03, 2017 at 16:59:18 +0200, Patrick Begou wrote:
> Even with v5.3.0-1 the problem remains. It seams related to the OSMESA
> config
> as a QT4 config on my desktop is successfull (same compilers and OpenMPI
> version
> but CentOS 6.9 instead of 6.7 on the cluster).
>
> On the
On Wed, May 03, 2017 at 11:55:15 +0200, Patrick Begou wrote:
> My git commit is:
>
> commit 8c380916ea13198b8912bef78971a71bba6d7147
> Merge: e75a492 84ebd63
> Author: Ben Boeckel <ben.boec...@kitware.com>
> Date: Tue May 2 12:33:58 2017 +
Are you building
On Tue, May 16, 2017 at 19:07:14 +0200, Ephraim Obermaier wrote:
> $ mpirun -n 2 pvpython test.py
I believe you want to use pvbatch for MPI-enabled Python scripts.
--Ben
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
On Thu, Oct 12, 2017 at 11:41:46 +0200, Christophe Trophime wrote:
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -g -O2
>
On Thu, Oct 12, 2017 at 09:39:29 -0400, Ben Boeckel wrote:
> Hmm, my browser history says I searched for this back in July… looking
> around there finds:
>
> https://gitlab.kitware.com/paraview/paraview/issues/17456
>
> which seems to have dropped off our radar. Is the V
On Wed, Nov 15, 2017 at 11:40:43 -0500, Ken Martin wrote:
> Basically there is a bug in Qt on windows where it refuses to see the 3.2
> context from Mesa because it is not a compatibility context.
On startup, Qt makes a context without a profile. Mesa gives it the best
compatibility profile it
On Sun, Nov 12, 2017 at 22:42:29 +, Scott, W Alan wrote:
> What are the magic cmake switches, for superbuild, that are used to
> build a non MPI, Mesa version of pvbatch? Where is this documented?
pvpython is the non-MPI version of pvbatch. The superbuild docs could
probably be improved
On Mon, Nov 13, 2017 at 22:04:19 +, Scott, W Alan wrote:
> I believe this is a change from the past. Here is what I desire – how
> do I get it?
>
> I want to run pv(pythonScript). I want it to produce output. I want
> it to run off screen, not showing on the console display or current
>
On Fri, Nov 03, 2017 at 19:49:26 +, the lily wrote:
> export PYTHONPATH=$PYTHONPATH:/Applications/ParaView-5.4.1.app/Contents/bin
The modules should be in /path/to/.app/Contents/Python. Try:
export
PYTHONPATH=$PYTHONPATH:/Applications/ParaView-5.4.1.app/Contents/Python
--Ben
On Tue, Dec 05, 2017 at 10:20:50 +1300, Zohar Levi via ParaView wrote:
> To be more specific, I'm building paraview 5.4.1 (gcc on cygwin), and I
> get the following errors:
>
> $ make
> [� 0%] Built target vtkWrappingTools
> [� 0%] Built target vtkWrapHierarchy
> [� 0%] Building CXX object
>
On Sun, Oct 29, 2017 at 20:10:26 +0100, Fabian Wein wrote:
> I could not find the build error in the link.
>
> The earliest version that builds for my gcc 7.2.1 is
> fontconfig-2.12.4, maybe this is a „compromise“?
Ah, sorry, I forgot to report back here. The issue is fixed on master.
It
On Wed, Oct 25, 2017 at 13:35:51 +0200, Fabian Wein wrote:
> thank you! So the current master will have the upgrade within a few days?
Hopefully. I need to get `gperf` onto the build machine since it is a
new build dependency of fontconfig.
--Ben
___
On Wed, Oct 25, 2017 at 13:35:51 +0200, Fabian Wein wrote:
> thank you! So the current master will have the upgrade within a few days?
It's not so simple :( . There's a build failure with older compilers:
https://open.cdash.org/viewNotes.php?buildid=5114526
--Ben
On Tue, Oct 24, 2017 at 16:51:09 +0200, Fabian Wein wrote:
> fontconfig 2.12.1 does not compile with the error at the end of this
> mail.
>
> Building the current fontconfig 2.12.6 works for me, maybe the version
> could be upgraded?
I've pushed an MR for the common-superbuild here:
On Fri, Oct 20, 2017 at 08:40:34 -0400, Cory Quammen wrote:
> I strongly recommend using the Ninja generator for building ParaView with
> Superbuild on Windows. It will build much faster than if you use other
> build generators, and will take care of the particular problem you are
> seeing as -j
On Thu, Jan 25, 2018 at 11:40:40 +0100, Nicolas Vuaille wrote:
> I don't know if there is a proper fix but there is a CMake option to bypass
> this check:
> set PYTHON_I_KNOW_WHAT_IM_DOING to true may solve the problem.
Indeed, this is the workaround. The problem is that we've had folks with
On Thu, Feb 08, 2018 at 15:46:27 +, Hermitte Luc (CS SI) wrote:
> I'm calling cmake with the following options?:
> cmake -Dqt5_enabled=On -DUSE_SYSTEM_qt5=On(/Off)
> -DQt5_DIR=/path/to/qt/5.9.1/lib/cmake/Qt5 ..
The input setting is `ENABLE_qt5`. The `qt5_enabled` variable indicates
On Wed, Dec 20, 2017 at 22:50:50 +, Heiland, Randy wrote:
> Ah, I see ‘os’ has been hijacked by PV. But something like this seems
> to accomplish what I want, maybe…
>
> Create a new module for PV:
>
> /Applications/ParaView-5.4.1.app/Contents/Python$ more envs.py
> import os
>
On Thu, Dec 21, 2017 at 23:37:55 +, Beach, Timothy A. (GRC-LTE0)[Vantage
Partners, LLC] wrote:
> Helo, I’ve been working through some issues compiling on a new MAC
> but this one has me stuck. I used CMAKE 3.10 to generate xcodebuild
> files for paraview 5.4. Any ideas?
Yep, Working on a
On Thu, Dec 21, 2017 at 15:14:01 +, Heiland, Randy wrote:
> Thanks Ben. You’re right, of course. Moreover, my idea for having
> (non-admin) users install additional Python modules (e.g., scipy) into
> PV’s dir, is a not going to go well.
Well, if `sys.path` or `PYTHONPATH` can be pointed to
101 - 151 of 151 matches
Mail list logo
