[Paraview] Catalyst osMesa rendering time

Fri Sep 16 13:10:40 EDT 2016

Hi Andy,

Thank you for all of the guidance that you have provided for compiling the osMesa version of ParaView. I think there must be a gap in my understanding that is causing me to implement/interpret your instructions incorrectly. My goal is to be able to run a code that makes calls to the Catalyst adaptor in order to generate .png output images of a domain for each timestep. The nodes that the code runs on do not have graphics cards, so I’m looking for a way to have the VTK library generate the images without resorting to calls to a GPU for rendering. That is what the ParaView build with osMesa is supposed to do right? It seems exceedingly difficult to get ParaView to compile osMesa, because even though I instruct the cmake configuration to use Mesa, it seems to disregard my request and continue to run by opening windows for generating the images. I don’t get compiler errors, so I suppose it just tosses out the osMesa stuff and compiles in the default way?

I apologize for the verbose post. I feel like Bill Murray in Groundhog Day in that I keep making changes to try to get ParaView to operate with osMesa, and I always end up back where I started with ParaView creating windows and causing my code to crash. I’m trying the superbuild, but that is currently failing to compile for reasons that I haven’t quite been able to figure out.

-Chris

From: Andy Bauer <andy.bauer at kitware.com>
Date: Monday, September 12, 2016 at 3:20 PM
To: Christopher Neal <chrisneal at snumerics.com>
Cc: Benson Muite via ParaView <paraview at paraview.org>
Subject: Re: [Paraview] Catalyst osMesa rendering time

I think the missing item is that you need to set VTK_USE_OFFSCREEN to ON.

On Mon, Sep 12, 2016 at 3:00 PM, Christopher Neal <chrisneal at snumerics.com> wrote:

Thanks Andy,

The file is quite large, so I have attached it.

I tried to follow the process that is explained at(http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D) so I made a shell script that contains all of the arguments passed to cmake. It is shown below.

#!/bin/bash

cmake \

  -DCMAKE_SOURCE_DIR:PATH=/home/neal/software/ParaView_osMesa/Source \

  -DCMAKE_INSTALL_PREFIX:PATH=/home/neal/software/ParaView_osMesa/build \

  -DCMAKE_BUILD_TYPE:STRING=Release \

  -DCMAKE_SKIP_INSTALL_RPATH:BOOL=YES \

  -DBUILD_TESTING:BOOL=OFF \

  -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \

  -DVTK_RENDERING_BACKEND=OpenGL2 \

  -DPARAVIEW_USE_MPI:BOOL=ON \

  -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \

  -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON \

  -DPARAVIEW_BUILD_CATALYST_ADAPTERS:BOOL=ON \

  -DPARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_ArrowGlyph:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_CDIReader:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_EyeDomeLighting:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_GMVReader:BOOL=FALSE \

 -DPARAVIEW_BUILD_PLUGIN_GeodesicMeasurement:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_H5PartReader:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_InSituExodus:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_MantaView:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_Moments:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_NonOrthogonalSource:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_PacMan:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_PointSprite:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_RGBZView:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=FALSE \

 -DPARAVIEW_BUILD_PLUGIN_SciberQuestToolKit:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_SierraPlotTools:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_StreamingParticles:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_UncertaintyRendering:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_AcceleratedAlgorithms:BOOL=OFF \

  -DVTK_USE_CXX11_FEATURES:BOOL=ON \

  -DVTK_USE_X:BOOL=OFF \

  -DOPENGL_INCLUDE_DIR:PATH=/home/neal/software/Mesa/build/include \

  -DOPENGL_gl_LIBRARY:PATH=/home/neal/software/Mesa/build/lib64/libOSMesa.so \

  -DOPENGL_glu_LIBRARY:PATH=/home/neal/software/Mesa/build/lib64/libGLU.so \

  -DVTK_OPENGL_HAS_OSMESA:BOOL=ON \

  -DOSMESA_INCLUDE_DIR:PATH=/home/neal/software/Mesa/build/include \

  -DOSMESA_LIBRARY:PATH=/home/neal/software/Mesa/build/lib64/libOSMesa.so  /home/neal/software/ParaView_osMesa/Source

make -j20

#make -j20 install

-Chris

From: Andy Bauer <andy.bauer at kitware.com>
Date: Monday, September 12, 2016 at 2:39 PM
To: Christopher Neal <chrisneal at snumerics.com>
Cc: Benson Muite via ParaView <paraview at paraview.org>
Subject: Re: [Paraview] Catalyst osMesa rendering time

Hi Chris,

It sounds like you didn't properly build ParaView with offscreen rendering. Can  you share your CMakeCache.txt from your build? I'm guessing VTK_USE_X, VTK_USE_OFFSCREEN or some other thing didn't get set properly.

Andy

On Mon, Sep 12, 2016 at 1:36 PM, Christopher Neal <chrisneal at snumerics.com> wrote:

Hi all,

I have compiled a version of ParaView with osMesa enabled. The version is 5.1.2 for ParaView. I’m running the CxxFullExample Catalyst example that is located in ParaView/Examples/Catalyst.

Operating system info

lsb_release –a: 
LSB Version:         n/a

Distributor ID:     openSUSE project

Description:         openSUSE 13.2 (Harlequin) (x86_64)

Release:                13.2

Codename:           Harlequin

I have added 1 additional script to the Catalyst example by using the “CoProcessing” button in ParaView to generate a Catalyst script that just exports a .png of an isometric view of the geometry. When I run the example, the operating system seems to freeze up completely in my login session i.e. windows can not be clicked, nothing at all can be done with the exception of moving the mouse around on the screen. It stays frozen like this for about 2 minutes before a window pops up that says “Paraview(batch)”. In the window is the isometric view and the window updates to show the geometry at every timestep that the example outputs an image at. The Catalyst script does seem to execute fine and outputs image files for each frame that I requested, but it is soooo slow for some reason.

Is this the expected behavior of running Catalyst with an osMesa build? I thought that ‘os’ stood for ‘off-screen’, which I interpreted as there being no screen display component to the rendering. Have I done something wrong with compiling ParaView with osMesa? Is Catalyst supposed to completely lock up the session until a window pops up?  

I would love to hear from other users of Catalyst to hear about the experiences of running Catalyst.

Thank you,

Chris Neal

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160916/0b522dbd/attachment.html>