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

Tue Jun 7 11:22:36 EDT 2016

Utkarsh - I was able to get a clean build with this OSMesa patch - but it
looks like the OSMesa pvserver is not compatible with the production 5.0.1
client??????

ERROR: In 
/usr/people/angel/PV/5.0.1/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Par
allel/Core/vtkSocketCommunicator.cxx, line 558
vtkSocketCommunicator (0x12324f0): Endian handshake failed.

ERROR: In 
/usr/people/angel/PV/5.0.1/Build_5.0.1_osmesa/paraview/src/paraview/ParaVie
wCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx, line 33
0
vtkTCPNetworkAccessManager (0x6612b0): Failed to connect to
excalibur03-int:22886

ERROR: In 
/usr/people/angel/PV/5.0.1/Build_5.0.1_osmesa/paraview/src/paraview/ParaVie
wCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx, line 34
0
vtkTCPNetworkAccessManager (0x6612b0):
**********************************************************************
Connection failed during handshake. This can happen for the following
reasons:
 1. Connection dropped during the handshake.
 2. vtkSocketCommunicator::GetVersion() returns different values on the
    two connecting processes (Current value: 100).
 3. ParaView handshake strings are different on the two connecting
    processes (Current value: paraview.5.0.connect_id.9407).
**********************************************************************

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

-----Original Message-----
From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Date: Monday, June 6, 2016 at 1:53 PM
To: "Hennessey, Joseph G CTR USARMY RDECOM ARL (US)"
<joseph.g.hennessey2.ctr at mail.mil>
Cc: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>, Simon Su
<simon.m.su.CIV at mail.mil>, ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
(UNCLASSIFIED)

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.  

----

Here's a MR for update superbuild that builds OSMesa 11.2.2. I've only
updated OSMesa. I'll tackle mesa-glx next.

Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/merge_reque
sts/114

Utkarsh

On Mon, Jun 6, 2016 at 12:31 PM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> I am working on updating superbuild today. Just hold on. I'll email
> once I have it working.
>
> On Mon, Jun 6, 2016 at 12:00 PM, Hennessey, Joseph G CTR USARMY RDECOM
> ARL (US) <joseph.g.hennessey2.ctr at mail.mil> wrote:
>> CLASSIFICATION: UNCLASSIFIED
>>
>> Utkarsh,
>>
>> I have rebuilt osmesa using mesa 11.2.2 but
>> it ParaView rebuilt with the new version is giving
>> me the same error as before, complaining that the
>> GL version 2.1 with gpu_shader4 extension is not
>> Supported.
>>
>> I think I know  why  this is occurring and I wondered if you
>> could confirm this for me.
>>
>> I configured mesa with these parameters
>>
>> ./configure \
>>     --disable-xvmc \
>>     --disable-glx \
>>     --disable-dri \
>>     --with-dri-drivers= \
>>     --with-gallium-drivers=swrast \
>>     --enable-texture-float \
>>     --disable-egl \
>>     --with-egl-platforms= \
>>     --enable-gallium-osmesa \
>>     --enable-gallium-llvm=yes \
>>     --prefix=<install prefix>
>>
>> but, I did not have a version of llvm available
>> and the configure script then set
>>
>> Llvm = no
>>
>> From my reading of this webpage
>>
>> Caution-http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D
>>
>> It seems that without gallium-llvm,
>> the version of OpenGL built reverts to an older version,
>> which I believe is why I am still getting the error.
>>
>> Would you agree with this?
>>
>> Thanks,
>>
>> Joe
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Joseph G. Hennessey Ph.D., Lockheed Martin
>> Army Research Lab
>> DOD Supercomputing Resource Center
>>
>>
>> -----Original Message-----
>> From: Utkarsh Ayachit [Caution-mailto:utkarsh.ayachit at kitware.com]
>> Sent: Thursday, June 02, 2016 4:19 PM
>> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
>> <joseph.g.hennessey2.ctr at mail.mil>
>> Cc: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
>> <richard.c.angelini.civ at mail.mil>; Su, Simon M CIV USARMY RDECOM ARL
>>(US)
>> <simon.m.su.civ at mail.mil>; ParaView <paraview at paraview.org>
>> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>> (UNCLASSIFIED)
>>
>> 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.
>>
>>
>>
>>
>> ----
>>
>>> And I have tried replacing the library
>>> lib/paraview-5.0/libOSMesa.so.7
>>> with both libOSMesa.so from 11.1.2 and 11.2.2 and they are both still
>>> giving the same error
>>
>> Simply swapping the libraries won't work. Mesa 11.2 [1] added new API
>> OSMesaCreateContextAttribs() which is needed to create correct OpenGL
>>context.
>> The API is used at compile time if appropriate osmesa.h is being used.
>>
>> You can try to update Projects/unix/osmesa.cmake in the superbuild
>>source to
>> use the configure arguments you used, and also change versions.cmake in
>>the
>> same repo to point to change the osmesa source tar ball to be 11.2. Now
>>the
>> superbuid will build 11.2 instead and it should then have the new API
>> available.
>>
>> [1] Caution-Caution-http://www.mesa3d.org/relnotes/11.2.0.html
>>
>>
>> CLASSIFICATION: UNCLASSIFIED