[Paraview] pvserver Projected tetra

[M P]

FYI, the symptoms are very similar to this post
http://www.paraview.org/pipermail/paraview/2012-November/026753.html
except that I am not using curved screen ...
Is there something specific that needs to be done to make tetra volume
rendering with pvserver happening?

Best regards,

Martin


On Thu, Jan 30, 2014 at 10:29 AM, M P <martin34148 at gmail.com> wrote:

> 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/20140205/5358b722/attachment.html>