Updating Design Points via ANSYS Remote Solve Manager or an EKM Portal

If an administrator has defined cluster configurations in ANSYS Remote Solve Manager (RSM) such that RSM queues are available in Workbench, you can submit design point updates to RSM. Cluster configurations enable RSM to integrate with established compute clusters, providing you with access to powerful compute resources when needed. For information on setting up RSM, see RSM Configuration in the RSM User's Guide.

Similarly, if you have access to an EKM Portal, and have created and opened a connection to it, you can submit the design point update to the EKM Portal for execution. EKM then dispatches the task to RSM, which sends it to the cluster submit host for scheduling. For information on submitting design point updates to RSM via an EKM Portal, refer to Integrating EKM with Remote Solve Manager (RSM) in the EKM Administration Guide.


Important:
  • If you are sending design point update jobs to a remote computing cluster, note that the license preferences set for your local machine (the RSM Client) may not be the same as the license preferences set for the remote cluster. In this case, the cluster license preferences will be used for all jobs. For more information, see Establishing User Licensing Preferences.

  • When design points are configured to be updated via RSM or an EKM Portal, the Solution cell cannot also be updated via RSM. In order to update design points via RSM, change the Solution cell update settings by setting the Update Option property to Run in Foreground. For further information about tutorials and documentation on the ANSYS Customer Portal, go to http://support.ansys.com/docinfo. Note that the update of both the Solution cell and design points via an EKM Portal is not supported. If both are submitted to the EKM Portal, the Solution cell update will automatically switch to Run in Foreground when the design points are being updated through the EKM Portal.


To update design points via RSM or an EKM Portal:

  1. Right-click the Parameter Set bar and select Properties to view the Design Point Update Process settings. If the Properties view is already visible, click the Parameter Set bar to refresh the Properties view with the design point settings.

  2. In the Properties view, specify the Design Point Update Process settings. These settings are initially populated based on your selections in Tools > Options > Solution Process. For more information, see Solution Process. You can choose different settings here if the default settings are not appropriate. For design points to be updated via RSM, set Update Option to Submit to Remote Solve Manager and then specify an available RSM Queue. For design points to be updated via an EKM Portal, set Update Option to Submit to Portal and then select a Portal Connection and Queue. If no connections are listed, you may need to create a connection or open an existing connection.

  3. For the Job Submission property, select one of the following options:

    • One Job for All Design Points: All design points are submitted as a single job to RSM.

    • One Job for Each Design Point: Each design point is submitted as a separate job to RSM (simultaneous parallel updates).

    • Specify Number of Jobs: Design points are divided into groups and submitted in multiple jobs, up to the specified maximum number of jobs. You can look at the RSM List view to determine which design points are assigned to each job. If you select this option, the Number of Jobs property is enabled, allowing you to specify the maximum number of jobs that can be created.


      Note:  The maximum number of jobs that can actually be run on the cluster is determined by the cluster’s resource management system.


  4. For the License Checkout property, select one of the following options:

    • On-demand: Licenses are checked out on demand. If licenses are unavailable, the update will not proceed.

    • Reserved: Enables you to reserve licenses to ensure that you have sufficient licenses available for the duration of your design point study. When you select this option, a Select Licenses option becomes available, enabling you to select the licenses to reserve.

      For more information, see Reserving Licenses for a Design Point Update.

  5. For the Component Execution Mode property, select one of the following options:

    • Serial: All components participating in the update are to run in serial mode.

    • Parallel: All components participating in the update that support this setting are to run in parallel mode.

    If you select Parallel:

    • The Number of Processes property allows you to specify the number of processes to be used in the solver for each job in the update. For jobs being sent to a cluster, the value entered for this property also determines how many cores are allocated on the cluster for each job. Note that resource allocation is determined by the cluster's resource management system.

    • RSM considers each design point update job as a single job, although the component will use more resources.

    Submitting a design point update to RSM is supported by the Solution (or Analysis) component update for the Mechanical APDL, Mechanical, Fluent, CFX and Polyflow solvers. These settings override any parallel or serial settings defined at the component level. When updating a component, system, or project, the Parameter Set properties for a design point update are ignored. The product specific settings that are overridden for a design point update via RSM are listed below.

    • For CFX:

      The following properties for the CFX-Solver Manager or CFX-Pre Solution cell are ignored for a design point update via RSM:

      • All settings under the Parallel Environment tab.

        Run mode
        All host information and partition weighting
    • For Fluent:

      The following properties for the Fluent Solution cell are ignored for a design point update via RSM:

      • Use Job Scheduler

      • Run Parallel Version

        (Visible under Parallel Run Settings when RPV=True)
        Number of Processes
        Use Shared Memory
        Machine Specification (visible when USM=false)
        Machine List (visible when USM=false)

        Notable exceptions in the parallel run settings group are the following properties whose effects remain enabled if set in all situations.

        Interconnect
        MPI Type
    • For Mechanical:

      The following properties in the Advanced section of a Mechanical Solve Process Setting are ignored for a design point update via RSM:

      • Distributed Solution (if possible)

      • Max number of utilized cores

    • For Mechanical APDL:

      The following properties for the Mechanical APDL Analysis cell are ignored for a design point update via RSM:

      • Processors

      • Distributed

      • MPI Type

      • Machine list

    • For Polyflow:

      The following properties in the Polyflow Options accessed via Solution cell preferences are ignored for a design point update via RSM:

      • Number of Processes


    Note:  The Component Execution Mode and Number of Processes settings are applied to all components participating in the update but can be overridden by component-level settings. This is described in an upcoming step.


  6. For the Retained Design Point property, select one of the following options:

    • Update parameters (default): Only parameters are updated for retained design points. If a component is not needed to get the value of an output parameter, it is not updated.

    • Update full project: Full project is updated for retained design points. Use this setting if you want to generate reports, or other content, from components that do not produce output parameters.

  7. Design point updates to RSM include component override settings for individual systems using the Solution or (Analysis) component for Mechanical APDL, Mechanical, Fluent, CFX and Polyflow systems. These settings override the Component Execution Mode and Number of Processes defined for the Parameter Set bar.

    Before updating a component:

    1. Right-click the Solution or (Analysis) component to expose the properties information.

    2. Under Restriction for Design Point Update Via RSM:

      • If solving in serial, enable Serial Execution Only.

      • If solving in parallel, enable Specify Number of Processes Restriction and enter the number of processes in the text field across from Number of Processes Used Not to Exceed.


    Note:  These settings override the serial or parallel settings for only this specific system.


    • For Mechanical APDL and Mechanical, if solving in parallel, enable Specify Number of Processes Restriction, enter the number of processes in the text field across from Number of Processes Used Not to Exceed and enable Shared Memory Parallel.


      Note:  Shared Memory Parallel allows jobs to strictly run in parallel on the master node. It does not run jobs in distributed parallel.


  8. To update your geometry locally prior to submitting design point updates to RSM, set Pre-RSM Foreground Update to Geometry.

    If you are using reserved licensing feature to send design point updates to RSM, you can specify whether or not your pre-RSM geometry update is to use reserved licenses. For more information, see Performing a Pre-RSM Geometry Update.

  9. Save the project. If you are working in an archived project, you must save the project to a permanent location.

  10. Initiate the update of the desired design points. For more information, see Updating Design Points. The project is archived, submitted to a cluster via RSM. The remote data is retrieved periodically as the design point updates complete. Should a design point update fail, an error is reported to the Messages view.

When updating design points via RSM, each output parameter that was out-of-date when the design point update was initiated is shown in a pending state ( ) in the design points table. ANSYS Workbench periodically queries RSM and refreshes any design point updates that have completed since the previous query. Design point updates that have not yet completed continue to be shown in a pending state.

Design points that have been updated via RSM need to be reintegrated into the project as the updates complete. To ensure the integrity of the data, ANSYS Workbench restricts or disables several GUI operations during pending RSM design point updates:


Note:  If you have updated design points remotely via a queuing system for RSM, information on the reserved licenses is available to the job scripts in the ANSYS_RESERVED_LICENSE_INFO environment variable.


Related Topics:

Performing a Pre-RSM Geometry Update

You can update your geometry locally before submitting design point updates to RSM. You would want to do this when:

  • Design points are to be updated simultaneously via RSM. The geometry update infrastructure does not support simultaneous design point updates in the same source geometry.

  • The compute cluster cannot perform geometry updates.

To perform the local geometry update before design point submission:

  1. Configure whether to use reserved licensing.

    If you are using reserved licensing to send design point updates to RSM, you can specify whether or not a pre-RSM geometry update is to use a reserved license. By default, a DesignModeler license is checked out of the reserved license pool for the pre-RSM geometry update. To specify that a reserved license is not needed, in the Parameter Set properties, clear the check box for reserving licenses for the pre-RSM update. A DesignModeler license is checked out in the standard manner, rather than from the reserved license pool. The license is released once the geometry update is completed. For more information, see Reserving Licenses for a Design Point Update.

  2. Set Pre-RSM Foreground Update to Geometry.


Note:  If the project includes a Geometry component and you have set Default Job Submission to either One Job per Design Point or Specify Number of Jobs (with Number of Jobs set to a value greater than 1), ANSYS Workbench ignores the setting for Pre-RSM Foreground Update. The geometry is updated locally in the foreground before your design points jobs are sent to RSM.


Aborting or Interrupting an RSM Design Point Update

You can abort or interrupt an RSM update that is in progress. In the Progress view, while the Status column displays the message Waiting for background task, click the stop button ( ) in the Progress column. You are prompted to either abort or interrupt the update. You can also choose cancel to close the dialog box.

  • To stop the RSM job and return no data to the project, click Abort.

  • To interrupt the RSM job and return any available data to the project, click Interrupt.

Exiting a Project during an RSM Design Point Update

You can exit a project while an RSM design point update is in progress. During the update, while the one or more RSM jobs are running in the background, the Progress view displays a project Status of Waiting for background task.


Note:
  • If you have submitted the Update All Design Points operation via RSM and are unable to exit the project because Workbench remains busy, see Suspending and Resuming Collection of RSM Design Point Results.

  • You cannot exit Workbench while job files are being uploaded. However, you can abort the job during the upload by clicking the stop button ( ) in the Progress bar.


For RSM jobs to continue to run after you exit the project, the project must be saved at least once after the design point update job was initiated.

If you attempt to exit a project while a design point update job is still running, the following scenarios cause a dialog box to open, 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 design point update job was initiated.

  • You have saved the project at least once after the same design point update was initiated, but design point results have been retrieved since your last save.

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

  • All design point results retrieved since the last Save operation are lost. However, if the project has been saved at least once since the update job was initiated, the results can be retrieved again when the project is reopened.

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

If you do save the project before exiting: 

  • Retrieved design point results are saved to the project.

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

  • Jobs for which the results have been saved show a Status of Finished. The finished icon ( ) displays 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.

Suspending and Resuming Collection of RSM Design Point Results

When the Update All Design Points operation has been submitted via RSM, Workbench may stay too busy collecting intermediate and final results to allow you to exit the session. To pause the data collection so you can exit the Workbench session, select Tools > Suspend Collection of RSM Results.

When you exit the project, results are saved according to the criteria described in Exiting a Project during an RSM Design Point Update.


Note:  The Suspend Collection of RSM Results option is also available during a project update via RSM. However, because only the current design point is being updated and RSM collects results only at the end of the update process, this option has no impact on the project update.


To resume the collection of design point data, select Tools > Resume Collecting RSM Results. The project reopens in the same state it was in when it closed. Once all the design points have been updated, all of the suspended results are collected and then updated to the project at the same time.

It is not necessary to use the Resume Collecting RSM Results option. The collection and update happen automatically when all jobs have been completed.

Product-Specific Limitations

Some products have additional limitations when submitting design points updates via RSM:

Ansoft

Projects that include Ansoft systems return updated parameter values but do not return the detailed solution for the current design point.

Mechanical

Design point updates via RSM can fail for a class of problems (typically involving a Structural system linked to a Modal or other type of Mechanical system) that meet the following criteria:

  • A non-parameterized upstream Mechanical system provides solution data to a parameterized downstream Mechanical system and both systems share the same geometry/model.

  • Updates are performed via a pre-RSM local update.

The parameters for some of the design points are not computed and are marked as errors in the design points table.

Workarounds:

  • Select the Enable Legacy Solve check box (Tools > Options > Mechanical).

  • In the Parameter Set properties, set Pre-RSM Foreground Update to None and Job Submission to One Job for All Design Points.

Rigid Body Dynamics and Explicit Dynamics

Rigid Body Dynamics and Explicit solvers always use RSM for update of the Solution, so it is not possible to update design points via RSM until special steps have been taken to enable update of a Solution via RSM within design point update via RSM. For assistance with enabling this functionality and configuring your system to support, go to the Support page of the ANSYS Customer Portal and submit an online support request. For further information about tutorials and documentation on the ANSYS Customer Portal, go to http://support.ansys.com/docinfo.

Third-Party CAD Systems

Projects that include geometry parameters that rely on third-party CAD systems do not update the geometry unless the CAD system is accessible on the execution node.


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