You can send a system coupling simulation to Remote Solve Manager (RSM) for remote update. In order for a system coupling simulation to be executed remotely, you must submit the Workbench project to RSM for a project update. To do so:
Set your project’s Solution Process and Project Update properties as described in Submitting Project Updates to Remote Solve Manager (RSM) or an EKM Portal.
Click the button in the Workbench toolbar.
All of the systems on the Project Schematic, including the System Coupling system, will be updated through RSM.
Note: For the System Coupling Solution cell, the Update Option property can only be set to Run in Foreground. As such, if you attempt to update the System Coupling system from its Solution cell, then the project update will not be sent to RSM regardless of the project’s Update Option setting.
The following sections provide information that is specific to remote project updates for System Coupling simulations:
In a System Coupling project, the individual components (such as Fluent, Mechanical, or CFX) share resources. By default, when a project containing a System Coupling system is submitted to RSM, available computing resources are distributed equally across all coupling participants according the number of compute nodes available and processes requested. Component-level parallel settings (such as the Execution Mode and Number of Processes properties) are disregarded during the project update.
If a coupled simulation requests 6 processes to be executed on a cluster that has 6 nodes with 1 processor per node, then participant solvers will start 6 processes, with one on each compute node. The participant solvers alternate their processing, so that only one participant is actively using computing resources at a time.
| Node | Solver Processes for Participant 1 | Solver Processes for Participant 2 |
|---|---|---|
|
1 |
1 |
1 |
|
2 |
1 |
1 |
|
3 |
1 |
1 |
|
4 |
1 |
1 |
|
5 |
1 |
1 |
|
6 |
1 |
1 |
If a coupled simulation requests 10 processes to be executed on a cluster that has 4 nodes with 8 processors per node, then each participant solver will start 10 processes.
| Node | Solver Processes for Participant 1 | Solver Processes for Participant 2 |
|---|---|---|
|
1 |
8 |
8 |
|
2 |
2 |
2 |
|
3 |
0 |
0 |
|
4 |
0 |
0 |
For a project configured for parallel processing, you can limit the number of solve processes that a coupling participant can use when the project is submitted to RSM. To do so, set the participant’s Restriction for Project/Design Point Update via RSM Solution cell properties as described in Updating Design Points via ANSYS Remote Solve Manager or an EKM Portal.
The solve process limitations are applied only to that component, and resources are otherwise allocated equally across participants. Resource allocation for the restricted participant is as follows:
If the component’s Specify Number of Processes Restriction is enabled:
and Number of Processes Used Not to Exceed is less than or equal to the number of processes requested by the project, then the component will be limited to the component-specified number of processes.
and Number of Processes Used Not to Exceed is set to a value greater than the number of processes requested by the project, then the component will be limited to the project-specified number of processes.
If the component’s Serial Execution Only is enabled, then the component is limited to a single process.
As the remote project update progresses, a single System Coupling Service Log file (scLog.scl) is generated for the coupling project and displayed in the Solution Information view of the System Coupling workspace. It is updated intermittently so you can use it to monitor the project update.
Note: When a project has multiple design points being updated simultaneously (i.e. the Job Submission Parameter Set property is set to One Job for Each Design Point), you cannot switch between the log files for the different design points. During and after completion of the updates, System Coupling will display the log file for the design point with the highest ID. To display the log file for the Current design point, you must save and reopen the project.
For more information, see the following sections in the System Coupling User's Guide:
| Solution Information |
| System Coupling Service Log File (scLog.scl_, scLog_##.scl) |
| Understanding the System Coupling Log File |
If you have interrupted a remote update of a System Coupling project, the Solution cells in your project will be given a status of Interrupted, Up to Date. To restart the update:
Click the button in the Workbench toolbar.
In dialog that is displayed, click one of the following buttons:
: Accepts the partially updated solution as Up to Date and uses it to update the project.
: Restarts the interrupted run, updating all solutions to completion before updating the project.