[Paraview] Why is pvbatch displaying images?
Pradeep Jha
pradeep at ccs.engg.nagoya-u.ac.jp
Thu Mar 14 02:17:50 EDT 2013
ok, I managed to get it working. I had to build in a new directory. Thanks
again for all your help.
2013/3/8 Patrick Begou <Patrick.Begou at hmg.inpg.fr>
> This libGLU.so.1file is provided by Mesa-7.11.2. I've build OSMesa only
> for pvserver so I set the same install prefix for building OSMesa and for
> building Paraview to put all the files together in
> /share/apps/paraView-server-3.98.1 subdirectory.
> May be, look where you install your builded OSMesa libraries.
>
> It is important for me to put all files together as this file system is
> exported on my cluster nodes: later I want to run pvserver in parallel on
> these nodes for visualization of very large datasets.
>
> Patrick
>
>
> Pradeep Jha wrote:
>
> But I dont see any such files in my paraview directory.
>
>
> 2013/3/7 Patrick Begou <Patrick.Begou at hmg.inpg.fr>
>
>> I'm not using system libGLU but the one provided by OSMesa when I build
>> this library. Look at the TAG:
>>
>> OPENGL_glu_LIBRARY = /share/apps/paraView-server-3.98.1/lib/libGLU.so
>>
>> when building paraview. Did you try this one ?
>> Patrick
>>
>>
>> Pradeep Jha wrote:
>>
>> Thanks Patrick and David. I set everything as you guys said except one
>> thing. I could not find the libGLU.so on the computer. When I did:
>> ---------------------------------------------------------------
>> [k00603 at fe01p09 ~]$locate libGLU
>> /usr/lib/libGLU.so.1
>> /usr/lib/libGLU.so.1.3.060501
>> /usr/lib64/libGLU.so.1
>> /usr/lib64/libGLU.so.1.3.060501
>> ----------------------------------------------------
>> so I set the "OPENGL_glu_LIBRARY" environment to
>> "/usr/lib64/libGLU.so.1". After this when I run the "make" command, I am
>> getting the following error:
>>
>> --------------------------------------------------------------------------------------------------------
>> [ 87%] Built target vtkRenderingMatplotlibCS
>> [ 88%] Built target vtkPVServerManagerRenderingCS
>> [ 89%] Built target vtkRenderingLODCS
>> [ 90%] Built target vtkPVServerManagerDefaultCS
>> Linking CXX shared library ../../../lib/
>> libvtkPVServerManagerApplication-pv3.98.so
>> CMakeFiles/vtkPVServerManagerApplication.dir/vtkInitializationHelper.cxx.o:
>> In function `PARAVIEW_CSSTREAMS_INITIALIZE(vtkClientServerInterpreter*)':
>> vtkInitializationHelper.cxx:(.text+0x355): undefined reference to
>> `vtkFiltersParallelMPICS_Initialize'
>> collect2: ld returned 1 exit status
>> make[2]: *** [lib/libvtkPVServerManagerApplication-pv3.98.so.1] Error 1
>> make[1]: ***
>> [ParaViewCore/ServerManager/SMApplication/CMakeFiles/vtkPVServerManagerApplication.dir/all]
>> Error 2
>> make: *** [all] Error 2
>> ----------------------------------------------------
>> ----------------------------------------------------
>>
>> Any ideas what am I doing wrong?
>>
>>
>>
>> 2013/3/7 Patrick Begou <Patrick.Begou at hmg.inpg.fr>
>>
>>> May be my (very) short experience with pvserver and OSMesa can help...
>>> I've just build a config without any error messages.
>>> I've downloaded Mesa-7.11.2 and ParaView-3.98.1 sources. (see
>>> "[Paraview] Using paraview with pvserver" thread on this list)
>>>
>>> 1) build of Mesa-7.11.2 with:
>>> ./configure --with-driver=osmesa --prefix=/share/apps/paraView-server-3.98.1
>>> make
>>> make install
>>>
>>> 2) build paraview with:
>>> mkdir ParaView-3.98.1-build
>>> cd ParaView-3.98.1-build
>>> ccmake28 -D PARAVIEW_BUILD_QT_GUI:BOOL=OFF -D VTK_USE_X:BOOL=OFF -D
>>> VTK_OPENGL_HAS_OSMESA:BOOL=ON /home/makerpm/PARAVIEW/ParaView-3.98.1-source
>>>
>>> and set
>>> PARAVIEW_BUILD_QT_GUI = OFF
>>> OPENGL_INCLUDE_DIR = /share/apps/paraView-server-3.98.1/include
>>> OPENGL_gl_LIBRARY =
>>> OPENGL_glu_LIBRARY = /share/apps/paraView-server-3.98.1/lib/libGLU.so
>>> VTK_OPENGL_HAS_OSMESA = ON
>>> OSMESA_INCLUDE_DIR = /share/apps/paraView-server-3.98.1/include
>>> OSMESA_LIBRARY = /share/apps/paraView-server-3.98.1/lib/libOSMesa.so
>>> VTK_USE_X = OFF
>>> PARAVIEW_USE_MPI=ON
>>>
>>> make
>>> make install
>>>
>>> It is important to set OPENGL_gl_LIBRARY empty.
>>>
>>> Patrick
>>>
>>>
>>> Pradeep Jha wrote:
>>>
>>> just wondering, when I was making OSMesa, it gave me the following
>>> message during "configure":
>>>
>>>
>>> ------------------------------------------------------------------------------------------------------------
>>> Project MESSAGE: Disabling video due the lack of GLib/Gio/GStreamer
>>>
>>> ------------------------------------------------------------------------------------------------------------
>>>
>>> is it ok? Or do I need to do something about it?
>>>
>>>
>>> 2013/3/6 David E DeMarle <dave.demarle at kitware.com>
>>>
>>>> See the cmake config settings for pure offscreen rendering
>>>> configuration of pvserver in:
>>>>
>>>> http://paraview.org/Wiki/ParaView/Users_Guide/Parallel_Rendering#Offscreen_Software_Rendering_via_OSMesa
>>>>
>>>> David E DeMarle
>>>> Kitware, Inc.
>>>> R&D Engineer
>>>> 21 Corporate Drive
>>>> Clifton Park, NY 12065-8662
>>>> Phone: 518-881-4909
>>>>
>>>>
>>>> On Wed, Mar 6, 2013 at 12:40 AM, Pradeep Jha <
>>>> pradeep at ccs.engg.nagoya-u.ac.jp> wrote:
>>>>
>>>>> I installed PV with OSMesa on a linux supercomputer. When I am
>>>>> running "pvbatch --use-offscreen-rendering script_file.py", I get the
>>>>> following error:
>>>>>
>>>>> ------------------------------------------------------------------------------------------------------------------------
>>>>> [fe02s01:15756] *** Process received signal ***
>>>>> [fe02s01:15756] Signal: Segmentation fault (11)
>>>>> [fe02s01:15756] Signal code: (128)
>>>>> [fe02s01:15756] Failing at address: (nil)
>>>>> [fe02s01:15756] [ 0] /lib64/libpthread.so.0 [0x357320eca0]
>>>>> [fe02s01:15756] [ 1]
>>>>> /home/hp120242/k00603/local/HH-1298/usr/lib64/libGL.so.1(glGetString+0xe)
>>>>> [0x2b747e417cee]
>>>>> [fe02s01:15756] *** End of error message ***
>>>>> Segmentation fault (core dumped)
>>>>>
>>>>> ------------------------------------------------------------------------------------------------------------------------
>>>>> What is going wrong? Is there any problem with the installation of
>>>>> my Paraview with OSMesa support? This pvbatch works fine without
>>>>> --use-offscreen-rendering option when I "ssh" with the "-X" option.
>>>>>
>>>>> Thank you,
>>>>> Pradeep
>>>>>
>>>>>
>>>>> 2013/1/31 Andy Bauer <andy.bauer at kitware.com>
>>>>>
>>>>>> Yes, you don't need OSMesa when there is graphics hardware support.
>>>>>> In that case though it will still pop up a render window to create screen
>>>>>> shots. OSMesa can still be used even if you have graphics hardware support
>>>>>> and is currently the only way to get around having a window to render into.
>>>>>>
>>>>>>
>>>>>> On Wed, Jan 30, 2013 at 9:09 AM, Pradeep Jha <
>>>>>> pradeep at ccs.engg.nagoya-u.ac.jp> wrote:
>>>>>>
>>>>>>> From the online resources I gathered that we need OSMesa only when
>>>>>>> there is no graphics hardware on the system. Ok, so I guess I need to
>>>>>>> install OSMesa and then compile Paraview again with OSMesa support?
>>>>>>>
>>>>>>> Please confirm.
>>>>>>>
>>>>>>>
>>>>>>> 2013/1/30 Andy Bauer <andy.bauer at kitware.com>
>>>>>>>
>>>>>>>> Hi Pradeep,
>>>>>>>>
>>>>>>>> If you don't want the window to pop up you'll need to use offscreen
>>>>>>>> rendering with OSMesa. WriteAnimation() needs to create a window in order
>>>>>>>> to generate the image. It is the same with WriteImage().
>>>>>>>>
>>>>>>>> Andy
>>>>>>>>
>>>>>>>> On Wed, Jan 30, 2013 at 3:33 AM, Pradeep Jha <
>>>>>>>> pradeep at ccs.engg.nagoya-u.ac.jp> wrote:
>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> I made my first PV python script using "Start Trace" and "End
>>>>>>>>> Trace". Now I am trying to run this script using pvbatch hoping it will
>>>>>>>>> execute everything on the command line and not display any graphics. I
>>>>>>>>> deleted the Render() statement which was at the end of the python script
>>>>>>>>> generated by Trace (file attached with this email). But still it keeps
>>>>>>>>> generating the image window and fails when I ssh without X option.
>>>>>>>>>
>>>>>>>>> I have attached the script file. I am executing pvbatch by the
>>>>>>>>> command
>>>>>>>>>
>>>>>>>>> $pvbatch export_movie.py
>>>>>>>>>
>>>>>>>>> Why is this happening?
>>>>>>>>>
>>>>>>>>> Thank you,
>>>>>>>>> Pradeep
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>> Follow this link to subscribe/unsubscribe:
>>>>>>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>>>
>>>>>>>> Follow this link to subscribe/unsubscribe:
>>>>>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>> Follow this link to subscribe/unsubscribe:
>>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>>>
>>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>> Follow this link to subscribe/unsubscribe:http://www.paraview.org/mailman/listinfo/paraview
>>>
>>>
>>>
>>> --
>>> ===============================================================
>>> | Equipe M.O.S.T. | http://most.hmg.inpg.fr |
>>> | Patrick BEGOU | ------------ |
>>> | LEGI | mailto:Patrick.Begou at hmg.inpg.fr <Patrick.Begou at hmg.inpg.fr> |
>>> | BP 53 X | Tel 04 76 82 51 35 |
>>> | 38041 GRENOBLE CEDEX | Fax 04 76 82 52 71 |
>>> ===============================================================
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
>>>
>>
>>
>> --
>> ===============================================================
>> | Equipe M.O.S.T. | http://most.hmg.inpg.fr |
>> | Patrick BEGOU | ------------ |
>> | LEGI | mailto:Patrick.Begou at hmg.inpg.fr <Patrick.Begou at hmg.inpg.fr> |
>> | BP 53 X | Tel 04 76 82 51 35 |
>> | 38041 GRENOBLE CEDEX | Fax 04 76 82 52 71 |
>> ===============================================================
>>
>>
>
>
> --
> ===============================================================
> | Equipe M.O.S.T. | http://most.hmg.inpg.fr |
> | Patrick BEGOU | ------------ |
> | LEGI | mailto:Patrick.Begou at hmg.inpg.fr <Patrick.Begou at hmg.inpg.fr> |
> | BP 53 X | Tel 04 76 82 51 35 |
> | 38041 GRENOBLE CEDEX | Fax 04 76 82 52 71 |
> ===============================================================
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20130314/c0e2a2c9/attachment-0001.htm>
More information about the ParaView
mailing list