|
Rafael, *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. 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. |Genesis File| --> |Simulation Code| --> |Exodus File| --> |ParaView| 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. 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." *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.) These two results file formats are quite flexible and allow you to use ParaView in rather amazing ways. Sam Key Rafael Castaneda wrote: Hi, |
<<attachment: samuelkey.vcf>>
_______________________________________________ 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
