[Paraview] Error when trying to turn on Volume Rendering for large tetrahedral data in ParaView 5.4.1
Utkarsh Ayachit
utkarsh.ayachit at kitware.com
Wed Jan 24 15:59:37 EST 2018
Joe,
Sorry, doesn't ring a bell. One thing to try is to turn of "Use Data
Partitions" (see [1]) if your data is already partitioned between
ranks such that we can build a sorting order.
Utkarsh
[1] https://blog.kitware.com/improved-parallel-rendering-in-paraview/
On Wed, Jan 24, 2018 at 3:16 PM, Hennessey, Joseph G CTR USARMY RDECOM
ARL (US) <joseph.g.hennessey2.ctr at mail.mil> wrote:
> Hello,
>
> I am experiencing an error with volume rendering very large
> tetrahedral data with ParaView version 5.4.1.
>
> The data is loaded properly and the surface representation works,
> but when I change the representation to Volume, I get the standard
> dialog below to which I respond "Yes"
>
> 'This will change the representation type to "Volume".
> That may take a while, depending on your dataset. Are you sure?'
>
> I am tested this on two of the HPC supercomputer systems
> while connected to a remote server with multiple compute nodes,
> communicating over MPI. I have verified, I am not running out of memory
> on the compute nodes or on the client but on large data,
> (over 40 million or so tetrahedrons) the compute nodes will crash
> without any error messages and the remote connection will drop,
> running out of memory would cause a similar failure, but as far as
> I can tell, that is not the case here.
>
> I wanted to see if anyone else had hit this problem, before I try building
> debug versions of the software and using a debugger on them,
> to trace the failure down more thoroughly.
>
> The data has 4 vectors and a scalar defined at each tetrahedron,
> and it renders fine with smaller subsets (less than 20 million
> or so tetrahedron). I would like to be able to scale up to a billion
> tetrahedrons eventually, so a 40 million limit is a problem.
>
> I suspect that there might be an issue in
> vtkOpenGLProjectedTetrahedraMapper.cxx
> where some buffer is maybe 32 bit instead of 64 bit,
> but I have not confirmed this.
>
> Has anyone already solved this problem yet?
>
> Thanks,
>
> Joe
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Joseph G. Hennessey Ph.D., SAIC
> Team SAIC
> Army Research Lab
> DOD Supercomputing Resource Center
> Email: joseph.g.hennessey2.ctr at mail.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
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>
More information about the ParaView
mailing list