Creating and editing co-executions

A co-execution is the co-simulation execution of two analysis jobs. You specify job parameters in a co-execution to create both analysis jobs. After creating the co-execution, you can edit the job parameters only in the individual analysis jobs.

Related Topics
Understanding co-executions
Creating, editing, and manipulating co-executions

Context:

The jobs are executed in synchronization with one another using the same functionality as described in Understanding analysis jobs. For more information on this analysis technique, see Structural-to-structural co-simulation.

  1. From the main menu bar, select Co-executionCreate or Co-executionEditco-execution name.

    The Edit Co-execution dialog box appears.

    Tip: You can also create a co-execution by clicking the icon in the module toolbox or clicking Create in the Co-execution Manager.

  2. Type the name of the new co-execution in the Name text field. The name that you specify must adhere to the file naming rules for your operating system.

  3. If desired, type the description of the co-execution in the Description text field. The description is stored in the model database and the output database, and you can use this description to help you manage your co-executions.

  4. In the Models table, select the models in the current model database to associate with the co-execution from the list in the Model Name column.

    The analysis product used in each of the selected models and the default job name for each model are displayed in the table.

  5. If desired, click in the Job Name column and edit the job name.

  6. Use the Submission, General, Memory, Parallelization, and Precision tabbed pages to define the initial job parameter settings in the individual job editors. After the co-execution is created, the job parameters in the co-execution editor are unavailable for editing; you must edit the individual jobs.

    Define the initial job parameter settings as described in the following sections:

  7. If desired, enter a different value in the Communication time out field to specify the time after which Abaqus/CAE terminates if it does not receive any communication from the coupled analyses. The default value is 10 minutes.

  8. Click OK.