Re: [Paraview] pvserver segfault
On Wed, Jun 10, 2015 at 1:13 PM, Jeff Becker jeffrey.c.bec...@nasa.gov wrote: I'm assuming the file gets read on the first one, and it splits up the grid among all the servers? It is up to the specific reader class to decide what to do so who exactly reads what depends on the file type. If the data is not well distributed, apply the D3 filter to make paraview repartition the read in data amongst the processors. David E DeMarle Kitware, Inc. RD Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 ___ 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
Re: [Paraview] pvserver segfault
On 06/10/2015 10:16 AM, David E DeMarle wrote: On Wed, Jun 10, 2015 at 1:13 PM, Jeff Becker jeffrey.c.bec...@nasa.gov mailto:jeffrey.c.bec...@nasa.gov wrote: I'm assuming the file gets read on the first one, and it splits up the grid among all the servers? It is up to the specific reader class to decide what to do so who exactly reads what depends on the file type. If the data is not well distributed, apply the D3 filter to make paraview repartition the read in data amongst the processors. I did the following to start a single pvserver on each of two hosts: $ mpirun r219i0n0,r219i0n1 -np 1 /usr/bin/env DISPLAY=:0 /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver --client-host=pfe20 --use-offscreen-rendering After I connected to the first pvserver, and opened the file, I tried to apply the D3 filter, but it was grayed out. -jeff David E DeMarle Kitware, Inc. RD Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 ___ 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
Re: [Paraview] pvserver segfault
mpirun r219i0n0,r219i0n1 -np 1… should be mpirun r219i0n0,r219i0n1 -np 2... no? David E DeMarle Kitware, Inc. RD Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Jun 10, 2015 at 1:34 PM, David E DeMarle dave.dema...@kitware.com wrote: In general a greyed out filter means that one of its input preconditions is not satisfied. In this case D3 needs more than 1 rank, but if the input was a structured data set instead of an unstructured one then that would disable it too. In windows and linux there should be text in the bottom left of the app that explains when you mouse over a disabled filter. Otherwise you have to look at the help for the filter in question and figure it out. David E DeMarle Kitware, Inc. RD Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Jun 10, 2015 at 1:30 PM, Utkarsh Ayachit utkarsh.ayac...@kitware.com wrote: Jeff, D3 is available only when there's more than 1 MPI rank. There's no need to do any load balancing with just 1 rank. Utkarsh On Wed, Jun 10, 2015 at 1:29 PM Jeff Becker jeffrey.c.bec...@nasa.gov wrote: On 06/10/2015 10:16 AM, David E DeMarle wrote: On Wed, Jun 10, 2015 at 1:13 PM, Jeff Becker jeffrey.c.bec...@nasa.gov wrote: I'm assuming the file gets read on the first one, and it splits up the grid among all the servers? It is up to the specific reader class to decide what to do so who exactly reads what depends on the file type. If the data is not well distributed, apply the D3 filter to make paraview repartition the read in data amongst the processors. I did the following to start a single pvserver on each of two hosts: $ mpirun r219i0n0,r219i0n1 -np 1 /usr/bin/env DISPLAY=:0 /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver --client-host=pfe20 --use-offscreen-rendering After I connected to the first pvserver, and opened the file, I tried to apply the D3 filter, but it was grayed out. -jeff David E DeMarle Kitware, Inc. RD Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 ___ 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
Re: [Paraview] pvserver segfault
In general a greyed out filter means that one of its input preconditions is not satisfied. In this case D3 needs more than 1 rank, but if the input was a structured data set instead of an unstructured one then that would disable it too. In windows and linux there should be text in the bottom left of the app that explains when you mouse over a disabled filter. Otherwise you have to look at the help for the filter in question and figure it out. David E DeMarle Kitware, Inc. RD Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Jun 10, 2015 at 1:30 PM, Utkarsh Ayachit utkarsh.ayac...@kitware.com wrote: Jeff, D3 is available only when there's more than 1 MPI rank. There's no need to do any load balancing with just 1 rank. Utkarsh On Wed, Jun 10, 2015 at 1:29 PM Jeff Becker jeffrey.c.bec...@nasa.gov wrote: On 06/10/2015 10:16 AM, David E DeMarle wrote: On Wed, Jun 10, 2015 at 1:13 PM, Jeff Becker jeffrey.c.bec...@nasa.gov wrote: I'm assuming the file gets read on the first one, and it splits up the grid among all the servers? It is up to the specific reader class to decide what to do so who exactly reads what depends on the file type. If the data is not well distributed, apply the D3 filter to make paraview repartition the read in data amongst the processors. I did the following to start a single pvserver on each of two hosts: $ mpirun r219i0n0,r219i0n1 -np 1 /usr/bin/env DISPLAY=:0 /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver --client-host=pfe20 --use-offscreen-rendering After I connected to the first pvserver, and opened the file, I tried to apply the D3 filter, but it was grayed out. -jeff David E DeMarle Kitware, Inc. RD Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 ___ 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
Re: [Paraview] pvserver segfault
Jeff, D3 is available only when there's more than 1 MPI rank. There's no need to do any load balancing with just 1 rank. Utkarsh On Wed, Jun 10, 2015 at 1:29 PM Jeff Becker jeffrey.c.bec...@nasa.gov wrote: On 06/10/2015 10:16 AM, David E DeMarle wrote: On Wed, Jun 10, 2015 at 1:13 PM, Jeff Becker jeffrey.c.bec...@nasa.gov wrote: I'm assuming the file gets read on the first one, and it splits up the grid among all the servers? It is up to the specific reader class to decide what to do so who exactly reads what depends on the file type. If the data is not well distributed, apply the D3 filter to make paraview repartition the read in data amongst the processors. I did the following to start a single pvserver on each of two hosts: $ mpirun r219i0n0,r219i0n1 -np 1 /usr/bin/env DISPLAY=:0 /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver --client-host=pfe20 --use-offscreen-rendering After I connected to the first pvserver, and opened the file, I tried to apply the D3 filter, but it was grayed out. -jeff David E DeMarle Kitware, Inc. RD Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 ___ 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
Re: [Paraview] pvserver segfault
On 06/09/2015 06:54 PM, Utkarsh Ayachit wrote: Can you try turning off Display Lists? It's an option under the Settings (Render View tab) dialog. You'll need to restart ParaView after making this change. I suspect the graphics driver is giving up while building a large display list. Display lists will be a thing of the past once we update the rendering backend in the next release of ParaView, FYI. That works. Now, I'll try running several pvservers (each on a different GPU node) in hopes of speeding up interactivity. I'm assuming the file gets read on the first one, and it splits up the grid among all the servers? Thanks. -jeff Utkarsh On Tue, Jun 9, 2015 at 8:23 PM Jeff Becker jeffrey.c.bec...@nasa.gov mailto:jeffrey.c.bec...@nasa.gov wrote: Hi. I'm running pvserver on a GPU server, and a client on my desktop. After starting X on the server, I'm running pvserver as follows, and then connect to it from the client $ mpirun -np 1 /usr/bin/env DISPLAY=:0 /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver --client-host=pfe20 --use-offscreen-rendering Waiting for client... Connection URL: cs://r219i0n0:1 Accepting connection(s): r219i0n0:1 Client connected. I open a 1.6GB unstructured (.vtu) grid file, and hit apply. After the file is read, and some time passes, I get SIGSEGV and I see the following backtrace in gdb. Please advise on what's wrong, and how to fix. Thanks. -jeff (gdb) bt #0 0x2aaab0bb92a8 in memcpy () from /lib64/libc.so.6 #1 0x2aaac3128a70 in ?? () from /usr/lib64/libnvidia-glcore.so.340.65 #2 0x2aaac327e2a1 in ?? () from /usr/lib64/libnvidia-glcore.so.340.65 #3 0x2aaac328006e in ?? () from /usr/lib64/libnvidia-glcore.so.340.65 #4 0x2aaaba0e4197 in vtkOpenGLDisplayListPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #5 0x2aaaba0e06a1 in vtkOpenGLClipPlanesPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #6 0x2aaaba122e2a in vtkOpenGLScalarsToColorsPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #7 0x2aaaba12fdb4 in vtkPainterPolyDataMapper::RenderPiece(vtkRenderer*, vtkActor*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #8 0x2c4ad93f in vtkPolyDataMapper::Render(vtkRenderer*, vtkActor*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #9 0x2aaaba0dcd08 in vtkOpenGLActor::Render(vtkRenderer*, vtkMapper*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #10 0x2aaab4f1630b in vtkPVLODActor::Render(vtkRenderer*, vtkMapper*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 #11 0x2aaab4f16157 in vtkPVLODActor::RenderOpaqueGeometry(vtkViewport*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 #12 0x2c4b9464 in vtkRenderer::UpdateGeometry() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #13 0x2aaab4f0a751 in vtkPVDefaultPass::Render(vtkRenderState const*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 #14 0x2aaaba0ae35b in vtkCameraPass::Render(vtkRenderState const*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #15 0x2aaaba1206c0 in vtkOpenGLRenderer::DeviceRender() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #16 0x2c4bb18d in vtkRenderer::Render() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #17 0x2c4b8429 in vtkRendererCollection::Render() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #18 0x2c4c2202 in vtkRenderWindow::DoStereoRender() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #19 0x2c4c2119 in vtkRenderWindow::DoFDRender() () from
Re: [Paraview] pvserver segfault
On 06/10/2015 10:30 AM, Utkarsh Ayachit wrote: Jeff, D3 is available only when there's more than 1 MPI rank. There's no need to do any load balancing with just 1 rank. But I'm using 1 rank on each of two nodes (r219i0n0,r219i0n1) -jeff Utkarsh On Wed, Jun 10, 2015 at 1:29 PM Jeff Becker jeffrey.c.bec...@nasa.gov mailto:jeffrey.c.bec...@nasa.gov wrote: On 06/10/2015 10:16 AM, David E DeMarle wrote: On Wed, Jun 10, 2015 at 1:13 PM, Jeff Becker jeffrey.c.bec...@nasa.gov mailto:jeffrey.c.bec...@nasa.gov wrote: I'm assuming the file gets read on the first one, and it splits up the grid among all the servers? It is up to the specific reader class to decide what to do so who exactly reads what depends on the file type. If the data is not well distributed, apply the D3 filter to make paraview repartition the read in data amongst the processors. I did the following to start a single pvserver on each of two hosts: $ mpirun r219i0n0,r219i0n1 -np 1 /usr/bin/env DISPLAY=:0 /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver --client-host=pfe20 --use-offscreen-rendering After I connected to the first pvserver, and opened the file, I tried to apply the D3 filter, but it was grayed out. -jeff David E DeMarle Kitware, Inc. RD Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 ___ 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
Re: [Paraview] pvserver segfault
Can you try turning off Display Lists? It's an option under the Settings (Render View tab) dialog. You'll need to restart ParaView after making this change. I suspect the graphics driver is giving up while building a large display list. Display lists will be a thing of the past once we update the rendering backend in the next release of ParaView, FYI. Utkarsh On Tue, Jun 9, 2015 at 8:23 PM Jeff Becker jeffrey.c.bec...@nasa.gov wrote: Hi. I'm running pvserver on a GPU server, and a client on my desktop. After starting X on the server, I'm running pvserver as follows, and then connect to it from the client $ mpirun -np 1 /usr/bin/env DISPLAY=:0 /u/jcbecker/ParaView-4.3.1-Linux-64bit/bin/pvserver --client-host=pfe20 --use-offscreen-rendering Waiting for client... Connection URL: cs://r219i0n0:1 Accepting connection(s): r219i0n0:1 Client connected. I open a 1.6GB unstructured (.vtu) grid file, and hit apply. After the file is read, and some time passes, I get SIGSEGV and I see the following backtrace in gdb. Please advise on what's wrong, and how to fix. Thanks. -jeff (gdb) bt #0 0x2aaab0bb92a8 in memcpy () from /lib64/libc.so.6 #1 0x2aaac3128a70 in ?? () from /usr/lib64/libnvidia-glcore.so.340.65 #2 0x2aaac327e2a1 in ?? () from /usr/lib64/libnvidia-glcore.so.340.65 #3 0x2aaac328006e in ?? () from /usr/lib64/libnvidia-glcore.so.340.65 #4 0x2aaaba0e4197 in vtkOpenGLDisplayListPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #5 0x2aaaba0e06a1 in vtkOpenGLClipPlanesPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #6 0x2aaaba122e2a in vtkOpenGLScalarsToColorsPainter::RenderInternal(vtkRenderer*, vtkActor*, unsigned long, bool) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #7 0x2aaaba12fdb4 in vtkPainterPolyDataMapper::RenderPiece(vtkRenderer*, vtkActor*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #8 0x2c4ad93f in vtkPolyDataMapper::Render(vtkRenderer*, vtkActor*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #9 0x2aaaba0dcd08 in vtkOpenGLActor::Render(vtkRenderer*, vtkMapper*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #10 0x2aaab4f1630b in vtkPVLODActor::Render(vtkRenderer*, vtkMapper*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 #11 0x2aaab4f16157 in vtkPVLODActor::RenderOpaqueGeometry(vtkViewport*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 #12 0x2c4b9464 in vtkRenderer::UpdateGeometry() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #13 0x2aaab4f0a751 in vtkPVDefaultPass::Render(vtkRenderState const*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkPVVTKExtensionsRendering-pv4.3.so.1 #14 0x2aaaba0ae35b in vtkCameraPass::Render(vtkRenderState const*) () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #15 0x2aaaba1206c0 in vtkOpenGLRenderer::DeviceRender() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #16 0x2c4bb18d in vtkRenderer::Render() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #17 0x2c4b8429 in vtkRendererCollection::Render() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #18 0x2c4c2202 in vtkRenderWindow::DoStereoRender() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #19 0x2c4c2119 in vtkRenderWindow::DoFDRender() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #20 0x2c4c31a3 in vtkRenderWindow::DoAARender() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #21 0x2c4bf7fe in vtkRenderWindow::Render() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingCore-pv4.3.so.1 #22 0x2aaaba1ae7ae in vtkXOpenGLRenderWindow::Render() () from /home4/jcbecker/ParaView-4.3.1-Linux-64bit/lib/paraview-4.3/libvtkRenderingOpenGL-pv4.3.so.1 #23 0x2aaab3b7597f in vtkPVRenderView::Render(bool, bool) () from
