[Paraview] vtu files with two pieces
Sreejith Kuttanikkad
sreejithpk at gmail.com
Thu Apr 16 03:57:34 EDT 2009
On Wed, Apr 15, 2009 at 10:44 PM, Samuel Key <samuelkey at bresnan.net> wrote:
> Sreejith,
>
> For two truly separate parts, create two separate *.vtu files. Each of the
> files should have a unique name (not really necessary for PV). PV is happy
> to read and display multiple datum sets -- even the same datum set twice. If
> you plan later to have many parts (for example, 100 parts), the collection
> can be aggregated with via a single *.pvd file (a meta-file or
> "mother-file"). Having PV read the single *.pvd file will load all of the
> *.vtu files referenced within the *.pvd file.
Thank you for the tips. Yes , idea of having a pvd file to load different
vtu files is good. I have tried that. I was thinking that I can have kind
of multiblock data in same vtu file with each block with different data set.
I understand there is multiblock data format too for vtk files. But dont
know the details and google search didnt give me enough information.
>
>
> A good rule to follow is to have each part as a "standalone" displayable
> graphical object.
>
Excuse me for my ignorance. What do you meant by above?
>
> Later on when you want to process large sets of data, EnSight-formatted
> binary files incorporate a "part" concept. Also, the EnSight-formatted data
> set has constructs for parallel file sets, and multiple files for individual
> data streams to get around file size limitations.
>
Thanks again,
Sreejith
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20090416/35d4a3bf/attachment.htm>
More information about the ParaView
mailing list