As trends push products to become more complex, engineers will need multiphysics simulations to optimize their designs.
The same trends will also increase the size and complexity of multiphysics simulations. As a result, engineers require access to high-performance computing (HPC) resources that easily and efficiently solve these large simulations.
With the release of Systems Coupling 2.0 (SC 2.0) in ANSYS 19.2, engineers have the choice of setting up their simulations though a script-based workflow or with the traditional graphical user interface (GUI).
The script-based workflow gives engineers the flexibility of customizing simulations without the additional overhead of file transfers or the GUI. By reducing this overhead, engineers can increase productivity as they work on larger multiphysics simulations.
When to Use Script-based Workflows
The ANSYS platform offers engineers a GUI to set up complex multiphysics simulations. The initial setup of the simulation and changes to the geometry or mesh are best made in the GUI.
After the initial setup, many users prefer to decouple their simulations from the GUI. At this point, they can customize their simulation through their run-time environment such as an HPC cluster or cloud.
Throughout a product development lifecycle, engineers will make numerous changes to their simulation settings (such as timesteps, loads and data transfers). These changes can be done efficiently and automatically using a script-based workflow. This is especially true for users that do not have visualization capabilities on their cluster.
SC 2.0 enables engineers to choose the best workflow (GUI or script-based) for the given situation.
Given the size and complexity of multiphysics simulations, script-based workflows offer a considerable boost in productivity.
Script-based Workflows Access the ANSYS Command Line
With the script-based feature of SC 2.0, users can define their simulation settings from a command line interface or place their settings into a Python file. The users then run the coupled simulation by sending it to the scheduler.
Users are also allowed to export initial settings from a simulation setup in the GUI. They can then modify it in a script file.
Script-based workflows can make it faster for engineers to submit their simulations to the cluster. They also give engineers more control and flexibility to automate workflows.
For instance, users can define the names and folders of output or temporary files. This can speed up the simulation by minimizing the file/data management of the result.
Users can even add logic to the command line script. For instance, you can set the timestep to change automatically based on given outputs from the simulation.
The output log file also gives users more information to help them control their simulations. As an example, the log file reports the runtime of each solver. This extra information can help users optimize resources.
How System Coupling 2.0 Makes Multiphysics Easier
Script-based workflows and updates to the command line aren’t the only way SC 2.0 makes it easier to work with large multiphysics simulations.
The updated coupling engine also allows users to connect 20 solvers.
Additionally, SC 2.0 is compatible with polyhedral meshes, giving users the freedom to choose the element type best-suited for their problem.
To learn more about coupling simulation solvers, look up ANSYS Multiphysics Simulation software.