[Paraview] Why is pvbatch displaying images?
Pradeep Jha
pradeep at ccs.engg.nagoya-u.ac.jp
Wed Mar 6 09:30:21 EST 2013
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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20130306/f80db91c/attachment-0001.htm>
More information about the ParaView
mailing list