[Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Yep - we built the HPC-side with “OpenGL2” … so does that mean that the
pre-built Mac/Linux binaries were both built with OpenGL?    Is there some
way to check to see which OpenGL the client was built with?

________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Date: Friday, May 27, 2016 at 2:24 PM
To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
Cc: ParaView <paraview at paraview.org>
Subject: [Non-DoD Source] Re: [Paraview] 5.0.1/Exodus Reader

All active links contained in this email were disabled.  Please verify the
identity of the sender, and confirm the authenticity of all links
contained within the message prior to copying and pasting the address to a
Web browser.  




----

Rick,

I must admit this was a major "oops" in 5.0.0 and 5.0.1 releases. We
should have handled this better and I will make sure we do for 5.1.
Basically, what you have is a mismatch in rendering configurations for
client and server. One of them is build with VTK_RENDERING_BACKEND set
to OpenGL and other to OpenGL2. You need them to match.

Utkarsh

On Fri, May 27, 2016 at 2:08 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> We’re seeing an issue with the Exodus reader in version 5.0.1.      We
>can
> read any particular Exodus dataset when running ParaView 5.0.1 locally –
> read the data on the same machine where the client is running.   However,
> when we try to load any of the Exodus datasets in client-server mode,
> ParaView 5.0.1 immediately crashes.    Crash happens when the client is
>run
> on either a Mac or Linux workstation.
>
>
> Accepting connection(s): my_Mac:52994
> ERROR: In
> 
>/Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_o
>sx10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerImple
>mentation/Core/vtkSIProxy.cxx,
> line 310
> vtkSIProxy (0x7fdebaa2f0f0): Failed to create vtkHAVSVolumeMapper.
>Aborting
> for debugging purposes.
>
>
> Accepting connection(s): my_Linux:35227
> ERROR: In
> 
>/usr/people/angel/PV/5.0.1/Build_5.0.1_gl/paraview/src/paraview/ParaViewCo
>re/ServerImplementation/Core/vtkSIProxy.cxx,
> line 310
> vtkSIProxy (0x7768340): Failed to create vtkHAVSVolumeMapper. Aborting
>for
> debugging purposes.
>
> This same dataset works in client-server mode using ParaView 4.3.1.
> We seem to be able to load up other data types using ParaView 5.0.1 – so
> far, it *appears* that only Exodus files are failing.
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
> _______________________________________________
> Powered by Caution-www.kitware.com
>
> Visit other Kitware open-source projects at
> Caution-http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-http://paraview.org/Wiki/ParaView
>
> Search the list archives at:
>Caution-http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> Caution-http://public.kitware.com/mailman/listinfo/paraview
>