[Paraview] pvbatch offscreen rendering problems
Good Morning, I am currently having issues with paraview-3.8.0 and paraview-3.9.0 when trying to use pvbatch and offscreen rendering. When I run with my DISPLAY variable set, I don't have any issues, when the DISPLAY variable is not set it fails with the "cannot connect to X server error". I have built paraview with the following flags to support the offscreen rendering capabilities: OPENGL_INCLUDE_DIR OPENGL_gl_LIBRARY OPENGL_glu_LIBRARY OPENGL_xmesa_INCLUDE_DIR OSMESA_INCLUDE_DIR OSMESA_LIBRARY VTK_OPENGL_HAS_OSMESA=ON VTK_USE_OFFSCREEN=ON VTK_USE_DISPLAY=OFF I have built paraview-3.6.2 with these flags and the pvbatch offscreen rendering works perfectly without the DISPLAY variable being set, the same does not work for 3.8.0 and 3.9.0. Am I missing a new flag for these packages? The mesa version I am using is 7.0.4. The pvbatch command I am running is: mpirun -np 4 pvbatch --use-offscreen-rendering testParallelRender.py Thanks in advance for your help, Carrie -- Carrie Spear Software Engineer Lockheed Martin / Army DoD Supercomputing Resource Center Aberdeen Proving Ground, MD 21005 Phone: 410-278-9976 Email: carrie.sp...@us.army.mil ___ 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
Re: [Paraview] pvbatch offscreen rendering problems
That sounds fishy, let me take a look. I'll get back to you. Utkarsh On Wed, Apr 7, 2010 at 8:06 AM, Carrie E. Spear (Cont, CISD/ARL) wrote: > Good Morning, > > I am currently having issues with paraview-3.8.0 and paraview-3.9.0 when > trying to use pvbatch and offscreen rendering. When I run with my DISPLAY > variable set, I don't have any issues, when the DISPLAY variable is not set > it fails with the "cannot connect to X server error". I have built paraview > with the following flags to support the offscreen rendering capabilities: > > OPENGL_INCLUDE_DIR > OPENGL_gl_LIBRARY > OPENGL_glu_LIBRARY > OPENGL_xmesa_INCLUDE_DIR > OSMESA_INCLUDE_DIR > OSMESA_LIBRARY > VTK_OPENGL_HAS_OSMESA=ON > VTK_USE_OFFSCREEN=ON > VTK_USE_DISPLAY=OFF > > I have built paraview-3.6.2 with these flags and the pvbatch offscreen > rendering works perfectly without the DISPLAY variable being set, the same > does not work for 3.8.0 and 3.9.0. Am I missing a new flag for these > packages? The mesa version I am using is 7.0.4. > > The pvbatch command I am running is: > mpirun -np 4 pvbatch --use-offscreen-rendering testParallelRender.py > > Thanks in advance for your help, > Carrie > > -- > Carrie Spear > Software Engineer > Lockheed Martin / Army DoD Supercomputing Resource Center > Aberdeen Proving Ground, MD 21005 > Phone: 410-278-9976 > Email: carrie.sp...@us.army.mil > > ___ > 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
Re: [Paraview] pvbatch offscreen rendering problems
Carrie, I just tried it with CVS ParaView and I could not reproduce it. Can you reproduce this when running on a single node? Try running ldd on pvbatch, is it getting the right OpenGL libraries? Utkarsh On Wed, Apr 7, 2010 at 9:40 AM, Utkarsh Ayachit wrote: > That sounds fishy, let me take a look. I'll get back to you. > > Utkarsh > > On Wed, Apr 7, 2010 at 8:06 AM, Carrie E. Spear (Cont, CISD/ARL) > wrote: >> Good Morning, >> >> I am currently having issues with paraview-3.8.0 and paraview-3.9.0 when >> trying to use pvbatch and offscreen rendering. When I run with my DISPLAY >> variable set, I don't have any issues, when the DISPLAY variable is not set >> it fails with the "cannot connect to X server error". I have built paraview >> with the following flags to support the offscreen rendering capabilities: >> >> OPENGL_INCLUDE_DIR >> OPENGL_gl_LIBRARY >> OPENGL_glu_LIBRARY >> OPENGL_xmesa_INCLUDE_DIR >> OSMESA_INCLUDE_DIR >> OSMESA_LIBRARY >> VTK_OPENGL_HAS_OSMESA=ON >> VTK_USE_OFFSCREEN=ON >> VTK_USE_DISPLAY=OFF >> >> I have built paraview-3.6.2 with these flags and the pvbatch offscreen >> rendering works perfectly without the DISPLAY variable being set, the same >> does not work for 3.8.0 and 3.9.0. Am I missing a new flag for these >> packages? The mesa version I am using is 7.0.4. >> >> The pvbatch command I am running is: >> mpirun -np 4 pvbatch --use-offscreen-rendering testParallelRender.py >> >> Thanks in advance for your help, >> Carrie >> >> -- >> Carrie Spear >> Software Engineer >> Lockheed Martin / Army DoD Supercomputing Resource Center >> Aberdeen Proving Ground, MD 21005 >> Phone: 410-278-9976 >> Email: carrie.sp...@us.army.mil >> >> ___ >> 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
Re: [Paraview] pvbatch offscreen rendering problems
Utkarsh, When I do an ldd pvbatch appears to be using the correct libraries GL libraries (I am building agains mesa-7.0.4, could it be that my version of mesa is too old). I ran the following test: bash-3.2$ echo $DISPLAY :0.0 bash-3.2$ unset DISPLAY bash-3.2$ echo $DISPLAY bash-3.2$ mpirun -np 4 pvbatch --use-offscreen-rendering testParallelRender.py : cannot connect to X server -- mpirun has exited due to process rank 0 with PID 4770 on node ls08270-l.arl.army.mil exiting without calling "finalize". This may have caused other processes in the application to be terminated by signals sent by mpirun (as reported here). -- When I have DISPLAY set it works perfectly. Thanks, Carrie Utkarsh Ayachit wrote: Carrie, I just tried it with CVS ParaView and I could not reproduce it. Can you reproduce this when running on a single node? Try running ldd on pvbatch, is it getting the right OpenGL libraries? Utkarsh On Wed, Apr 7, 2010 at 9:40 AM, Utkarsh Ayachit wrote: That sounds fishy, let me take a look. I'll get back to you. Utkarsh On Wed, Apr 7, 2010 at 8:06 AM, Carrie E. Spear (Cont, CISD/ARL) wrote: Good Morning, I am currently having issues with paraview-3.8.0 and paraview-3.9.0 when trying to use pvbatch and offscreen rendering. When I run with my DISPLAY variable set, I don't have any issues, when the DISPLAY variable is not set it fails with the "cannot connect to X server error". I have built paraview with the following flags to support the offscreen rendering capabilities: OPENGL_INCLUDE_DIR OPENGL_gl_LIBRARY OPENGL_glu_LIBRARY OPENGL_xmesa_INCLUDE_DIR OSMESA_INCLUDE_DIR OSMESA_LIBRARY VTK_OPENGL_HAS_OSMESA=ON VTK_USE_OFFSCREEN=ON VTK_USE_DISPLAY=OFF I have built paraview-3.6.2 with these flags and the pvbatch offscreen rendering works perfectly without the DISPLAY variable being set, the same does not work for 3.8.0 and 3.9.0. Am I missing a new flag for these packages? The mesa version I am using is 7.0.4. The pvbatch command I am running is: mpirun -np 4 pvbatch --use-offscreen-rendering testParallelRender.py Thanks in advance for your help, Carrie -- Carrie Spear Software Engineer Lockheed Martin / Army DoD Supercomputing Resource Center Aberdeen Proving Ground, MD 21005 Phone: 410-278-9976 Email: carrie.sp...@us.army.mil ___ 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 -- Carrie Spear Software Engineer Lockheed Martin / Army DoD Supercomputing Resource Center Aberdeen Proving Ground, MD 21005 Phone: 410-278-9976 Email: carrie.sp...@us.army.mil ___ 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
Re: [Paraview] pvbatch offscreen rendering problems
That's exactly what I am doing as well ("unset DISPLAY" that is), and
seems to work well. Is this a debug build. Can you track down where
the error message is coming from? I am not sure where this error
message is coming from since it doesn't look like a paraview message
and a quick "grep" didn't yield any result. When paraview spews a
display error, it looks something as follows:
Process id: 0 >> ERROR: In
/home/utkarsh/Kitware/ParaView3/ParaView3/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
line 542
vtkXOpenGLRenderWindow (0x3be47e0): bad X server connection.
DISPLAY=Process id: 0 >> ERROR: In
/home/utkarsh/Kitware/ParaView3/ParaView3/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
line 344
vtkXOpenGLRenderWindow (0x3be47e0): bad X server connection. DISPLAY=p0_29057:
Also make sure that OSMESA_INCLUDE_DIR, and OSMESA_LIBRARY are set
correctly. Just for consistency sake, set the following to default
values:
VTK_USE_OFFSCREEN=OFF
VTK_USE_DISPLAY=ON
These need not be changed at all for using OS mesa in ParaView.
Utkarsh
On Wed, Apr 7, 2010 at 1:09 PM, Carrie E. Spear (Cont, CISD/ARL)
wrote:
> Utkarsh,
>
> When I do an ldd pvbatch appears to be using the correct libraries GL
> libraries (I am building agains mesa-7.0.4, could it be that my version of
> mesa is too old). I ran the following test:
>
> bash-3.2$ echo $DISPLAY
> :0.0
> bash-3.2$ unset DISPLAY
> bash-3.2$ echo $DISPLAY
>
> bash-3.2$ mpirun -np 4 pvbatch --use-offscreen-rendering
> testParallelRender.py
> : cannot connect to X server
> --
> mpirun has exited due to process rank 0 with PID 4770 on
> node ls08270-l.arl.army.mil exiting without calling "finalize". This may
> have caused other processes in the application to be
> terminated by signals sent by mpirun (as reported here).
> --
>
> When I have DISPLAY set it works perfectly.
>
> Thanks,
> Carrie
>
> Utkarsh Ayachit wrote:
>>
>> Carrie,
>>
>> I just tried it with CVS ParaView and I could not reproduce it. Can
>> you reproduce this when running on a single node? Try running ldd on
>> pvbatch, is it getting the right OpenGL libraries?
>>
>> Utkarsh
>>
>> On Wed, Apr 7, 2010 at 9:40 AM, Utkarsh Ayachit
>> wrote:
>>
>>>
>>> That sounds fishy, let me take a look. I'll get back to you.
>>>
>>> Utkarsh
>>>
>>> On Wed, Apr 7, 2010 at 8:06 AM, Carrie E. Spear (Cont, CISD/ARL)
>>> wrote:
>>>
Good Morning,
I am currently having issues with paraview-3.8.0 and paraview-3.9.0 when
trying to use pvbatch and offscreen rendering. When I run with my
DISPLAY
variable set, I don't have any issues, when the DISPLAY variable is not
set
it fails with the "cannot connect to X server error". I have built
paraview
with the following flags to support the offscreen rendering
capabilities:
OPENGL_INCLUDE_DIR
OPENGL_gl_LIBRARY
OPENGL_glu_LIBRARY
OPENGL_xmesa_INCLUDE_DIR
OSMESA_INCLUDE_DIR
OSMESA_LIBRARY
VTK_OPENGL_HAS_OSMESA=ON
VTK_USE_OFFSCREEN=ON
VTK_USE_DISPLAY=OFF
I have built paraview-3.6.2 with these flags and the pvbatch offscreen
rendering works perfectly without the DISPLAY variable being set, the
same
does not work for 3.8.0 and 3.9.0. Am I missing a new flag for these
packages? The mesa version I am using is 7.0.4.
The pvbatch command I am running is:
mpirun -np 4 pvbatch --use-offscreen-rendering testParallelRender.py
Thanks in advance for your help,
Carrie
--
Carrie Spear
Software Engineer
Lockheed Martin / Army DoD Supercomputing Resource Center
Aberdeen Proving Ground, MD 21005
Phone: 410-278-9976
Email: carrie.sp...@us.army.mil
___
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
>
>
> --
> Carrie Spear
> Software Engineer
> Lockheed Martin / Army DoD Supercomputing Resource Center
> Aberdeen Proving Ground, MD 21005
> Phone: 410-278-9976
> Email: carrie.sp...@us.army.mil
>
>
___
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
Re: [Paraview] pvbatch offscreen rendering problems
So, we're really stumped.
- Paraview (pvbatch) 3.6.2 works exactly as we'd expect.
- pvbatch 3.8.0/3.9.0 fail with the "can't open display" error. If we
set a display variable, pvbatch works, but that's not really a solution.
- All three are using the same exact Mesa library and use the same
CMakeInit file during the build.
- We've also built by hand (without a CMakeInit file) and get the same
error.
- See the same display error when running pvbatch serially
Not really sure where to turn.
Utkarsh Ayachit wrote:
That's exactly what I am doing as well ("unset DISPLAY" that is), and
seems to work well. Is this a debug build. Can you track down where
the error message is coming from? I am not sure where this error
message is coming from since it doesn't look like a paraview message
and a quick "grep" didn't yield any result. When paraview spews a
display error, it looks something as follows:
Process id: 0 >> ERROR: In
/home/utkarsh/Kitware/ParaView3/ParaView3/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
line 542
vtkXOpenGLRenderWindow (0x3be47e0): bad X server connection.
DISPLAY=Process id: 0 >> ERROR: In
/home/utkarsh/Kitware/ParaView3/ParaView3/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
line 344
vtkXOpenGLRenderWindow (0x3be47e0): bad X server connection. DISPLAY=p0_29057:
Also make sure that OSMESA_INCLUDE_DIR, and OSMESA_LIBRARY are set
correctly. Just for consistency sake, set the following to default
values:
VTK_USE_OFFSCREEN=OFF
VTK_USE_DISPLAY=ON
These need not be changed at all for using OS mesa in ParaView.
Utkarsh
On Wed, Apr 7, 2010 at 1:09 PM, Carrie E. Spear (Cont, CISD/ARL)
wrote:
Utkarsh,
When I do an ldd pvbatch appears to be using the correct libraries GL
libraries (I am building agains mesa-7.0.4, could it be that my version of
mesa is too old). I ran the following test:
bash-3.2$ echo $DISPLAY
:0.0
bash-3.2$ unset DISPLAY
bash-3.2$ echo $DISPLAY
bash-3.2$ mpirun -np 4 pvbatch --use-offscreen-rendering
testParallelRender.py
: cannot connect to X server
--
mpirun has exited due to process rank 0 with PID 4770 on
node ls08270-l.arl.army.mil exiting without calling "finalize". This may
have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).
--
When I have DISPLAY set it works perfectly.
Thanks,
Carrie
Utkarsh Ayachit wrote:
Carrie,
I just tried it with CVS ParaView and I could not reproduce it. Can
you reproduce this when running on a single node? Try running ldd on
pvbatch, is it getting the right OpenGL libraries?
Utkarsh
On Wed, Apr 7, 2010 at 9:40 AM, Utkarsh Ayachit
wrote:
That sounds fishy, let me take a look. I'll get back to you.
Utkarsh
On Wed, Apr 7, 2010 at 8:06 AM, Carrie E. Spear (Cont, CISD/ARL)
wrote:
Good Morning,
I am currently having issues with paraview-3.8.0 and paraview-3.9.0 when
trying to use pvbatch and offscreen rendering. When I run with my
DISPLAY
variable set, I don't have any issues, when the DISPLAY variable is not
set
it fails with the "cannot connect to X server error". I have built
paraview
with the following flags to support the offscreen rendering
capabilities:
OPENGL_INCLUDE_DIR
OPENGL_gl_LIBRARY
OPENGL_glu_LIBRARY
OPENGL_xmesa_INCLUDE_DIR
OSMESA_INCLUDE_DIR
OSMESA_LIBRARY
VTK_OPENGL_HAS_OSMESA=ON
VTK_USE_OFFSCREEN=ON
VTK_USE_DISPLAY=OFF
I have built paraview-3.6.2 with these flags and the pvbatch offscreen
rendering works perfectly without the DISPLAY variable being set, the
same
does not work for 3.8.0 and 3.9.0. Am I missing a new flag for these
packages? The mesa version I am using is 7.0.4.
The pvbatch command I am running is:
mpirun -np 4 pvbatch --use-offscreen-rendering testParallelRender.py
Thanks in advance for your help,
Carrie
--
Carrie Spear
Software Engineer
Lockheed Martin / Army DoD Supercomputing Resource Center
Aberdeen Proving Ground, MD 21005
Phone: 410-278-9976
Email: carrie.sp...@us.army.mil
___
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
--
Carrie Spear
Software Engineer
Lockheed Martin / Army DoD Supercomputing Resource Center
Aberdeen Proving Ground, MD 21005
Phone: 410-278-9976
Email: carrie.sp...@us.army.mil
___
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/m
Re: [Paraview] pvbatch offscreen rendering problems
I was writing a response when it struck me, are you building with
PARAVIEW_BUILD_QT_GUI ON? That's possible the only difference between
your build and mine. I am going to turn on PARAVIEW_BUILD_QT_GUI and
try to reproduce the problem.
Utkarsh
On Wed, Apr 7, 2010 at 2:06 PM, Rick Angelini wrote:
> So, we're really stumped.
>
> - Paraview (pvbatch) 3.6.2 works exactly as we'd expect.
> - pvbatch 3.8.0/3.9.0 fail with the "can't open display" error. If we set a
> display variable, pvbatch works, but that's not really a solution.
> - All three are using the same exact Mesa library and use the same CMakeInit
> file during the build. - We've also built by hand (without a CMakeInit
> file) and get the same error.
> - See the same display error when running pvbatch serially
>
> Not really sure where to turn.
>
> Utkarsh Ayachit wrote:
>>
>> That's exactly what I am doing as well ("unset DISPLAY" that is), and
>> seems to work well. Is this a debug build. Can you track down where
>> the error message is coming from? I am not sure where this error
>> message is coming from since it doesn't look like a paraview message
>> and a quick "grep" didn't yield any result. When paraview spews a
>> display error, it looks something as follows:
>>
>> Process id: 0 >> ERROR: In
>>
>> /home/utkarsh/Kitware/ParaView3/ParaView3/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
>> line 542
>> vtkXOpenGLRenderWindow (0x3be47e0): bad X server connection.
>> DISPLAY=Process id: 0 >> ERROR: In
>>
>> /home/utkarsh/Kitware/ParaView3/ParaView3/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
>> line 344
>> vtkXOpenGLRenderWindow (0x3be47e0): bad X server connection.
>> DISPLAY=p0_29057:
>>
>> Also make sure that OSMESA_INCLUDE_DIR, and OSMESA_LIBRARY are set
>> correctly. Just for consistency sake, set the following to default
>> values:
>> VTK_USE_OFFSCREEN=OFF
>> VTK_USE_DISPLAY=ON
>>
>> These need not be changed at all for using OS mesa in ParaView.
>>
>> Utkarsh
>>
>>
>> On Wed, Apr 7, 2010 at 1:09 PM, Carrie E. Spear (Cont, CISD/ARL)
>> wrote:
>>
>>>
>>> Utkarsh,
>>>
>>> When I do an ldd pvbatch appears to be using the correct libraries GL
>>> libraries (I am building agains mesa-7.0.4, could it be that my version
>>> of
>>> mesa is too old). I ran the following test:
>>>
>>> bash-3.2$ echo $DISPLAY
>>> :0.0
>>> bash-3.2$ unset DISPLAY
>>> bash-3.2$ echo $DISPLAY
>>>
>>> bash-3.2$ mpirun -np 4 pvbatch --use-offscreen-rendering
>>> testParallelRender.py
>>> : cannot connect to X server
>>>
>>> --
>>> mpirun has exited due to process rank 0 with PID 4770 on
>>> node ls08270-l.arl.army.mil exiting without calling "finalize". This may
>>> have caused other processes in the application to be
>>> terminated by signals sent by mpirun (as reported here).
>>>
>>> --
>>>
>>> When I have DISPLAY set it works perfectly.
>>>
>>> Thanks,
>>> Carrie
>>>
>>> Utkarsh Ayachit wrote:
>>>
Carrie,
I just tried it with CVS ParaView and I could not reproduce it. Can
you reproduce this when running on a single node? Try running ldd on
pvbatch, is it getting the right OpenGL libraries?
Utkarsh
On Wed, Apr 7, 2010 at 9:40 AM, Utkarsh Ayachit
wrote:
>
> That sounds fishy, let me take a look. I'll get back to you.
>
> Utkarsh
>
> On Wed, Apr 7, 2010 at 8:06 AM, Carrie E. Spear (Cont, CISD/ARL)
> wrote:
>
>
>>
>> Good Morning,
>>
>> I am currently having issues with paraview-3.8.0 and paraview-3.9.0
>> when
>> trying to use pvbatch and offscreen rendering. When I run with my
>> DISPLAY
>> variable set, I don't have any issues, when the DISPLAY variable is
>> not
>> set
>> it fails with the "cannot connect to X server error". I have built
>> paraview
>> with the following flags to support the offscreen rendering
>> capabilities:
>>
>> OPENGL_INCLUDE_DIR
>> OPENGL_gl_LIBRARY
>> OPENGL_glu_LIBRARY
>> OPENGL_xmesa_INCLUDE_DIR
>> OSMESA_INCLUDE_DIR
>> OSMESA_LIBRARY
>> VTK_OPENGL_HAS_OSMESA=ON
>> VTK_USE_OFFSCREEN=ON
>> VTK_USE_DISPLAY=OFF
>>
>> I have built paraview-3.6.2 with these flags and the pvbatch offscreen
>> rendering works perfectly without the DISPLAY variable being set, the
>> same
>> does not work for 3.8.0 and 3.9.0. Am I missing a new flag for these
>> packages? The mesa version I am using is 7.0.4.
>>
>> The pvbatch command I am running is:
>> mpirun -np 4 pvbatch --use-offscreen-rendering testParallelRender.py
>>
>> Thanks in advance for your help,
>> Carrie
>>
>> --
>> Carrie Spear
>> Software Engineer
>> Lockheed Martin / Army DoD Supercomputing Resource Center
>> Aberdeen Proving Ground, MD 21005
>> Phone: 410-278-9976
>> Email: carr
Re: [Paraview] pvbatch offscreen rendering problems
Rick/ Carrie,
My paraview is still building and will be a while before I can try
this out. But attached is a patch that I think will solve this issue.
Can you try it out?
Thanks
Utkarsh
On Wed, Apr 7, 2010 at 2:15 PM, Utkarsh Ayachit
wrote:
> I was writing a response when it struck me, are you building with
> PARAVIEW_BUILD_QT_GUI ON? That's possible the only difference between
> your build and mine. I am going to turn on PARAVIEW_BUILD_QT_GUI and
> try to reproduce the problem.
>
> Utkarsh
>
>
>
>
>
> On Wed, Apr 7, 2010 at 2:06 PM, Rick Angelini
> wrote:
>> So, we're really stumped.
>>
>> - Paraview (pvbatch) 3.6.2 works exactly as we'd expect.
>> - pvbatch 3.8.0/3.9.0 fail with the "can't open display" error. If we set a
>> display variable, pvbatch works, but that's not really a solution.
>> - All three are using the same exact Mesa library and use the same CMakeInit
>> file during the build. - We've also built by hand (without a CMakeInit
>> file) and get the same error.
>> - See the same display error when running pvbatch serially
>>
>> Not really sure where to turn.
>>
>> Utkarsh Ayachit wrote:
>>>
>>> That's exactly what I am doing as well ("unset DISPLAY" that is), and
>>> seems to work well. Is this a debug build. Can you track down where
>>> the error message is coming from? I am not sure where this error
>>> message is coming from since it doesn't look like a paraview message
>>> and a quick "grep" didn't yield any result. When paraview spews a
>>> display error, it looks something as follows:
>>>
>>> Process id: 0 >> ERROR: In
>>>
>>> /home/utkarsh/Kitware/ParaView3/ParaView3/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
>>> line 542
>>> vtkXOpenGLRenderWindow (0x3be47e0): bad X server connection.
>>> DISPLAY=Process id: 0 >> ERROR: In
>>>
>>> /home/utkarsh/Kitware/ParaView3/ParaView3/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
>>> line 344
>>> vtkXOpenGLRenderWindow (0x3be47e0): bad X server connection.
>>> DISPLAY=p0_29057:
>>>
>>> Also make sure that OSMESA_INCLUDE_DIR, and OSMESA_LIBRARY are set
>>> correctly. Just for consistency sake, set the following to default
>>> values:
>>> VTK_USE_OFFSCREEN=OFF
>>> VTK_USE_DISPLAY=ON
>>>
>>> These need not be changed at all for using OS mesa in ParaView.
>>>
>>> Utkarsh
>>>
>>>
>>> On Wed, Apr 7, 2010 at 1:09 PM, Carrie E. Spear (Cont, CISD/ARL)
>>> wrote:
>>>
Utkarsh,
When I do an ldd pvbatch appears to be using the correct libraries GL
libraries (I am building agains mesa-7.0.4, could it be that my version
of
mesa is too old). I ran the following test:
bash-3.2$ echo $DISPLAY
:0.0
bash-3.2$ unset DISPLAY
bash-3.2$ echo $DISPLAY
bash-3.2$ mpirun -np 4 pvbatch --use-offscreen-rendering
testParallelRender.py
: cannot connect to X server
--
mpirun has exited due to process rank 0 with PID 4770 on
node ls08270-l.arl.army.mil exiting without calling "finalize". This may
have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).
--
When I have DISPLAY set it works perfectly.
Thanks,
Carrie
Utkarsh Ayachit wrote:
>
> Carrie,
>
> I just tried it with CVS ParaView and I could not reproduce it. Can
> you reproduce this when running on a single node? Try running ldd on
> pvbatch, is it getting the right OpenGL libraries?
>
> Utkarsh
>
> On Wed, Apr 7, 2010 at 9:40 AM, Utkarsh Ayachit
> wrote:
>
>
>>
>> That sounds fishy, let me take a look. I'll get back to you.
>>
>> Utkarsh
>>
>> On Wed, Apr 7, 2010 at 8:06 AM, Carrie E. Spear (Cont, CISD/ARL)
>> wrote:
>>
>>
>>>
>>> Good Morning,
>>>
>>> I am currently having issues with paraview-3.8.0 and paraview-3.9.0
>>> when
>>> trying to use pvbatch and offscreen rendering. When I run with my
>>> DISPLAY
>>> variable set, I don't have any issues, when the DISPLAY variable is
>>> not
>>> set
>>> it fails with the "cannot connect to X server error". I have built
>>> paraview
>>> with the following flags to support the offscreen rendering
>>> capabilities:
>>>
>>> OPENGL_INCLUDE_DIR
>>> OPENGL_gl_LIBRARY
>>> OPENGL_glu_LIBRARY
>>> OPENGL_xmesa_INCLUDE_DIR
>>> OSMESA_INCLUDE_DIR
>>> OSMESA_LIBRARY
>>> VTK_OPENGL_HAS_OSMESA=ON
>>> VTK_USE_OFFSCREEN=ON
>>> VTK_USE_DISPLAY=OFF
>>>
>>> I have built paraview-3.6.2 with these flags and the pvbatch offscreen
>>> rendering works perfectly without the DISPLAY variable being set, the
>>> same
>>> does not work for 3.8.0 and 3.9.0. Am I missing a new flag for these
>>> packages? The mesa version I am using is 7.0.4.
>>
Re: [Paraview] pvbatch offscreen rendering problems
Looks like the patch should resolve this issue. I've committed it to
CVS. Let me know if that doesn't work. We'll commit it to 3.8 branch
soon.
Utkarsh
On Wed, Apr 7, 2010 at 2:20 PM, Utkarsh Ayachit
wrote:
> Rick/ Carrie,
>
> My paraview is still building and will be a while before I can try
> this out. But attached is a patch that I think will solve this issue.
> Can you try it out?
>
> Thanks
> Utkarsh
>
> On Wed, Apr 7, 2010 at 2:15 PM, Utkarsh Ayachit
> wrote:
>> I was writing a response when it struck me, are you building with
>> PARAVIEW_BUILD_QT_GUI ON? That's possible the only difference between
>> your build and mine. I am going to turn on PARAVIEW_BUILD_QT_GUI and
>> try to reproduce the problem.
>>
>> Utkarsh
>>
>>
>>
>>
>>
>> On Wed, Apr 7, 2010 at 2:06 PM, Rick Angelini
>> wrote:
>>> So, we're really stumped.
>>>
>>> - Paraview (pvbatch) 3.6.2 works exactly as we'd expect.
>>> - pvbatch 3.8.0/3.9.0 fail with the "can't open display" error. If we set a
>>> display variable, pvbatch works, but that's not really a solution.
>>> - All three are using the same exact Mesa library and use the same CMakeInit
>>> file during the build. - We've also built by hand (without a CMakeInit
>>> file) and get the same error.
>>> - See the same display error when running pvbatch serially
>>>
>>> Not really sure where to turn.
>>>
>>> Utkarsh Ayachit wrote:
That's exactly what I am doing as well ("unset DISPLAY" that is), and
seems to work well. Is this a debug build. Can you track down where
the error message is coming from? I am not sure where this error
message is coming from since it doesn't look like a paraview message
and a quick "grep" didn't yield any result. When paraview spews a
display error, it looks something as follows:
Process id: 0 >> ERROR: In
/home/utkarsh/Kitware/ParaView3/ParaView3/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
line 542
vtkXOpenGLRenderWindow (0x3be47e0): bad X server connection.
DISPLAY=Process id: 0 >> ERROR: In
/home/utkarsh/Kitware/ParaView3/ParaView3/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
line 344
vtkXOpenGLRenderWindow (0x3be47e0): bad X server connection.
DISPLAY=p0_29057:
Also make sure that OSMESA_INCLUDE_DIR, and OSMESA_LIBRARY are set
correctly. Just for consistency sake, set the following to default
values:
VTK_USE_OFFSCREEN=OFF
VTK_USE_DISPLAY=ON
These need not be changed at all for using OS mesa in ParaView.
Utkarsh
On Wed, Apr 7, 2010 at 1:09 PM, Carrie E. Spear (Cont, CISD/ARL)
wrote:
>
> Utkarsh,
>
> When I do an ldd pvbatch appears to be using the correct libraries GL
> libraries (I am building agains mesa-7.0.4, could it be that my version
> of
> mesa is too old). I ran the following test:
>
> bash-3.2$ echo $DISPLAY
> :0.0
> bash-3.2$ unset DISPLAY
> bash-3.2$ echo $DISPLAY
>
> bash-3.2$ mpirun -np 4 pvbatch --use-offscreen-rendering
> testParallelRender.py
> : cannot connect to X server
>
> --
> mpirun has exited due to process rank 0 with PID 4770 on
> node ls08270-l.arl.army.mil exiting without calling "finalize". This may
> have caused other processes in the application to be
> terminated by signals sent by mpirun (as reported here).
>
> --
>
> When I have DISPLAY set it works perfectly.
>
> Thanks,
> Carrie
>
> Utkarsh Ayachit wrote:
>
>>
>> Carrie,
>>
>> I just tried it with CVS ParaView and I could not reproduce it. Can
>> you reproduce this when running on a single node? Try running ldd on
>> pvbatch, is it getting the right OpenGL libraries?
>>
>> Utkarsh
>>
>> On Wed, Apr 7, 2010 at 9:40 AM, Utkarsh Ayachit
>> wrote:
>>
>>
>>>
>>> That sounds fishy, let me take a look. I'll get back to you.
>>>
>>> Utkarsh
>>>
>>> On Wed, Apr 7, 2010 at 8:06 AM, Carrie E. Spear (Cont, CISD/ARL)
>>> wrote:
>>>
>>>
Good Morning,
I am currently having issues with paraview-3.8.0 and paraview-3.9.0
when
trying to use pvbatch and offscreen rendering. When I run with my
DISPLAY
variable set, I don't have any issues, when the DISPLAY variable is
not
set
it fails with the "cannot connect to X server error". I have built
paraview
with the following flags to support the offscreen rendering
capabilities:
OPENGL_INCLUDE_DIR
OPENGL_gl_LIBRARY
OPENGL_glu_LIBRARY
OPENGL_xmesa_INCLUDE_DIR
OSMESA_INCLUDE_DIR
OSMESA_LIBRARY
VTK_OPENGL_HAS_OSMESA=ON
Re: [Paraview] pvbatch offscreen rendering problems
It is now in the branch as well.
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMChartViewProxy.cxx,v
<-- Servers/ServerManager/vtkSMChartViewProxy.cxx
new revision: 1.8.2.1; previous revision: 1.8
On Wed, Apr 7, 2010 at 2:43 PM, Utkarsh Ayachit wrote:
> Looks like the patch should resolve this issue. I've committed it to
> CVS. Let me know if that doesn't work. We'll commit it to 3.8 branch
> soon.
>
> Utkarsh
>
> On Wed, Apr 7, 2010 at 2:20 PM, Utkarsh Ayachit
> wrote:
> > Rick/ Carrie,
> >
> > My paraview is still building and will be a while before I can try
> > this out. But attached is a patch that I think will solve this issue.
> > Can you try it out?
> >
> > Thanks
> > Utkarsh
> >
> > On Wed, Apr 7, 2010 at 2:15 PM, Utkarsh Ayachit
> > wrote:
> >> I was writing a response when it struck me, are you building with
> >> PARAVIEW_BUILD_QT_GUI ON? That's possible the only difference between
> >> your build and mine. I am going to turn on PARAVIEW_BUILD_QT_GUI and
> >> try to reproduce the problem.
> >>
> >> Utkarsh
> >>
> >>
> >>
> >>
> >>
> >> On Wed, Apr 7, 2010 at 2:06 PM, Rick Angelini <
> rick.angel...@us.army.mil> wrote:
> >>> So, we're really stumped.
> >>>
> >>> - Paraview (pvbatch) 3.6.2 works exactly as we'd expect.
> >>> - pvbatch 3.8.0/3.9.0 fail with the "can't open display" error. If we
> set a
> >>> display variable, pvbatch works, but that's not really a solution.
> >>> - All three are using the same exact Mesa library and use the same
> CMakeInit
> >>> file during the build. - We've also built by hand (without a CMakeInit
> >>> file) and get the same error.
> >>> - See the same display error when running pvbatch serially
> >>>
> >>> Not really sure where to turn.
> >>>
> >>> Utkarsh Ayachit wrote:
>
> That's exactly what I am doing as well ("unset DISPLAY" that is), and
> seems to work well. Is this a debug build. Can you track down where
> the error message is coming from? I am not sure where this error
> message is coming from since it doesn't look like a paraview message
> and a quick "grep" didn't yield any result. When paraview spews a
> display error, it looks something as follows:
>
> Process id: 0 >> ERROR: In
>
>
> /home/utkarsh/Kitware/ParaView3/ParaView3/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
> line 542
> vtkXOpenGLRenderWindow (0x3be47e0): bad X server connection.
> DISPLAY=Process id: 0 >> ERROR: In
>
>
> /home/utkarsh/Kitware/ParaView3/ParaView3/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
> line 344
> vtkXOpenGLRenderWindow (0x3be47e0): bad X server connection.
> DISPLAY=p0_29057:
>
> Also make sure that OSMESA_INCLUDE_DIR, and OSMESA_LIBRARY are set
> correctly. Just for consistency sake, set the following to default
> values:
> VTK_USE_OFFSCREEN=OFF
> VTK_USE_DISPLAY=ON
>
> These need not be changed at all for using OS mesa in ParaView.
>
> Utkarsh
>
>
> On Wed, Apr 7, 2010 at 1:09 PM, Carrie E. Spear (Cont, CISD/ARL)
> wrote:
>
> >
> > Utkarsh,
> >
> > When I do an ldd pvbatch appears to be using the correct libraries GL
> > libraries (I am building agains mesa-7.0.4, could it be that my
> version
> > of
> > mesa is too old). I ran the following test:
> >
> > bash-3.2$ echo $DISPLAY
> > :0.0
> > bash-3.2$ unset DISPLAY
> > bash-3.2$ echo $DISPLAY
> >
> > bash-3.2$ mpirun -np 4 pvbatch --use-offscreen-rendering
> > testParallelRender.py
> > : cannot connect to X server
> >
> >
> --
> > mpirun has exited due to process rank 0 with PID 4770 on
> > node ls08270-l.arl.army.mil exiting without calling "finalize". This
> may
> > have caused other processes in the application to be
> > terminated by signals sent by mpirun (as reported here).
> >
> >
> --
> >
> > When I have DISPLAY set it works perfectly.
> >
> > Thanks,
> > Carrie
> >
> > Utkarsh Ayachit wrote:
> >
> >>
> >> Carrie,
> >>
> >> I just tried it with CVS ParaView and I could not reproduce it. Can
> >> you reproduce this when running on a single node? Try running ldd on
> >> pvbatch, is it getting the right OpenGL libraries?
> >>
> >> Utkarsh
> >>
> >> On Wed, Apr 7, 2010 at 9:40 AM, Utkarsh Ayachit
> >> wrote:
> >>
> >>
> >>>
> >>> That sounds fishy, let me take a look. I'll get back to you.
> >>>
> >>> Utkarsh
> >>>
> >>> On Wed, Apr 7, 2010 at 8:06 AM, Carrie E. Spear (Cont, CISD/ARL)
> >>> wrote:
> >>>
> >>>
>
> Good Morning,
>
> I am currently having issues with paraview-3.8.0 and
> paraview-3.9.0
> when
> trying t
Re: [Paraview] pvbatch offscreen rendering problems
The patch seems to have resolved the issue related to the DISPLAY
variable. Thanks!
Utkarsh Ayachit wrote:
Looks like the patch should resolve this issue. I've committed it to
CVS. Let me know if that doesn't work. We'll commit it to 3.8 branch
soon.
Utkarsh
On Wed, Apr 7, 2010 at 2:20 PM, Utkarsh Ayachit
wrote:
Rick/ Carrie,
My paraview is still building and will be a while before I can try
this out. But attached is a patch that I think will solve this issue.
Can you try it out?
Thanks
Utkarsh
On Wed, Apr 7, 2010 at 2:15 PM, Utkarsh Ayachit
wrote:
I was writing a response when it struck me, are you building with
PARAVIEW_BUILD_QT_GUI ON? That's possible the only difference between
your build and mine. I am going to turn on PARAVIEW_BUILD_QT_GUI and
try to reproduce the problem.
Utkarsh
On Wed, Apr 7, 2010 at 2:06 PM, Rick Angelini wrote:
So, we're really stumped.
- Paraview (pvbatch) 3.6.2 works exactly as we'd expect.
- pvbatch 3.8.0/3.9.0 fail with the "can't open display" error. If we set a
display variable, pvbatch works, but that's not really a solution.
- All three are using the same exact Mesa library and use the same CMakeInit
file during the build. - We've also built by hand (without a CMakeInit
file) and get the same error.
- See the same display error when running pvbatch serially
Not really sure where to turn.
Utkarsh Ayachit wrote:
That's exactly what I am doing as well ("unset DISPLAY" that is), and
seems to work well. Is this a debug build. Can you track down where
the error message is coming from? I am not sure where this error
message is coming from since it doesn't look like a paraview message
and a quick "grep" didn't yield any result. When paraview spews a
display error, it looks something as follows:
Process id: 0 >> ERROR: In
/home/utkarsh/Kitware/ParaView3/ParaView3/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
line 542
vtkXOpenGLRenderWindow (0x3be47e0): bad X server connection.
DISPLAY=Process id: 0 >> ERROR: In
/home/utkarsh/Kitware/ParaView3/ParaView3/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
line 344
vtkXOpenGLRenderWindow (0x3be47e0): bad X server connection.
DISPLAY=p0_29057:
Also make sure that OSMESA_INCLUDE_DIR, and OSMESA_LIBRARY are set
correctly. Just for consistency sake, set the following to default
values:
VTK_USE_OFFSCREEN=OFF
VTK_USE_DISPLAY=ON
These need not be changed at all for using OS mesa in ParaView.
Utkarsh
On Wed, Apr 7, 2010 at 1:09 PM, Carrie E. Spear (Cont, CISD/ARL)
wrote:
Utkarsh,
When I do an ldd pvbatch appears to be using the correct libraries GL
libraries (I am building agains mesa-7.0.4, could it be that my version
of
mesa is too old). I ran the following test:
bash-3.2$ echo $DISPLAY
:0.0
bash-3.2$ unset DISPLAY
bash-3.2$ echo $DISPLAY
bash-3.2$ mpirun -np 4 pvbatch --use-offscreen-rendering
testParallelRender.py
: cannot connect to X server
--
mpirun has exited due to process rank 0 with PID 4770 on
node ls08270-l.arl.army.mil exiting without calling "finalize". This may
have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).
--
When I have DISPLAY set it works perfectly.
Thanks,
Carrie
Utkarsh Ayachit wrote:
Carrie,
I just tried it with CVS ParaView and I could not reproduce it. Can
you reproduce this when running on a single node? Try running ldd on
pvbatch, is it getting the right OpenGL libraries?
Utkarsh
On Wed, Apr 7, 2010 at 9:40 AM, Utkarsh Ayachit
wrote:
That sounds fishy, let me take a look. I'll get back to you.
Utkarsh
On Wed, Apr 7, 2010 at 8:06 AM, Carrie E. Spear (Cont, CISD/ARL)
wrote:
Good Morning,
I am currently having issues with paraview-3.8.0 and paraview-3.9.0
when
trying to use pvbatch and offscreen rendering. When I run with my
DISPLAY
variable set, I don't have any issues, when the DISPLAY variable is
not
set
it fails with the "cannot connect to X server error". I have built
paraview
with the following flags to support the offscreen rendering
capabilities:
OPENGL_INCLUDE_DIR
OPENGL_gl_LIBRARY
OPENGL_glu_LIBRARY
OPENGL_xmesa_INCLUDE_DIR
OSMESA_INCLUDE_DIR
OSMESA_LIBRARY
VTK_OPENGL_HAS_OSMESA=ON
VTK_USE_OFFSCREEN=ON
VTK_USE_DISPLAY=OFF
I have built paraview-3.6.2 with these flags and the pvbatch offscreen
rendering works perfectly without the DISPLAY variable being set, the
same
does not work for 3.8.0 and 3.9.0. Am I missing a new flag for these
packages? The mesa version I am using is 7.0.4.
The pvbatch command I am running is:
mpirun -np 4 pvbatch --use-offscreen-rendering testParallelRender.py
Thanks in advance for your help,
Carrie
--
Carrie Spear
Software Engineer
Lockheed Martin / Army DoD Supercomputing Resource Center
Aberdeen Proving Ground, MD 21005
Phone: 410-278-9976
Ema
