Scribd
Upload
14 views

HDF5 Api

This document describes the format for an input file that defines a finite element model with multiple parts, domains, variables, and geometry. It specifies the sections for general model information, geometry, variables, coordinates, and connectivity for structured or unstructured meshes. Transient problems require multiple input files, while changing geometry can be handled in the current file or by referencing external files.

Uploaded by

Sai Kumar
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
14 views

HDF5 Api

This document describes the format for an input file that defines a finite element model with multiple parts, domains, variables, and geometry. It specifies the sections for general model information, geometry, variables, coordinates, and connectivity for structured or unstructured meshes. Transient problems require multiple input files, while changing geometry can be handled in the current file or by referencing external files.

Uploaded by

Sai Kumar
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Version 0.

9
8/21/02 /model # parts (n, 1 or greater)
# Variables (k, 0 or greater)
*Time step and values are given here, but a transient problem Legend: group
requires a casefile pointing to multiple hdf files.
# domains (m, 1 or greater)
dataset
hasNodeIDs
attribute
*For changing geometry: hasElementIDs
geomChangingFlag writingConn LastGeomFile where are coords where is conn modelDescription1
-------------------------- --------------- ------------------- ------------------- ------------------ modelDescription2
STATIC TRUE ignored in this file in this file timeStep
STATIC FALSE "filename" in "filename" in "filename timeValue
COORDS_ONLY TRUE ignored in this file in this file geomChangingFlag (STATIC/COORDS_ONLY/CONN)
COORDS_ONLY FALSE "filename" in this file in "filename" writingConn
CONN ignored ignored in this file in this file lastGeomFile

If other than STATIC and writingConn = FALSE

Geometry Variables
[extent mins[3]/maxs[3]]

[variable_1] [variable_2] ... [variable_k]


varName
geom_part_1 geom_part_2 ... geom_part_n varDescription
partName varType (MODEL_CONSTANT/PART_CONSTANT/SCALAR/VECTOR/TENSOR)
partDescription If (not MODEL_ or PART_CONSTANT)
[extent mins[3]/maxs[3]] mappingType (PER_NODE/PER_ELEMENT) |
structuredFlag (UNSTRUCTURED/STRUCTURED) [range mins[9]/maxs[9]] |
if(STRUCTURED) else
structuredType (UNIFORM/RECTILINEAR/CURVILINEAR) constValue
iblankingVarName (Null if no iblanking)
ghostVarName (Null if no ghosts) (if not MODEL_CONSTANT)
structuredIJKs[3]

var_part_1 var_part_2 ... var_part_n


If (not PART_CONSTANT)
[range mins[9]/maxs[9]]
geom_domain_1 [geom_domain_2] ... [geom_domain_m] else
[extent mins[3]/maxs[3]] constValue
if (STRUCTURED)
IJKranges[6] (if not PART_CONSTANT)
|---> If other than COORDS_ONLY and writingConn = FALSE

var_domain_1 [var_domain_2] ... [var_domain_m]


[range mins[9]/maxs[9]]
coordinates [node_ids] [point] [point_ids] [bar2] [bar2_ids] [...]
layout layout layout
nNodes nElems nElems

If (STRUCTURED) [coordinates] [point] [bar2] [bar3] [tri3] [...]


If (UNIFORM), coordinates will have origin and deltas (6 numbers) layout layout layout layout layout
If (RECTILINEAR), coordinates will have the 3 vectors in component order
If (CURIVILINEAR), coordinates will have ijk order by components
Note: If STRUCTURED, only the following may be used:
If PER_NODE, coordinates
If PER_ELEM, bar2, qua4, or hex8 (as appropriate)

You might also like