[Paraview] XDMF questions...

[Kidambi Sreenivas]

Jerry,

    Thanks for the quick answer.  I had a follow up question:  When I 
used what you suggested in (1) below, I found that I had to repeat the 
Geometry section for each of grids in the collection.  How is this 
handled memory wise?  Is each of the subgrids going to have a copy of 
all the coordinates in the grid?  If that is the case, then we are 
really inefficient.  An alternative would be to allow a Grid to have 
multiple Topology sections, that way I can do what I want without having 
to repeat things.

    I have not tried (2) yet; will keep you posted on how that works.

Sree


Jerry Clarke wrote:
> Sree,
>
> 1) Make each separate Topology a separate Grid. Then encapsulate
> all the grids into a collection :
>     <Grid GridType="Collection" CollectionType="Spatial" ..
>           <Grid
>           <Grid
> 2)Use XdmfSet :
>
>         <Set Name="Ids" SetType="Node" SetLength="4">
>             <DataItem Format="XML" Dimensions="4" >
>                 1 2 3 4
>             </DataItem>
>             <Attribute Name="Force" Center="Node">
>                 <DataItem Format="XML" Dimensions="4" >
>                     100.0 110.0 100.0 200.0
>                 </DataItem>
>             </Attribute>
>         </Set>
> 3)No not really. You could use a nested <DataItem> of type="Coordinates"
> but that would be messy and slow.
>
>
> Jerry
>
> Kidambi Sreenivas wrote:
>> Hi,
>>
>>   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:
>>
>> (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?
>>
>> (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?
>>
>> (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?
>>
>> Thanks for your help,
>>
>> Sree
>> _______________________________________________
>> 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
>