[Paraview] Paraview Catalyst offscreen rendering

[Lukáš Kresta]

it was build with easybuild with these parametrs:

cmake /apps/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay/ParaView-v5.4.0/

-DCMAKE_INSTALL_PREFIX=/apps/all/ParaView/5.4.0-intel-2017a-mpi-OSPRay

-DCMAKE_C_COMPILER='mpiicc' -DCMAKE_Fortran_FLAGS='-O2 -xHost -ftz
-fp-speculation=safe -fp-model source -fPIC'

-DCMAKE_CXX_FLAGS='-O2 -xHost -ftz -fp-speculation=safe -fp-model
source -fPIC' -DCMAKE_CXX_COMPILER='mpiicpc'

DCMAKE_Fortran_COMPILER='mpiifort' -DCMAKE_C_FLAGS='-O2 -xHost -ftz
-fp-speculation=safe -fp-model source -fPIC'

-DCMAKE_VERBOSE_MAKEFILE=ON -DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON
-DVTK_OPENGL_HAS_OSMESA=ON

-DPARAVIEW_USE_MPI=ON -DOPENGL_INCLUDE_DIR=$EBROOTMESA/include
-DOPENGL_gl_LIBRARY=$EBROOTMESA/lib/libGL.so

-DOSMESA_INCLUDE_DIR=$EBROOTMESA/include
-DOSMESA_LIBRARY=$EBROOTMESA/lib/libOSMesa.so

-DOPENGL_glu_LIBRARY=$EBROOTLIBGLU/lib/libGLU.so
-DVTK_USE_SYSTEM_HDF5=ON -DPARAVIEW_ENABLE_PYTHON=ON
-DBUILD_SHARED_LIBS=ON

-DVTK_RENDERING_BACKEND=OpenGL2 -DPARAVIEW_USE_OSPRAY=ON
-DOSPRAY_INSTALL_DIR=$EBROOT
 OSPRAY -DPARAVIEW_QT_VERSION=5 -DBUILD_TESTING=OFF


I hope, it will help solve my problem. If you need, i can send you complete log.


2017-07-26 17:37 GMT+02:00 Andy Bauer <andy.bauer at kitware.com>:

> Hi,
>
> It sounds like you didn't properly build with OSMesa. If you share your
> CMakeCache.txt from your ParaView build I can see if I can track down the
> problem.
>
> Best,
> Andy
>
> On Wed, Jul 26, 2017 at 11:20 AM, Lukáš Kresta <lukas.kresta at gmail.com>
> wrote:
>
>> Thank you, but I have ParaView build with OSMesa without X. If I run
>> program with Catalyst(genereted script from ParaView, with render views) on
>> cluster with mpi, ussually one render view will show, but on anothers
>> process it crash with this error: ERROR: In .../ParaView-v5.4.0/VTK/Render
>> ing/OpenGL2/vtkOpenGLRenderWindow.cxx, line 819
>> vtkXOpenGLRenderWindow (0x3f7cbf0): GLEW could not be initialized. I have
>> the same error with pvserver with or without --use-offscreen-rendering or
>> without pvserver.
>>
>> If i run Catalyst with script only for live visualization then the
>> program go without problem but i dont get pictures which i want. Is there
>> some posibility how fix the error or how to get pictures(with offscreen
>> rendering)?
>>
>> 2017-07-14 16:24 GMT+02:00 Andy Bauer <andy.bauer at kitware.com>:
>>
>>> Hi,
>>>
>>> If you're not memory constrained I suggest just doing a full ParaView
>>> build with OSMesa and X11 disabled. There are quite a few discussions on
>>> the PV mailing list on how to do that.
>>>
>>> If you're memory constrained then I would suggest building with all of
>>> the Catalyst editions enabled and see if that works for you.
>>>
>>> Best,
>>> Andy
>>>
>>> On Fri, Jul 14, 2017 at 3:31 AM, Lukáš Kresta <lukas.kresta at gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I would like to ask, which Paraview Catalyst (python) script use(with
>>>> render view or live visualization). If i want save images with offscreen
>>>> rendering on HPC.  On cluster is no gpu. And how to properly use it?
>>>>
>>>> Thank you for your help.
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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/20170727/ac073609/attachment.html>