About the SIMULIA Co-Simulation Services Configuration File

The Co-Simulation Configuration file specifies the layout of the coupled simulation (the subsystems involved and the fields exchanged between the subsystems), the synchronization and coupling scheme, as well as mapper controls.

Developers need to author the Co-Simulation Configuration file for their coupled simulation product. Experienced end users might benefit from the discussion in case they need to modify algorithmic settings for their coupled simulation.

You should have:

  • Prerequisite knowledge of XML (refer to the World Wide Web Consortium (W3C) site, for information on XML); and
  • Knowledge of the capabilities and features of the SIMULIA Co-Simulation Services.

This page discusses:

The SIMULIA Co-Simulation Services is comprised of software libraries used by the clients (referred to as subsystem simulators) and an independent directing process (referred to as the SIMULIA Co-Simulation Services Director). For example, the subsystem simulators communicate through the SIMULIA Co-Simulation Services API with a collection of runtime libraries called the Simulation Runtime Environment (SRE). The subsystem simulators are then directed in their simulation behaviors through the SRE, which operates under the direction of the SIMULIA Co-Simulation Services Director. The SIMULIA Co-Simulation Services Director is a finite state machine, as described in SIMULIA Co-Simulation Services Director. You define the coupled physics properties and behaviors to the SIMULIA Co-Simulation Services Director by providing the Co-Simulation Configuration file. The SIMULIA Co-Simulation Services Director then generates an SCXML state machine for the coupled simulation.

The Configuration File Content

Coupled simulation requires the interaction of two or more subsystems simulators, perhaps from different physics disciplines. The Co-Simulation Configuration file provides a general and extensible interface to define the coupled simulation, the synchronization and coupling algorithm, and mapper settings.

Any information related to the computing environment or file system resources is not defined in the Co-Simulation Configuration file. Examples of such information include the following:

  • file system or database resource locators for subsystem input data (for example, Abaqus/Standard input files);
  • CPU counts for execution of subsystem simulation (for example, the user’s directive to run Abaqus/Explicit using 16 CPUs); and
  • execution path definitions and environment setting for subsystem simulators.

Configuration File Consistency Requirements

The configuration file is created in XML. You must satisfy the following requirements for the Co-Simulation Configuration file to be accepted by the SIMULIA Co-Simulation Services Director. These requirements are verified by the SIMULIA Co-Simulation Services Director at run time. Optionally, the SIMULIA Co-Simulation Services Director can perform all but the final check using the datacheck execution option.

XML well-formedness
Your file must be written in proper XML format. In addition to using the SIMULIA Co-Simulation Services Director to confirm that your file is well-formed, virtually any XML authoring tool or facility provides similar services.
Conformance to the Co-Simulation Services schema
The majority of the rules and constraints defined in this section are described formally in the file SMACseConfig.xsd, which is included in the /site folder of the SIMULIA Co-Simulation Services API Kit. This file is written in the XML Schema Definition Language (XSD). In addition to use of the SIMULIA Co-Simulation Services Director to confirm the schema compliance of your file, a significant number of XML authoring tools provide similar schema validating services.
Internal consistency of references
The Co-Simulation Configuration file defines references among items defined elsewhere in the file. For example, a “connection set” refers to a pair of “connectors” and the connector names referred to in the connection set must be defined in the file. The SIMULIA Co-Simulation Services Director enforces constraints such as these.
Topological and algorithmic consistency
The Co-Simulation Configuration file provides information that can be considered correct only in the context of the topology of the problem described (for example, are input variables paired with output variables?) and the algorithms used (for example, does a configuration description result in a deadlock situation?). The SIMULIA Co-Simulation Services Director performs these consistency checks.
External consistency of references
At run time, the subsystem simulators, through use of SIMULIA Co-Simulation Services API calls, register names with the SIMULIA Co-Simulation Services Director. These names must have accompanying entries in the Co-Simulation Configuration file. The SIMULIA Co-Simulation Services Director enforces these constraints during run time; they cannot be enforced during the data check phase.