Run a Job With Optional CouplingΒΆ

A coupled simulation (or co-simulation) is one in which the CONVERGE solver and a third-party application advance together in time, exchanging data at each time-step. On CONVERGE Horizon, you can run coupled simulations with GT-SUITE if you have a GT-SUITE license hosted on your own license server.

Before running jobs with optional coupling, complete the setup required to use a self-hosted license for GT-SUITE. Once this setup is done, you can follow the usual process for running jobs in the CONVERGE Horizon web interface, with a few special considerations:

  • Be sure to perform the necessary case setup for a coupled simulation and upload all of the required input files to the file system or space. This includes the cosimulation.in file and the input files for GT-SUITE. For more details, refer to the CONVERGE Manual, available on the Convergent Science Hub (login required).

  • Do not upload a gtlink.prm file. This file is generated automatically by CONVERGE Horizon.

  • When creating the job, specify optional coupling with GT-SUITE.

  • Confirm that the GT-SUITE version in cosimulation.in matches the version selected in CONVERGE Horizon.

  • Specify your GT-SUITE license server before starting the job.

  • When selecting a node type, be aware that 2 cores will be allocated to GT-SUITE. For example, if you select a virtual machine (VM) with 36 cores, 34 cores will be used for CONVERGE and 2 cores will be used for GT-SUITE.

  • For jobs run from spaces, expect the Provisioning step to take longer than for a job without coupling (installing GT-SUITE on the cluster increases the build time). For jobs run on file systems, GT-SUITE will be installed on the file system for the first job and then cached for future jobs, so the extra build time will only affect the first job.