Re: [Paraview] vtkHashSource-pv5.1 binary disappearing during ParaView 'make install'

I tried it again with cmake 3.5.1 and I see the same error. -- Up-to-date: /home/neal/software/ParaView5.2/build/lib/cmake/paraview-5.1/Modules/vtkUtilitiesHashSource.cmake CMake Error at VTK/Utilities/HashSource/cmake_install.cmake:46 (file): file INSTALL cannot find

Re: [Paraview] vtkHashSource-pv5.1 binary disappearing during ParaView 'make install'

For the case outlined in this email chain, it is the ParaView source. I’m currently using Paraview5.2.  I have also had the same trouble with: Catalyst-v5.1.0-Base-Enable-Python-Essentials, with the symbolic link ad-hoc solution working with this case as well. From: Andy Bauer

Re: [Paraview] vtkHashSource-pv5.1 binary disappearing during ParaView 'make install'

Hi Chris, Are you trying to build from a Catalyst edition or directly from the full ParaView source? I want to make sure that we're going in the proper direction when trying to fix this problem. Thanks, Andy On Fri, Aug 5, 2016 at 1:15 PM, Utkarsh Ayachit wrote:

Re: [Paraview] vtkHashSource-pv5.1 binary disappearing during ParaView 'make install'

Ben, Can you take a look please? Thanks. On Fri, Aug 5, 2016 at 1:03 PM, Christopher Neal wrote: > I tried it again with cmake 3.5.1 and I see the same error. > > -- Up-to-date: >

[Paraview] Cannot access information from second input array in a XML custom filter

Hey all, I'm trying to create a custom filter (using vtkPythonProgrammableFilter) that allows the user to specify two input arrays (the XML file is attached). As a guide, I mimicked the XML specifications for the Glyphs filter in the filters.xml file. The filter appears as it should, but I

Re: [Paraview] vtkHashSource-pv5.1 binary disappearing during ParaView 'make install'

Thank you Utkarsh, I will try cmake 3.5.1 to see if that has any effect on the issue that I’m having. Output from: cmake –version cmake version 3.6.20160722-g8842a Output from: lsb_relase –a LSB Version:n/a Distributor ID: openSUSE project Description:openSUSE 13.2 (Harlequin)

Re: [Paraview] Slicing a sphere based on longitudes and latitudes

Lester, This is pretty straightforward problem in geometry. As I give you the answer, I am assuming that your sphere is centered at the origin (as you said), the axis that runs through the north/south pole is along the Z axis, and the prime meridian (0 degrees longitude) is in the positive X

Re: [Paraview] Depth rendering issues on ParaView Desktop 5.1.0

Thank you David, soon I have access to my workstation I'll try the other versions and report the results here. -Júlio ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please

[Paraview] Slicing a sphere based on longitudes and latitudes

Hello, Quick query, but is there an easy way to slice a spherical Earth model based on longitude and latitude while keeping the origin at the centre? What I am looking to do is slice along a fixed longitude or latitude, e.g. Longitude slice at 150 degrees; Latitude slice at -30 degrees. Based

Re: [Paraview] Depth rendering issues on ParaView Desktop 5.1.0

The only other thing I can think of is that it might be an issue with the new depth peeling code, which is used to blend layers of translucent geometry. However, from the look of the screenshots, it appears that all of the geometry is opaque, in which case depth peeling wouldn't be used. Still,

Re: [Paraview] Depth rendering issues on ParaView Desktop 5.1.0

Thank you David, I tried with Mesa and the result is the same. I'm gonna try the newer release, but I suspect it won't solve the issue. Any information that I can export and that can help figure out the root of the problem? -Júlio ___ Powered by

Re: [Paraview] Depth rendering issues on ParaView Desktop 5.1.0

That is very odd. I use arch linux as well and don't see this here. I'm suspecting a graphics driver issue at this point. Try running paraview with the "--mesa-llvm" command line argument and see if it fares better. That will force paraview to use a software-based OpenGL implementation and bypass