Data Model Structure

System Coupling's data model has a hierarchical structure, much like that of a directory system or file system.

Settings are grouped and contained in paths in the data model. Items defined in the data model tree are of two types: containers and settings.

Containers

Containers are used to organize the different branches of the data model and can contain other containers and/or settings. There are two types of containers: singletons and object containers.

  • Singletons are containers that may have multiple instances but can be defined only once within their context. For example:

    • The AnalysisControl singleton has only one instance in the data model. Analysis control settings are applied at the analysis level.

    • ExecutionControl is a singleton that has multiple instances in the data model, with one defined for each participant. Execution settings are applied at the participant level.

  • Object Containers are containers that may have multiple instances of the same name and that can contain multiple uniquely named objects. For example:

    • There is only one CouplingParticipant object container, and it contains multiple named participant objects, such as MAPDL-1, CFX-2, and so on.

    • There can be multiple instances of the Region and Variable object containers defined for each coupling participant. They can contain one or more uniquely named region or variable objects, respectively, for the associated participant.

    A coupled analysis includes at least two participant objects and at least one interface object.

Settings

Settings are parameters that have values assigned with an equal sign.

Figure 1: Data model example in System Coupling's GUI

Data model example in System Coupling's GUI

Figure 2: Data model example in System Coupling's CLI

Data model example in System Coupling's CLI