<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Rafael,<br>
<br>
*Exodus II.* The Exodus-II format supports side-sets and node-sets,
each of which may have point-data and cell-data. These are subsets of
the mesh model (meshed domain, whole object, or whatever terminology
you are using). On input, they are intended to be used by the
simulation software for areal and point BCs. If the simulation wants
to place data on these side-sets and node-sets, it may and then the
results can be viewed with ParaView. The side-sets in the case of
solids are element faces, and in the case of planar elements (quads or
triangles in 3D) are element edges. If one wants to use one of these
auxiliary sets for the display of results, a side-set can transect any
number of element blocks, have no BC's "attached" to it, but have the
simulation code add data to it. Of course, the simulation code has to
recognize this and write the datum occurring of this side-set out to
the final results.<br>
<br>
An Exodus-II file used only for mesh & BC input and empty of
results is usually referred to as a "Genesis" file. The simulation
code starts by reading the mesh model from the "Genesis" file and
initializes a new Exodus-II-formatted file with the mesh model in it
and follows by writing simulation results to it. <br>
<br>
|Genesis File| --> |Simulation Code| --> |Exodus File| -->
|ParaView|<br>
<br>
The "blocks" in an Exodus-II file are element-blocks. In the original
concept (and most software that uses the Exodus-II format), the finite
elements in the block all possess the same geometry, same nodalization,
same material model, and same element formulation (gradient &
divergence operator construction). In the simulation software, the the
outside-loop is on blocks and the inside-loop is on the elements in the
block. A homogeneous domain can be processed as one block, or be
sub-divided into any number of blocks in anticipation of post
processing needs. For a simulation code writing an Exodus-II formatted
file, the blocks do not have to be homogeneous with respect to material
model and formulation for ParaView.<br>
<br>
<br>
<br>
The Exodus-II format also supports hierarchical collections of element
blocks that can be used for identifying "parts" or "assemblies of
parts." However, the simulation code that writes the file needs to
have this "knowledge." <br>
<br>
*EnSight.* The EnSight format supports a concept of "parts."
Essentially, it is the idea of individual displayable graphics objects
each with point-data and cell-data. It is written out as if it were
one large assembly. ParaView via the filter 'Extract Block' can
collect just those "parts" (1 or more) you want to view as a single
item. (I use the "part" feature extensively including writing out
side-sets, node-sets, and other grid-sets that the simulation software
knows about.)<br>
<br>
These two results file formats are quite flexible and allow you to use
ParaView in rather amazing ways.<br>
<br>
Sam Key<br>
<br>
Rafael Castaneda wrote:
<blockquote
cite="mid:898447c41001190553xc318ba5n256f0fdfdbc806de@mail.gmail.com"
type="cite">Hi,<br>
<br>
thanks for answering. I've programmed a plugin for CFD preprocessing
purposes (I mean, setting boundary and initial conditions, solver
parameters and so on) and I would like that a user could make a
model+mesh in ICEM CFD and export it to ParaView. When using ICEM CFD,
one usually creates parts, which are grouping of 2D geometric entities,
so that one can distinguish between different regions to attribute
different BC's or IC's. The user also must create a domain, which is
actually the 3D physical domain in which there is a flow. <br>
<br>
When I export to exodus II format, just the 3D Physical Domain is
created as a block in the Multiblock Dataset, the 2D geometric
entities, the parts, are not created. But I really need this
information, so that I can distinguish the parts of the Model in my
plugin and allow the user to select them to associate conditions. I
tried exporting to fluent format in ICEM CFD, then opening with Fluent,
saving as .cas file (which ParaView can read), but also: no information
about the parts.<br>
<br>
The question is: is there any format or reader, available in VTK or
ParaView that is known to read ICEM CFD Meshes with ALL the information
? I'm pretty sure someone somewhere already needed this ! <br>
<br>
Thanks a lot for your help,<br>
Rafael Castaneda.<br>
<br>
<div class="gmail_quote">2010/1/19 Berk Geveci <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:berk.geveci@kitware.com">berk.geveci@kitware.com</a>></span><br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Out
of curiosity, what is the difference between parts and blocks? Or<br>
are you using them<br>
interchangeably?<br>
<div>
<div class="h5"><br>
<br>
On Mon, Jan 18, 2010 at 11:28 AM, Rafael Castaneda <<a
moz-do-not-send="true" href="mailto:ramacaneto@gmail.com">ramacaneto@gmail.com</a>>
wrote:<br>
> Hi,<br>
><br>
> I'm trying to export a mesh generated in ICEM CFD to ParaView. I
realized<br>
> that I can export the mesh to Exodus II format and then open it
with<br>
> ParaView, but no information about the parts of the mesh is
loaded, just the<br>
> blocks.<br>
><br>
> Any reader available to export geometry and mesh from ICEM CFD to
ParaView ?<br>
> I would like that the MultiBlockDataSet generated as result have
information<br>
> about the parts created in ICEM CFD.<br>
><br>
> Regards,<br>
> Castaneda.<br>
><br>
</div>
</div>
> _______________________________________________<br>
> Powered by <a moz-do-not-send="true" href="http://www.kitware.com"
target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at<br>
> <a moz-do-not-send="true"
href="http://www.kitware.com/opensource/opensource.html"
target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Please keep messages on-topic and check the ParaView Wiki at:<br>
> <a moz-do-not-send="true" href="http://paraview.org/Wiki/ParaView"
target="_blank">http://paraview.org/Wiki/ParaView</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a moz-do-not-send="true"
href="http://www.paraview.org/mailman/listinfo/paraview"
target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
><br>
><br>
</blockquote>
</div>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Powered by <a class="moz-txt-link-abbreviated" href="http://www.kitware.com">www.kitware.com</a>
Visit other Kitware open-source projects at <a class="moz-txt-link-freetext" href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a>
Please keep messages on-topic and check the ParaView Wiki at: <a class="moz-txt-link-freetext" href="http://paraview.org/Wiki/ParaView">http://paraview.org/Wiki/ParaView</a>
Follow this link to subscribe/unsubscribe:
<a class="moz-txt-link-freetext" href="http://www.paraview.org/mailman/listinfo/paraview">http://www.paraview.org/mailman/listinfo/paraview</a>
</pre>
</blockquote>
</body>
</html>