ANSYS, Inc. Release Notes
ANSYS, Inc. Release Notes
The following enhancements have been made to the Remote Solve Manager (RSM) in release 14.0.
Remote Solve Manager now provides Batch Queue support for FLUENT, CFX, and ANSYS Mechanical APDL. For solutions that will be submitted to RSM, the solver Properties view now allows you to specify remote execution options. Except where otherwise noted, these solvers now support the following modes of execution on remote queues:
Serial
Shared memory parallel
Distributed parallel on Linux clusters via PBS and LSF, and on Windows clusters via Windows HPC and LSF
CFX also has extended support for CFX external files (e.g., BC profiles, .csv variables, etc.). See Using Remote Solve Manager with ANSYS CFX in the CFX documentation for a complete list of which files are and are not supported.
Limitation: In release 14.0, RSM does not support Windows clusters via LSF for the submission of FLUENT solutions.
When you submit Batch Queue jobs via Remote Solve Manager, you can now specify that you want to store solver files in local directory on the Compute Server machine (i.e., in a local “scratch” directory on the execution node), rather than in the shared cluster directory that serves as the central RSM file-staging directory. By using a local directory on the execution node, you could optimize performance by reducing the need to copy files. The location in which solver files are stored is controlled by the File Management property of the Compute Server Properties dialog.
Limitation: Note that this option is not available if you are sending CFX jobs to a Microsoft HPC Compute Server; in this case, the shared cluster directory is always used.
You now have the option to retain temporary RSM job files created in the Working Directory on the Compute Server. In the release, the General tab of the redesigned Compute Server Properties dialog includes a new Delete Job Files in Working Directory property that allows you to specify whether the temporary job files will be saved or deleted upon completion of the associated job. You can save these temporary job files and use them for troubleshooting purposes.
Modifications to the RSM installation and initialization scripts for Linux allow you to install RSM services and configure them as daemons (i.e., to start up automatically when the machine is booted). Once the RSM daemon services are installed, they can be configured so that non-root users can run, stop, and restart them.
For more information, see Starting RSM Services Automatically at Boot Time for Linux in the Remote Solve Manager documentation.
In the Parameter Set Properties view, use the new Default Job Submission property to specify how design points sent to Remote Solve Manager for update will be submitted. Submission options are as follows:
One Job for All Design Points: All design points being sent for update are submitted as a single job.
One Job per Design Point: Each design point being sent for update is submitted as a separate job.
Specify Maximum Number of Jobs: Design points being sent for update are distributed among and submitted in multiple jobs, up to the maximum number of jobs specified.
For more information, see Updating Design Points via Remote Solve Manager (RSM) in the Workbench User’s Guide.
Note: | The failure of design points to update or merge back into the project will not affect any design points that updated and merged successfully. If you encounter any failed design points, simply resubmit those design points for updating. When submitting design points as separate jobs using this release, you may encounter occasional failures with the design point updates. These failures are most likely to occur if submitting design points from a DesignXplorer design exploration system and generally occur when ANSYS Workbench attempts to merge the results back into the project. |
You can now submit Design Point updates to RSM from DesignXplorer (DX). The Pending state is also now supported for DX, which means if you submit a design point update to RSM from DX, you can continue interacting with the project on a limited basis and can view intermediate results of individual design point updates via the Table of Design Points while the remote update is in progress. Additionally, if you exit the project, when you reopen it the Resume button allows you to resume the update.
For additional information, see Using Remote Solve Manager with DesignXplorer in the DesignXplorer help.
In this release, the new Pre-RSM Foreground Update property in the Parameter Set Properties view allows you to update the geometry locally before submitting design points to RSM. This feature enables remote update of design points in situations where remote machines do not have access to CAD software, or sufficient licenses for CAD, CAD connections, or geometry components. It also allows you to interrupt an update earlier in the process if failures are found during geometry update. Output files for the geometry update for all design points are then retained and reused for the remainder of the design point updates.
This functionality is available for RSM remote server machines on which both Workbench and necessary CAD software have been installed.
For more detailed information on geometry-only design point updates, see Solution Process or Updating Design Points via Remote Solve Manager (RSM) in the Workbench User’s Guide .
The Compute Server Properties dialog has a new, more intuitive design, allowing you to configure and administrate RSM more easily. The Compute Server Properties dialog now offers a three-tab design (with General, Cluster, and SSH tabs), context-sensitive help, a clearer presentation of options, and properties that have been modified to enhance clarity and ease of use.
For more information, see Adding a Compute Server in the Remote Solve Manager help.
There have been significant revisions to the Installation and Configuration section and the Appendices of the Remote Solve Manager help. The instructions have been updated, consolidated where possible, and reorganized for clarity and ease of use.
UDFs are now supported for Solution Update via RSM, with the following limitations:
Automatic compilation of UDFs (when submitting to a host with different operating system or architecture) requires that the UDF directory be in the same location as the case data within the project directory structure.
Automatic compilation of UDFs also requires that a suitable compiler be installed on the remote system, and that the remote system environment be configured so that the compiler can be located. See the compiler documentation.
Submission of Fluent via RSM to a LSF batch queue is supported on Linux only.