Submitting Fluids Jobs to RSM or an EKM Portal

See the following sections for more information:

Submitting CFX Jobs to RSM or an EKM Portal

  1. Configure your remote solution settings via Remote Solve Manager. If submitting jobs directly to Remote Solve Manager, see RSM Installation and Startup and RSM Configuration in the RSM User's Guide. If submitting jobs to Remote Solve Manager via an EKM Portal, see Integrating EKM with Remote Solve Manager (RSM) in the EKM Administration Guide.

  2. In ANSYS Workbench, right-click the Solution cell and select Properties. Select the Solution Process settings that you want to use for this solution and update the project.


    Note:
    • If you set Execution Mode to Parallel:

      • You can specify the number of processes that you want to use to create the results file. You should specify a number that is less than or equal to the number of cores available in the cluster, and you should ensure that each process contains at least 100,000 nodes or elements.

      • UGE and PBS clusters must be configured to use the SSH communication protocol; RSH is not supported. If you are using the Submit to Remote Solve Manager option, see Configuring RSM to Use SSH for Job Submission to a Remote Linux Cluster in the Remote Solve Manager User’s Guide.

    • You can Interrupt or Abort an update by right-clicking the Solution cell. These options are available during foreground, background and RSM updates.


ANSYS CFX has the following limitations when used with Remote Solve Manager or an EKM Portal:

  • RIF (Flamelet) cases are not supported.

  • Reconnect will not work after moving a project to another machine.

  • Only one copy of a saved project that is in the pending state can reconnect successfully.

  • You must manually save a project after a reconnect.

  • You cannot edit a run that is in progress.

  • You cannot perform a remote backup.

  • For runs that are submitted to a remote machine:

    • Serial and Local Parallel runs are always supported.

    • Other local parallel modes must be supported on the job host.

    • Distributed parallel is supported only for multi-node clusters.

  • The default update interval for Display Monitors is 120 seconds. Use the Download Progress Information and Progress Download Interval options under Tools > Options > Solution Process to enable/disable polling or to change the polling interval. The settings established here will also be visible in the Solution Process properties pane in ANSYS Workbench.


    Note:  This monitoring of solution updates submitted to RSM or an EKM Portal has the following limitations:

    • When you use the Solution cell's properties field to set the frequency at which you poll the data, this represents a maximum frequency. In cases of network congestion or where large files are involved, the observed monitor update frequency will be less.

    • Solution monitor data is transferred via the CFX Solver-Manager, which has a limited capacity to handle monitor data transfer requests. In situations where multiple users are using the same CFX Solver-Manager to monitor runs, or where multiple runs are being monitored by a single user, the update frequency of monitor data may decrease or become sporadic.

    • When monitoring RSM updates, CFX Solver-Manager will not report run completion. The Out File window will show the completed run information; however, CFX Solver-Manager's workspace will still display "Running". Note that in these cases, Workbench will accurately report update completion.


Submitting CFX Jobs with Design Points to RSM or an EKM Portal

When performing a Design Point update with a CFX system via RSM, the Component Execution Mode and Max. Number of Processes Per Job settings on the Parameter Set Properties view control the parallel-processing settings that the CFX Solver uses. For details, see Updating Design Points via ANSYS Remote Solve Manager or an EKM Portal.

Submitting CFX Jobs to a Cluster via RSM or an EKM Portal

If you have a Microsoft HPC, PBS, LSF, UGE or TORQUE queue available, you can use that as a parallel solution option. In the Solution Processes pane:

  1. Set the Update Option to Submit to Remote Solve Manager or Submit to Portal.

  2. Set the RSM Queue or Queue, as appropriate.

  3. Set the Execution Mode to Parallel.

  4. Set the Number of Processes to the number of partitions desired[2]. The cluster job scheduler automatically controls where the partitions are solved.

Refer to the following sections in the Remote Solver Manager User’s Guide for details on defining cluster configurations in RSM, and configuring a cluster:


Note:
  • For a Microsoft HPC cluster, PSSH is not supported on Microsoft Windows for this operation.

  • PBS, LSF, UGE and TORQUE clusters on Windows are not supported.


Submitting Polyflow Jobs to RSM or an EKM Portal

  1. Configure your remote solution settings via Remote Solve Manager. If submitting jobs directly to Remote Solve Manager, see RSM Installation and Startup and RSM Configuration in the RSM User's Guide. If submitting jobs to Remote Solve Manager via an EKM Portal, see Integrating EKM with Remote Solve Manager (RSM) in the EKM Administration Guide.

  2. In ANSYS Workbench, right-click the Solution cell and select Properties. Select the Solution Process settings that you want to use for this solution and update the project.


Note:
  • You can Abort an update by right-clicking the Solution cell. This option is available during foreground, background, Portal and RSM updates.

  • Polyflow has the following limitations when used with Remote Solve Manager:

    • Reconnect will not work after moving a project to another machine.

    • Only one copy of a saved project that is in the pending state can reconnect successfully.

    • You must manually save a project after a reconnect.

    • The RSM Interrupt option performs an abort operation, not an interrupt.

    • Parallel design point submissions to batch queue clusters will only run on the master node and with the number of cores allocated by the batch queue scheduler.


Submitting Fluent Jobs to RSM or an EKM Portal

You can use this feature to queue multiple jobs to run on the local machine, such as overnight or during other low-usage times, and you can submit a job to remote machines.

  1. Configure your remote solution settings via Remote Solve Manager. If submitting jobs directly to Remote Solve Manager, see RSM Installation and Startup and RSM Configuration in the RSM User's Guide. If submitting jobs to Remote Solve Manager via an EKM Portal, see Integrating EKM with Remote Solve Manager (RSM) in the EKM Administration Guide.

  2. In ANSYS Workbench, right-click the Solution cell and select Properties. Select the Solution Process settings that you want to use for this solution and update the project.

    An update of the Solution cell submits the job to RSM or an EKM Portal, moves into Pending mode for the duration of the solution, and then automatically reconnects at the end of the run.


    Tip:  If you set Execution Mode to Parallel, you can specify the number of processes that you want to use to create the results file. You should specify a number that is less than or equal to the number of cores available in the cluster, and you should ensure that each process contains at least 100,000 nodes or elements.



Note:
  • You can Interrupt or Abort an update by right-clicking the Solution cell. These options are available during background, Portal and RSM updates.

  • Fluent has the following limitations when used with Remote Solve Manager:

    • Only one copy of a saved project that is in the pending state can reconnect successfully.

    • System Coupling is not supported.

    • UDFs are supported but you must have a supported compiler on Windows 64-bit machines. Supported compilers for Windows are Microsoft Visual Studio 2008 Standard and Microsoft Visual Studio 2010 Professional.

    • On Linux, UDFs are supported. You can always send UDFs between Linux machines and make use of the auto-compile feature; if the machines have compatible compilers, you can send precompiled UDFs.


For additional information about compiling Fluent UDFs, see Compiling UDFs in the Fluent Customization Manual.

Solution Properties: Use Setup Launcher Settings

The Properties view of the Fluent Solution cell has a toggle that controls whether the solution uses settings from the Setup Launcher. When Use Setup Launcher Settings is checked, the Launcher Settings are copied from Setup component to Solution component. This copying also happens any time you change the Launcher settings in setup. When Use Setup Launcher Settings is cleared, the Solution cell's Launcher settings are available:

General

Precision

Default: Single Precision

Applicable to RSM or EKM Portal: Yes

Show Launcher at Startup

Default: Enabled

Applicable to RSM or EKM Portal: No

Display Mesh After Reading

Default: Enabled

Applicable to RSM or EKM Portal: Yes

Embed Graphics Window

Default: Enabled

Applicable to RSM or EKM Portal: Yes

Use Workbench Color Scheme

Default: Enabled

Applicable to RSM or EKM Portal: Yes

Set up Compilation Environment for UDF

Default: Enabled

Applicable to RSM or EKM Portal: No

Use Job Scheduler

Default: Disabled

Applicable to RSM or EKM Portal: No

Run Parallel Version

Default: The initial default execution mode (Serial / Parallel) is based on the Run Settings. The initial 'Number of Processes' in RSM is based on the Number of Processors option in the run settings: if it is > 1, that value will be used, otherwise 2 will be used. If Run Parallel Version is not enabled, then Serial mode is forced.

Applicable to RSM or EKM Portal: Yes

UDF Compilation Script Path

Default: $(FLUENT_ROOT)\$(ARCH)\udf.bat

Applicable to RSM or EKM Portal: No

Use Remote Linux Nodes

Default: Enabled

Applicable to RSM or EKM Portal: No

Remote

Remote Polyflow Root Path

Default: none

Applicable to RSM or EKM Portal: No

Use Specified Remote Working Directory

Default: Enabled

Applicable to RSM or EKM Portal: No

Remote Working Directory

Default: none

Applicable to RSM or EKM Portal: No

Remote Spawn Command

Default: RSH

Applicable to RSM or EKM Portal: No

Use Remote Cluster Head Node

Default: Enabled

Applicable to RSM or EKM Portal: No

Remote Host Name

Default: none

Applicable to RSM or EKM Portal: No

Parallel Run Settings

Number of Processors

Default: 1

Applicable to RSM or EKM Portal: No

Interconnect

default

Applicable to RSM or EKM Portal: No*


Note:  * You can enable Interconnect to be available for Polyflow RSM runs by enabling Tools > Options > Solution Process > Show Advanced Solver Options. This setting requires you to ensure that the remote Compute Servers can accept the Interconnect that you specify—there is no automatic checking for such compatibility.

To learn what values are available, see Starting Parallel ANSYS Fluent on a Windows System Using Command Line Options in the Fluent User's Guide.


MPI Type

default

Applicable to RSM or EKM Portal: No*


Note:  * You can enable MPI Type to be available for Polyflow RSM runs by enabling Tools > Options > Solution Process > Show Advanced Solver Options. This setting requires you to ensure that the remote Compute Servers can accept the MPI Type that you specify—there is no automatic checking for such compatibility.

To learn what values are available, see Starting Parallel ANSYS Fluent on a Windows System Using Command Line Options in the Fluent User's Guide.


Use Shared Memory

Default: Disabled

Applicable to RSM or EKM Portal: No

Machine Specification

Default: (file containing the machine list)

Applicable to RSM or EKM Portal: No

Machine Filename

Default: none

Applicable to RSM or EKM Portal: No

The Solution cell's Solution Process setting is always displayed; when Use Setup Launcher Settings is checked, the option is read-only:

Solution Process

Update Option

You can choose to Run in Foreground, Run in Background, Submit to Portal, or Submit to Remote Solve Manager. When Submit to Remote Solve Manager or Submit to Portal is chosen, options that are not applicable to RSM/Portal are hidden. Also, fluentlauncher.txt will not contain options that conflict with RSM.

Submitting Fluent Jobs to a Cluster via RSM or an EKM Portal

If you have a Microsoft HPC, PBS, LSF, UGE or TORQUE queue available, you can use that as a parallel solution option. In the Solution Processes pane:

  1. Set the Update Option to Submit to Remote Solve Manager or Submit to Portal.

  2. Set the RSM Queue or Queue, as appropriate.

  3. Set the Execution Mode to Parallel.

  4. Set the Number of Processes to the number of partitions desired[2]. The cluster job scheduler automatically controls where the partitions are solved.

Refer to the following sections in the Remote Solver Manager User’s Guide for details on defining cluster configurations in RSM, and configuring a cluster:


Note:
  • For a Microsoft HPC cluster, PSSH is not supported on Microsoft Windows for this operation.

  • PBS, LSF, UGE and TORQUE clusters on Windows are not supported.


Submitting Icepak Jobs to RSM

You can use this feature to queue multiple jobs to run on the local machine, such as overnight or during other low-usage times, and you can submit a job to remote machines.

  1. Configure your remote solution settings via Remote Solve Manager. See RSM Installation and Startup and RSM Configuration in the RSM User's Guide.

  2. In ANSYS Workbench, right-click the Solution cell and select Properties. Select the Solution Process settings that you want to use for this solution.

    An update of the Solution cell submits the job to RSM, moves into Pending mode for the duration of the solution, and then automatically reconnects at the end of the run.


    Tip:  If you set Execution Mode to Parallel, you can specify the number of processes that you want to use to create the results file. You should specify a number that is less than or equal to the number of cores available in the cluster, and you should ensure that each process contains at least 100,000 nodes or elements.


  3. Under Solution Process:

    • If solving in serial, enable Serial for Execution Mode.

    • If solving in parallel, select Parallel for Execution Mode and enter the number of processes in the text field below, across from Number of Processes.


  4. Note:  RSM updates Icepak with Convergence plot data at the Progress Download Interval specified in Workbench. Set the Progress Download Interval as needed prior to starting the solution.


    Update the project. An update of the Solution cell submits the job to RSM, moves into Pending mode for the duration of the solution, and then automatically reconnects at the end of the run. To re-run a solution with the same model, run another solution in the same project, or run a restart solution, right-click the Setup cell in Workbench and select Enable Update.


Note:
  • You can Interrupt or Abort an update by right-clicking the solution in the Workbench Job Monitor. These options are available during background and RSM updates. To display the Job Monitor, select Jobs > Open Job Monitor.

  • Icepak has the following limitations when used with Remote Solve Manager:

    • You cannot submit jobs containing parametric trials to RSM.

    • Convergence data is not plotted in Icepak on the local computer. The .res and .uns_out files are written at the frequency specified in RSM settings. You must open them in Icepak to view them.


Exiting a Project During an RSM Solution Cell Update

You can exit a project while a Solution cell update via RSM is in progress (that is, one or more RSM jobs are running in the background and the Progress view displays a project Status of Waiting for background task).


Note:  You cannot exit Workbench while job files are being uploaded. You can abort the job during the upload, however, by using the Stop button in the Progress bar.


In order for RSM jobs to continue to run after you exit the project, the project must be saved at least once after the Solution cell update job was initiated.

If you attempt to exit a project while a Solution cell update job is still running, the following scenarios will cause a dialog to display, allowing you to specify whether you want to save the project before exiting:

  • You have never saved the project at any time after the same Solution cell update job was initiated.

  • You have saved the project at least once after the same Solution cell update was initiated, but results have been retrieved since your last Save.

In either of these cases, if you do not save the project before exiting: 

  • All results retrieved since the last Save operation will be lost. You must save the project before exiting if you want to keep any of results retrieved since the last save of the background Solution cell update.

  • If the project has never been saved after the Solution cell update job was initiated, all RSM jobs will be aborted and will show a Status of Cancelled and the Cancelled icon ( ) in the RSM List view; the asterisk on the icon indicates that the job has also been released. When you reopen the project, it will be in the state of your last manual save.

  • If the project has been saved at least once after the Solution cell update job was initiated, RSM jobs that are queued and running will continue to run after you exit. When you reopen the project, you can resume the update of the pending jobs to reconnect and download the results.

If you do save the project before exiting: 

  • Retrieved results will be saved to the project.

  • RSM jobs that are queued and running will continue to run after you exit.

  • Jobs for which the results have been saved will show a Status of Finished and the Finished icon ( ) in the RSM List view; the asterisk on the icon indicates that the job has also been released.

  • Jobs for which results have not yet been saved are not released upon exit. When you reopen the project, you can resume update of the pending jobs to reconnect and download the results.



[2] You should have at least 100,000 elements or nodes per partition to compensate for the overhead associated with the partition.


Release 18.2 - © ANSYS, Inc. All rights reserved.