[Paraview] [EXTERNAL] pvserver Projected tetra

[Scott, W Alan]

MP,
I believe this is the same bug that my team found a week ago.  Basically, remote rendered, multiple server volume rendering is broken with 4.1.0.  Kitware knows about this, and is working on it.  One solution would be to stick with 4.0.1 for volume rendering.

http://paraview.org/Bug/view.php?id=14581

Alan


From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of M P
Sent: Thursday, January 30, 2014 2:29 AM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] pvserver Projected tetra

Hi all,

I have a problem using volume rendering with the "Projected tetra" mapper in paraview client/server mode (4CPU server)

I start the server (it is linux sever with K20m teslas) using:

~/sw/ParaView-4.1.0-Linux-64bit/lib/paraview-4.1/mpiexec -np 4 ~/sw/ParaView-4.1.0-Linux-64bit/lib/paraview-4.1/pvserver

... with that confuguratin the Projected tetra mappere prosuces only some artifacts

But when I start the sever on just one CPU it renders (Projected tetra) OK:

~/sw/ParaView-4.1.0-Linux-64bit/bin/paraview


My settings in paraview client are:

"Remote Render Threshold"  On (0 Mbytes)


It could be replicated like this:

1. create Wavelet source
this volume renders (Smart mapper) OK in both server setups

2. convert it with Tetrahedralize filter
volume rendering of this (Projected tetra) with parallel server prduces just some cells rednered as can be seen in the attached image.

images:
smart.jpeg ... Wavelet voleme rendered (Smart) with both server configurations
projected_tetra.jjpeg ... tetrahedralized wavelet volume rendered (Projected tetra) on 4 cpu server
both.jpeg ... the above results in one image

Is this an expected beahaviour? Or is some solution to this?

Thank you,

Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20140220/c8277157/attachment.html>