3. Field Enumerators

In a MemCom database, many different kinds of solution data may be present simultaneously. This creates the problem of identifying of and distinguishing between the different kinds of data. The concept of enumerators deals with this problem. In MemCom, data is grouped into datasets. Each dataset has a unique name. This name contains the enumerator names and values that apply for that dataset. All other enumerator values are "None".

In the following, all supported enumerators are described. Depending on the database in question, not all of the enumerators described here may be displayed.

• NAME: This is the generic name. Typical examples are "DISP", "VELO", "TEMP", etc.

• COMPUTATION: This enumerator is used for databases where several analyses using possibly different codes have been made using the same mesh. For instance, a database may contain the solution datasets from a stress analysis made with code A and from a fatigue analysis performed using code B, both using the same Finite-Element mesh. The enumerator values for COMPUTATION would then be "A" and "B". If no computations are defined, the value is "None".

• CASE: Load case to be selected. This applies primarily to Finite-Element codes or codes where the database contains solutions from different initial and boundary conditions. If no load cases are defined, the value is "None".

• CYCLE: Computational cycle. This applies to nonlinear analyses.

• MODE: For modal analysis (e.g. pre-buckling analysis, free-vibration analysis), this identifies the mode number.

• SUBCYCLE: For nonlinear analyses using a Newton-Raphson iterations or similar techniques, this identifies the sub-iteration. This enumerator is rarely used. It can be useful to verify the correct behaviour of nonlinear solvers.

• LAYER: For Finite-Element stress analysis; this may identify the layer of a composite structure. This enumerator is rarely used.