<br><br><div class="gmail_quote">On Wed, Apr 15, 2009 at 10:44 PM, Samuel Key <span dir="ltr"><<a href="mailto:samuelkey@bresnan.net">samuelkey@bresnan.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Sreejith,<br>
<br>
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.</blockquote>
<div><br>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.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
A good rule to follow is to have each part as a "standalone" displayable graphical object.<br>
</blockquote><div><br>Excuse me for my ignorance. What do you meant by above?<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
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.<br>
</blockquote><div><br>Thanks again,<br>Sreejith<br><br></div></div><br>