SIMULIA Co-Simulation Engine Director Execution

Co-simulation between Abaqus/Standard and Abaqus/Explicit is governed by an additional process, the SIMULIA Co-Simulation Engine (CSE) director. Typically, you are not required to invoke the CSE director process; it is invoked automatically when you run the Abaqus co-simulation procedure (Abaqus/Standard, Abaqus/Explicit, and FMU Co-Simulation Execution).

If you are unable to use the Abaqus co-simulation procedure and are required to submit the co-simulation analyses separately using the Abaqus execution procedure (Abaqus/Standard and Abaqus/Explicit Execution), you must invoke the CSE director as described in this section.

This page discusses:

 

See Also
About Execution Procedures

Command Summary

abaqus cse job cosim-job-name configure configuration file-name listenerport listener port-number datacheck interactive license_type { token credit }

Command Line Options

job

The value of this option specifies the name of the co-simulation summary log file generated during the run. If this option is omitted from the command line, you will be prompted for its value.

configure

This option specifies the name of the SIMULIA Co-Simulation Engine configuration file that governs the co-simulation. For more information, see Using the SIMULIA Co-Simulation Engine Configuration File.

listenerport

This option is used to specify the TCP/UDP port number for co-simulation inbound messages to the director. Set listenerport equal to the port number used for the connection.

datacheck

This option causes the director to check the correctness of the configuration file only.

interactive

This option causes the director to run interactively.

license_type

This option is used to control the type of license Abaqus uses for the SimUnit license model. The possible values are token and credit. The default value is token. This capability is also supported through the Abaqus environment file with the environment variable license_type. For more information, see Environment File Settings.

Examples

The following example illustrates the different functions and capabilities of the co-simulation director execution procedure when you are required to submit the co-simulation analyses separately.

Running an Abaqus/Standard to Abaqus/Explicit Co-Simulation

Use the following command for the first Abaqus analysis, running on machine “earth,” to connect to the co-simulation director, running on machine “mercury” and listening on port 44444: 

abaqus job=explicit csedirector=mercury:44444

Use the following command for the second Abaqus analysis, running on machine “venus,” to connect to the co-simulation director, running on machine “mercury” and listening on port 44444: 

abaqus job=standard csedirector=mercury:44444

Use the following command for the co-simulation director, running on machine “mercury,” to operate according to the co-simulation configuration defined in the file explicit_standard_config.xml and to receive communication through port 44444: 

abaqus cse job=cosim listenerport=44444
   configure=explicit_standard_config.xml