[Paraview] [EXTERNAL] Best file format for volume rendering in ParaView?

[Christoffer Green]

Hello

Thank you for the suggestion.

If I do this:

Import ensight (that is multi-block) data->apply MergeBlocks filter-> Apply
calculator filter (to get magnitude of the velocity data, volume rendering
complains of lack of points otherwise). And then select volume as
representation then I get a progressbar that says
"OpenGLProjectedTetrahedraMapper: 1" that extremely slow, appears to get
incremented by 1% every 5 minutes or so.


Is this by design or a bug? I have tried it on 2 different computers.

The data set used is a 80x80x46 point volume cube.

BR/ Christoffer

On Mon, May 21, 2012 at 8:01 PM, Scott, W Alan <wascott at sandia.gov> wrote:

>  Christoffer,****
>
> ** **
>
> Ensight format – You can volume render multi-block datasets by first using
> the Merge Blocks filter.****
>
> ** **
>
> Alan****
>
> ** **
>
> ** **
>
> *From:* paraview-bounces at paraview.org [mailto:
> paraview-bounces at paraview.org] *On Behalf Of *Christoffer Green
> *Sent:* Monday, May 21, 2012 5:57 AM
> *To:* ParaView
> *Subject:* [EXTERNAL] [Paraview] Best file format for volume rendering in
> ParaView?****
>
> ** **
>
> Hello****
>
> ** **
>
> What are your thoughts on the best file format to use when doing volume
> rendering in ParaView?****
>
> ** **
>
> I have been trying out the ensight format and the vtk format and find them
> less then ideal, is there anything better?****
>
> ** **
>
> Findings for ensight:****
>
> ParaView does not appear to support volume rendering of ensight files due
> to it not supporting volume rendering of multi-block datasets and the
> ensight reader always imports things in multi block mode. There are ways to
> get around this (tetrahedralize together with calculator filter) but the
> end results appear to be extremely slow when volume rendering.****
>
> ** **
>
> Findings for vtk:****
>
> Importing a volume of data as image data and volume rendering it works
> well but image data in the vtk format must always be aligned to the global
> orthogonal (x, y, z) axes so it cannot be rotated. Since we have multiple
> data files that all must be positioned and rotated in a scene (MRI volumes
> and image planes) this makes things uncomfortable. There is a transform
> filter in ParaView but after applying it to image data it changes the data
> type to curvalinear grid which ParaView cannot volume render.****
>
> ** **
>
> ** **
>
> What are the alternatives?****
>
> ** **
>
> BR/ Christoffer****
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20120523/090f392f/attachment-0001.htm>