Re: [Paraview] ... not yet supported for more than 2147483647 bytes.

2017-06-29 Thread Kashiwa, Bucky
17 PM To: andrealphus <andrealp...@gmail.com<mailto:andrealp...@gmail.com>> Cc: Bucky Kashiwa <b...@lanl.gov<mailto:b...@lanl.gov>>, "ParaView@ParaView.org<mailto:ParaView@ParaView.org>" <ParaView@paraview.org<mailto:ParaView@paraview.org>> Subject

Re: [Paraview] ... not yet supported for more than 2147483647 bytes.

2016-12-21 Thread Berk Geveci
Besides what others said here, I am curious why ParaView is trying to move > 2 GB over MPI. This wouldn't normally happen unless it was trying to gather and deliver the entire dataset to the client. Which in itself would be a problem with data this size. What operation leads to this error? On

Re: [Paraview] ... not yet supported for more than 2147483647 bytes.

2016-12-19 Thread Kashiwa, Bucky
gov>>, "ParaView@ParaView.org<mailto:ParaView@ParaView.org>" <ParaView@paraview.org<mailto:ParaView@paraview.org>> Subject: Re: [Paraview] ... not yet supported for more than 2147483647 bytes. There are two parts to this issue. The first is that that vtkMPICommu

Re: [Paraview] ... not yet supported for more than 2147483647 bytes.

2016-12-19 Thread Andy Bauer
There are two parts to this issue. The first is that that vtkMPICommunicator for PV 4.3.1 won't communicate data that is over 2^31 bytes of data. This is fixed in PV 5.2. The other issue is due to MPI having a limit of 2^31 objects to be communicated in a single shot. This is MPI's API in that the

Re: [Paraview] ... not yet supported for more than 2147483647 bytes.

2016-12-19 Thread andrealphus
That is a 32 bit error, from trying to index something with more than (2^32)/2 elements or indices. Are you using any custom libraries/packages/modules which might not be 64 bit compliant? Are you sure you built a 64 bit version (check your gcc -v). -ashton On Mon, Dec 19, 2016 at 1:32 PM,