Python /Versions/5/Qtcore (Which Was Built For Mac Os X 10.11)

Python /Versions/5/Qtcore (Which Was Built 10.11) Software But You#

Python /Versions/5/Qtcore (Which Was Built 10.11) Software But You

The display area is just background color. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.From utkarsh.ayachit at kitware.com Mon Jun 27 08:53:42 2016From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)Subject: Scalar scaling of glyphs causes unrecoverable errorDo you have a sample dataset to share to reproduce this issue? AlsoWhat version of ParaView are you trying this with?> I can import (raw binary) a 3D file (1178x1202x1000x1float), extract a> subset and display it using sphere glyphs where the spheres are too large.> However, when I set the scale mode to scalar and 1, the program displays> nothing. A simple guide on installing the latest Qt (currently 5.6) and PyQt5 on Mac OS X 10.11 (El.Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. PyQt5 is a toolkit for creating Python GUI applications.

It could be the newer> driver we use since a few weeks, but like I said, I don't see issues> Paul, can you try with ParaView 5.0.0 and 4.4 binaries as well? Since> those worked before, let's see if it's a NVIdia driver change that's> 4.4 works without problem in client-server mode (although I can't seem> to get subsampled rendering during interaction working, no matter what> remote render settings I try). It looks like a bug to> _> Visit other Kitware open-source projects at> Please keep messages on-topic and check the ParaView Wiki at:> Follow this link to subscribe/unsubscribe:From samuelkey at bresnan.net Mon Jun 27 09:47:07 2016From: samuelkey at bresnan.net (Samuel Key)Subject: PV 4.1 how to extract a surfaceFrom paul.melis at surfsara.nl Mon Jun 27 11:29:37 2016From: paul.melis at surfsara.nl (Paul Melis)Subject: Client-server mode fails with 5.0.1> On 18-04-16 20:04, Utkarsh Ayachit wrote:> This has always worked for me with earlier versions of> ParaView, but something seems to have changed. If I delete everything and then retry without the scaling, I still> This looks like some sort of workspace corruption.

VTK will run in a compatibility mode designed to work withEarlier versions of OpenGL but some features may not work.The supported OpenGL version is 4.2.0, so I don't understand why theServer glx vendor string: NVIDIA CorporationClient glx vendor string: NVIDIA Corporation, NVIDIA CorporationOpenGL renderer string: GeForce GTX 780 Ti/PCIe/SSE2OpenGL version string: 4.5.0 NVIDIA 367.27The nvidia driver used is 367.27, Debian 7.11 (wheezy), 64-bitFrom utkarsh.ayachit at kitware.com Mon Jun 27 13:15:24 20161. A test between my workstation (PV client)> and a different machine (PV server) with driver 352.79 also works.> I just tried on a node with an updated nvidia driver (367.27, latest> for the specific model of GPU used) and get the same error on the> Trying 5.1.0 (binary from paraview.org for both client and server) and> I no longer get the error and PV seems work fine in client-server mode.This might or might not be related, but while retestingRelating to the OpenGL context on the server when switching to slice mode:Paulm at s37n2:~/software/ParaView-5.1.0-Qt4-OpenGL2-MPI-Linux-64bit/bin$Connection URL: cs://s37n2.int.elvis.surfsara.nl:11111Accepting connection(s): s37n2.int.elvis.surfsara.nl:11111/home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,VtkXOpenGLRenderWindow (0x30b0eb0): VTK is designed to work with OpenGLVersion 3.2 but it appears it has been given a context that does notSupport 3.2. 5.0.0 shows the same> (running both client and server there) with driver 364.16 and there> it works without a problem. It could be the> driver we use since a few weeks, but like I said, I don't see> 4.4 works without problem in client-server mode (although I can't> seem to get subsampled rendering during interaction working, no> matter what remote render settings I try). A test between my workstation (PV client) and> a different machine (PV server) with driver 352.79 also works.I just tried on a node with an updated nvidia driver (367.27, latest forThe specific model of GPU used) and get the same error on the serverTrying 5.1.0 (binary from paraview.org for both client and server) and INo longer get the error and PV seems work fine in client-server mode.From paul.melis at surfsara.nl Mon Jun 27 11:37:44 2016> ParaView, but something seems to have changed.

5.0.0 shows the same GLX-related issue as 5.0.1.> NVidia driver we use (361.28): I tested 5.0.1 on my workstation (running> both client and server there) with driver 364.16 and there it works without> a problem. We can> 4.4 works without problem in client-server mode (although I can't seem to> get subsampled rendering during interaction working, no matter what remote> render settings I try). Accept the change using OK.Do you get the same segfault? If so, it's independent of what you'reRendering, but just the fact that remote rendering kicks in. From Edit | Settings, Render View tab, set 'Remote RenderThreshold' to 0.

Python /Versions/5/Qtcore (Which Was Built For Mac Os X 10.11)