Are your pvservers 32 or 64 bits? If your pvserver's were compiled with 32 bits, my guess is that, you can't load piece of models with more than 4GB.

It's just my guess since I don't know exactly how PV works in these cases. Note that you can have the whole model in just 1 file or split in several files using a parallel file format like Xdmf. In the first case, pvserver should be able to load the entire model before partitioning among the other processes. In the second case, each process should be able to load its piece of model without relying in huge memory requirements.

(it's just my 2 cents for the subject... the other PV guys could clarify this question better...)

Renato.

Robert Mueller wrote:
Hi all,
I want to visualize simple 3d voxel data: creating iso surfaces, slices etc... First interactive and later in batch mode. As the data sets tend to get quite large (up to 1000x1000x1000 voxels) I probably have to use some parallel computation. pvserver/pvbatch seem the right tools for this, but the computing nodes don't have graphic cards I can use. So I tried compiling pvserver with osmesa and using the --use-offscreen-rendering switch. I tried some combinations of paraview version/mesa-lib with and without mpi. It's always the same: Stand alone paraview can open the (small) test files und display everything I want. When using the client/server mode, the server crashes at the point when more than a simple outline of the data has to be displayed.

Can somebody give instructions how to get a working pvserver fpr use without without graphics hardware (versions, linux distribution, compiler version)? Maybe I could build this system in virtual machine, just to have a valid starting point. I'm using ubuntu, amd64, 7.10
thank you
Robert Mueller
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview


_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview

Reply via email to