HyperMesh Results Database

The structure of a results database allows you to access results by a method similar to that of the analysis code. A results database is divided into sections called simulations. Each simulation stores the results for a model as it responds to a loading condition. For example, if you run a linear statics problem and apply three different loading conditions to your model, the results file generated by the translator contains three simulations. If you run a nonlinear job, each load step (the response of the model to each incremental amount of load applied) translates to a simulation.

Each simulation in the results database is further subdivided into data types. Each data type found in a simulation contains a group of results of the same type. For example, each simulation in a results file may contain two data types: displacements and von Mises stress. A data type may contain only one type of result. Data types are one of the forms described below:

nodal displacement	Stores three floating point values at a node. This form of data type is usually used to store displacements or a vector quantity.
nodal value	Stores one floating point value at a node. This form of data type is used to store stress quantities or other types of results where a single value is needed at a node.
element value	Stores one floating point value at an element. This form of data type is used to store stress quantities or other types of results where a single value is needed at an element.
complex nodal displacement	Stores a complex value (magnitude and phase) at a node. This form of data type is usually used to store displacements or a vector quantity.
complex nodal value	Stores a complex value (magnitude and phase) at a node.
complex element value	Stores a complex value (magnitude and phase) at an element.
complex nodal von Mises	Stores a complex von Mises value (magnitude, phase, offset) at a node.
complex element von Mises	Stores a complex von Mises value (magnitude, phase, offset) at an element.

Data types are not required to contain results for every node or element in the model, and may contain a subset of the total model, if this is appropriate. If this occurs, a message is printed indicating that results for some of the entities requested were not found in the database. In order to complete the post-processing function being executed, HyperMesh sets the results values needed for that function to zero for all of the nodes or elements that are missing.