When you select the option for the Solution Execution Target and solve, your solution is submitted to the Ansys Cloud capability. In order to use this capability, you must sign-in and have the necessary customer account. Given sign in and account access, selecting the context (right-click) menu option, , on the Solution object opens the web interface so that you can review and manage the job(s).
Go to a section topic:
Requirements
To solve remotely using the Ansys Cloud, your company must subscribe to an Ansys Cloud plan. Each plan includes a pool of cloud compute credits and provides cloud access to a limited number of users. Your company's Ansys administrator manages cloud user access in the Ansys Admin portal at https://admin.ansys.com/. For more information, refer to the Ansys Admin Guide.
To solve remotely using the Ansys Cloud, you need:
Ansys ID (initially created during sign-in).
Membership in an Ansys Cloud plan created by your administrator.
Assignment of a cloud user seat.
Assignment of a Burst seat.
Sufficient credits available in your company pool.
Use the Ansys Cloud (https://portal.ansys.com) to gain access to the web interface capability and view and manage simulation jobs that you submitted to the Ansys Cloud. For more information, see the Ansys Portal Guide.
Note: If you have an ASC or Admin role in the Ansys Admin portal, see the Ansys Cloud Subscription Quick Start Guide for instructions on setting up your Ansys Cloud plan.
Limitations
Note that is:
Only available using the Windows platform.
Only supported for the solver.
Not supported for the , , and solvers.
Not supported for the following analysis types:
Additive Manufacturing
Structural Optimization
Condensed Geometry (Generation Pass)
Rigid Dynamics
Motion
Supported Linked Analysis Types
Without needing to download the results of the upstream system, Cloud Burst Compute currently supports the following linked analyses:
Mode Superposition analyses: Mode Superposition Harmonic Response, Transient, Random Vibration, and Response Spectrum (including Prestress)
Prestress Modal
Prestress Full Harmonic Response
Prestress Eigenvalue Buckling
Prestress Coupled Field Modal and Coupled Field Harmonic
Static Acoustics and Modal Acoustics
Static Acoustics and Harmonic Acoustics
Synchronous Submissions
When you initiate a solve on a downstream system or at the Model level of a system, the application submits all the jobs for the linked systems synchronously, even if the upstream system has not completed its solution. All jobs in the Cloud Burst Compute queue process in order. Because the application does not wait to submit all jobs for linked systems, you can close the application once all jobs have been submitted to conserve your license for other purposes.
Furthermore, the application automatically determines whether it needs to wait for upstream systems to complete. This eliminates the need for you to monitor the process.
Limitations of Synchronous Submissions
The synchronous submission process is not supported if an analysis includes any of the following:
Spot Welds
Bolt Pretension
Weak Springs
EM Transducer loading condition
Command (APDL) objects
Contact Splitting
These features and capabilities may require the application to create additional elements or nodes during the solution process. As a result, Mechanical would need to wait for upstream jobs to complete in order to receive the necessary data for the downstream jobs.
Downloading Upstream Results
Cloud Burst Compute also supports the following types of linked analyses for which the upstream results are required to be downloaded. In such cases, the upstream results are automatically downloaded before submitting the downstream analysis to Cloud Burst Compute.
Analyses involving imported loads from the upstream system such as Steady-State Thermal and Static Structural systems and Electric Conduction and Steady-State Thermal systems.
Steady-State Thermal and Transient Thermal systems.
Note:
If you are performing the upstream and downstream analyses on different Cloud Burst Compute servers, make sure to download the results of the upstream system before submitting the downstream system. However, we recommend submitting the linked systems to the same server to take advantage of the file referencing capabilities of Cloud Burst Compute.
When you initiate a solve on a downstream system or at the Model level of a system, and you abort the job or the job fails, all jobs currently running or that are pending stop automatically.
Recommendation: As stated above, you can close the application after all systems have been submitted. However, if your simulation includes systems that must wait for upstream processes to complete, and/or the results to be downloaded, it may take some time for the last system to be submitted. In this instance, you may want to submit the jobs individually if the application needs to be closed during the solution process.