[Paraview] Data size limit?

[Wylie, Brian]

All of the information below is correct, I just want to explicitly point
out that the easiest thing to do in the short term is just turn off
compositing.

Long term, figure out why you can't open an x window, fix it, and turn
compositing back on. :)

  Brian Wylie - Org 9227
  Sandia National Laboratories
  MS 0822 - Building 880/A1-J
  (505)844-2238 FAX(505)845-0833                       
       ____                  _    __
      / __ \____  _________ | |  / (_)__ _      __ 
     / /_/ / __ `/ ___/ __ `/ | / / / _ \ | /| / /
    / ____/ /_/ / /  / /_/ /| |/ / /  __/ |/ |/ /
   /_/    \__,_/_/   \__,_/ |___/_/\___/|__/|__/

                                    Unleash the Beast
 

> -----Original Message-----
> From: paraview-bounces+bnwylie=sandia.gov at paraview.org 
> [mailto:paraview-bounces+bnwylie=sandia.gov at paraview.org] On 
> Behalf Of Moreland, Kenneth
> Sent: Tuesday, February 28, 2006 5:10 PM
> To: Christoph Moder; ParaView at paraview.org
> Subject: RE: [Paraview] Data size limit?
> 
> I'm guessing your crash has nothing to do with ParaView 
> running out of memory.  When you are running in client/server 
> and you load in a "big"
> data set (the threshold for "big" is adjustable, but 10 MB by 
> default), rendering switches from client to server.  This 
> means that the server will open up rendering windows, render 
> in parallel, and ship images to the client.
> 
> It looks like your server is unable to connect to the xhost 
> to open a window (note the "bad X server connection" error) 
> and is subsequently crashing.  Change the xhost permissions 
> on the nodes in your cluster to allow your ParaView job to 
> connect to the xhost.
> 
> Alternatively, if you do not have rendering hardware on your 
> server and you are rendering with Mesa anyway, you can turn 
> on OSMesa support so that the server never has to connect to 
> the xhost.
> 
> -Ken
> 
> > -----Original Message-----
> > From: paraview-bounces+kmorel=sandia.gov at paraview.org
> > [mailto:paraview-bounces+kmorel=sandia.gov at paraview.org] On 
> Behalf Of 
> > Christoph Moder
> > Sent: Tuesday, February 28, 2006 5:04 PM
> > To: ParaView at paraview.org
> > Subject: [Paraview] Data size limit?
> > 
> > Hello!
> > 
> > I would like to use Paraview with big data files which contain 
> > unstructured grids with 10 million grid points. But Paraview always 
> > crashes, with different error messages. Is there any size 
> limit? The 
> > size of the data file (binary vtk) is only 800 MB, this 
> should not be 
> > a problem (PC: 2 GB RAM +
> > 4 GM swap space). Also parallel processing does not help. 
> > Below are some error messages. Any comments?
> > 
> > Thanks,
> > Christoph
> > 
> > ====================
> > 
> > $ mpirun -machinefile ~/machinefile.txt -np 2 ./paraview
> > p1_27474:  p4_error: alloc_p4_msg: Message size exceeds P4s maximum 
> > message size: 321213977
> > rm_l_1_27475: (257.175131) net_send: could not write to 
> fd=5, errno = 
> > 32
> > 
> > ====================
> > 
> > $ ./paraview
> > ErrorMessage
> > # Error or warning: There was a VTK Error in file: 
> > /home/moder/paraview-3D/paraview-2.4.2-clone2/GUI/Client/vtkPV
> > Application.cxx
> > (1732)
> >   vtkPVApplication (0xb65d8b8): TclTk error: Point scalarUncaught
> > exception: St9bad_alloc
> >   Point scalarUncaught exception: St9bad_alloc
> > 
> >      while executing
> > "vtkTemp92 DrawSurface"
> >      invoked from within
> > ".paraview.24.33.34.176.177.200.201.203.208.214.215.216.frame.
> > 483.485.487.494.495
> > invoke active"
> >      ("uplevel" body line 1)
> >      invoked from within
> > "uplevel #0 [list $w invoke active]"
> >      (procedure "tk::MenuInvoke" line 47)
> >      invoked from within
> > "tk::MenuInvoke
> > .paraview.24.33.34.176.177.200.201.203.208.214.215.216.frame.4
> > 83.485.487.494.495
> > 1"
> >      (command bound to event)
> > ErrorMessage end
> > 
> > ErrorMessage
> > # Error or warning: There was a VTK Error in file: 
> > /home/moder/paraview-3D/paraview-2.4.2-clone2/VTK/Common/vtkDa
> > taArrayTemplate.txx
> > (241)
> >   vtkIdTypeArray (0xac862e20): Unable to allocate 146800640 
> elements 
> > of size 8: St9bad_alloc ErrorMessage end
> > p0_22811:  p4_error: interrupt SIGSEGV: 11
> > 
> > ====================
> > 
> > $ mpirun -machinefile ~/machinefile.txt -np 2 ./paraview 
> Process id: 1 
> > >> ERROR: In 
> > /home/moder/paraview-3D/paraview-2.4.2-clone2/VTK/Rendering/vt
> > kXOpenGLRenderWindow.cxx,
> > line 1319
> > vtkXOpenGLRenderWindow (0xb576c78): bad X server connection.
> > 
> > 
> > p1_22329:  p4_error: interrupt SIGSEGV: 11
> > rm_l_1_22330: (1360.557878) net_send: could not write to 
> fd=5, errno = 
> > 32
> > 
> > ====================
> > _______________________________________________
> > ParaView mailing list
> > ParaView at paraview.org
> > http://www.paraview.org/mailman/listinfo/paraview
> > 
> > 
> 
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
> 
>