[Paraview] Volume rendering & pvserver

[Aashish Chaudhary]

Hi Johannes,

Utkarsh is right and what is suggested could work for you. I also remember
someone asking the same question in this mailing list and that person was
able to modify the volume rendering code to make it work in the CAVE. I
have to find the information but I believe that was the case. If you don't
find that email in this list, let us know unless you want to take the route
suggested by Utkarsh.

Thanks,


On Wed, Nov 21, 2012 at 10:05 AM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> Volume rendering of image datasets is currently not supported in CAVE
> (aka CurvedScreen) configurations. One hacky way to deal with it is to
> convert the data to unstructured grid (using Tetrahedralize filter)
> and then volume render that.
>
>
> On Wed, Nov 21, 2012 at 8:18 AM, Johannes Zarl <johannes.zarl at jku.at>
> wrote:
> > Hi,
> >
> > It seems like there is a bug with rendering volume datasets when being
> > connected to a pvserver process.
> >
> > When I use the builtin: server and load the dataset into paraview,
> everything
> > is rendered correctly. However, when I connect to a server process, only
> parts
> > of the volume data are shown. Objects using surface representation are
> always
> > rendered correctly.
> >
> > Just now I realised that there is a pattern to display irregularities:
> the
> > bounderies of the rendered parts align with the data-segmentation
> between the
> > process ids.
> >
> > So I guess there is some kind of communication problem between the
> pvserver
> > processes? If so, how can I find out the cause of this?
> >
> > Any help appreciated,
> >   Johannes
> >
> >
> > P.S.:
> > The example data I use is the headsq.vti file from the
> ParaViewTutorialData
> > dataset. I currently use ParaView/master 3.14.1-2441-g46cfc4c, and have
> tested
> > this also with paraview 3.14.1 (compiled from source).
> >
> > The server is started as follows:
> > mpirun -np 3 \
> >   --host n001 --host n002 --host n003 \
> >   --mca btl openib,sm,self \
> >    -x LD_LIBRARY_PATH -x PATH -x DISPLAY=:0 \
> >    pvserver /home/edvz/zing/scratch/vcva/curvedscreen.pvx
> >
> > The curvedscreen.pvx file is this one:
> > <?xml version="1.0" ?>
> > <pvx>
> >  <Process Type="client" />
> >   <Process Type="server">
> >   <EyeSeparation Value="0.065"/>
> >     <!-- CurvedScreen 3 screens -->
> >    <Machine Name="n001"
> >             Environment="DISPLAY=:0"
> >             LowerLeft= "-4.701 0.0   -2.641"
> >             LowerRight="-1.201 0.0   -2.641"
> >             UpperRight="-1.201 1.750 -2.641" />
> >    <Machine Name="n002"
> >             Environment="DISPLAY=:0"
> >             LowerLeft= "-1.750 0.0   -2.641"
> >             LowerRight= "1.750 0.0   -2.641"
> >             UpperRight= "1.750 1.750 -2.641" />
> >    <Machine Name="n003"
> >             Environment="DISPLAY=:0"
> >             LowerLeft=  "1.202 0.0   -2.641"
> >             LowerRight= "4.752 0.0   -2.641"
> >             UpperRight= "4.752 1.750 -2.641" />
> >  </Process>
> > </pvx>
> > _______________________________________________
> > 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
> >
> > Follow this link to subscribe/unsubscribe:
> > http://www.paraview.org/mailman/listinfo/paraview
> _______________________________________________
> 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
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>



-- 
| Aashish Chaudhary
| R&D Engineer
| Kitware Inc.
| www.kitware.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20121121/a3a59de9/attachment.htm>