<!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">
Jerry,<br>
<br>
When I am defining a Set as you have in (2) below, is it a
standalone entity or is it part of a Grid? If it is part of a Grid,
does it need to be defined at the "Collection" level or at the
individual "Topology Grid" levels [from (1) below].<br>
<br>
I will try to explain my problem in a little more detail as I do
not see exactly how the Set is going to help me. For each
Quadrilateral and Triangle in the unstructured mesh, I have an integer
value (surface ID) that determines which "surface" it belongs to.
Therefore, I would like to associate this data (the surface ID) with
the <b>existing</b> quadrilaterals and triangles that were defined in
the Grid Collection. In that sense, they are like <i>Attributes</i>
for the Quadrilaterals and Triangles.<br>
<br>
If I were to define them as Attributes to the Quads and Triangles,
how would ParaView treat them and where would they show up in the
Interface, i.e., how do I display specific surfaces? Same question
applies if I were to define them as Attributes to the Sets.<br>
<br>
Any suggestions most welcome.<br>
<br>
Sree<br>
<br>
<br>
<br>
Jerry Clarke wrote:
<blockquote cite="mid:4B50C847.8090303@arl.army.mil" type="cite">Sree,
<br>
<br>
1) Make each separate Topology a separate Grid. Then encapsulate
<br>
all the grids into a collection :
<br>
<Grid GridType="Collection" CollectionType="Spatial" ..
<br>
<Grid
<br>
<Grid
<br>
2)Use XdmfSet :
<br>
<br>
<Set Name="Ids" SetType="Node" SetLength="4">
<br>
<DataItem Format="XML" Dimensions="4" >
<br>
1 2 3 4
<br>
</DataItem>
<br>
<Attribute Name="Force" Center="Node">
<br>
<DataItem Format="XML" Dimensions="4" >
<br>
100.0 110.0 100.0 200.0
<br>
</DataItem>
<br>
</Attribute>
<br>
</Set>
<br>
3)No not really. You could use a nested <DataItem> of
type="Coordinates"
<br>
but that would be messy and slow.
<br>
<br>
<br>
Jerry
<br>
<br>
Kidambi Sreenivas wrote:
<br>
<blockquote type="cite">Hi,
<br>
<br>
I have a custom unstructured grid and solution file that is in HDF5.
I was looking into reading this into ParaView and was planning on
using XDMF for this purpose. However, I have run into certain issues
which I am not sure how to address and hence this plea for help:
<br>
<br>
(1) I have the connectivity maps for the various element types as
separate chunks in the HDF file, i.e., the Tetrahedra connectivity is
stored separately from the Wedge connectivity etc. This leads to a
problem with the Topology specification as I can have only one Topology
section per Grid. If I set the Topology type to Mixed, then I have to
re-encode my connectivity data (something I would prefer not to do).
Is there any way to read this data given these constraints?
<br>
<br>
(2) I did not see any support for specifying boundary "tags", i.e., an
integer identifier for boundary faces (triangles and quads in 3D) such
that I can display only a specified surface or a list of surfaces as
needed. Am I missing something or is this feature not available?
<br>
<br>
(3) I have the dependent variable vector (consists of a combination of
scalars and vectors) that is written out as a single entity and not as
individual scalars and vectors. Is there an easy way to make XDMF read
it?
<br>
<br>
Thanks for your help,
<br>
<br>
Sree
<br>
_______________________________________________
<br>
Powered by <a class="moz-txt-link-abbreviated" href="http://www.kitware.com">www.kitware.com</a>
<br>
<br>
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>
<br>
<br>
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>
<br>
<br>
Follow this link to subscribe/unsubscribe:
<br>
<a class="moz-txt-link-freetext" href="http://www.paraview.org/mailman/listinfo/paraview">http://www.paraview.org/mailman/listinfo/paraview</a>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>