ANSYSEM: Computer-aided engineering software for electromagnetic systems

Contents

  1. Overview of package
  2. Overview of package
    1. General usage
  3. Availability of package by cluster
  4. Using the GUI on the HPC cluster
  5. Submitting batch jobs

Overview of package

General information about package
Package: ANSYSEM
Description: Computer-aided engineering software for electromagnetic systems
For more information: http://www.ansys.com
Categories:
License: Proprietary

General usage information

Ansys Electromagnetic Suite is a suite of software for engineering analysis for electrical and electronic products.

AnsysEM is not supported on RHEL8. A singularity container provides the products on a CentOS7 platform.

To start the main GUI, do: singularity run \$SINGULARITY_IMAGEFILE Other AnsysEM executables are accessed via: singularity exec \$SINGULARITY_IMAGEFILE program_name

**************************************************** NOTE **************************************************** This is restrictively licensed software. It is currently being made available on the UMD Deepthought HPC clusters by the generosity of the Dept of Mechanical Engineering.

Available versions of the package ANSYSEM, by cluster

This section lists the available versions of the package ANSYSEMon the different clusters.

Available versions of ANSYSEM on the Deepthought2 cluster (RHEL8)

Available versions of ANSYSEM on the Deepthought2 cluster (RHEL8)
Version Module tags CPU(s) optimized for GPU ready?
21.1 ansys-em/21.1 x86_64 Y
20.2 ansys-em/20.2 x86_64 Y

Available versions of ANSYSEM on the Juggernaut cluster

Available versions of ANSYSEM on the Juggernaut cluster
Version Module tags CPU(s) optimized for GPU ready?
20.2 ansys-em/20.2 x86_64 Y

Available versions of ANSYSEM on the Deepthought2 cluster (RHEL6) [DEPRECATED]

Available versions of ANSYSEM on the Deepthought2 cluster (RHEL6) [DEPRECATED]
Version Module tags CPU(s) optimized for GPU ready?
19.5 ansys-em/19.5 x86_64 N
a name="gui">

Using the Ansys EDT GUI on the HPC cluster

Although generally it is preferable to do production runs in batch mode, as discussed in the next section, it is sometimes useful to invoke the Ansys EDT GUI. This is particularly useful for setting up/designing the simulation.

Running graphical applications on the HPC cluster so that the display goes back to the workstation you are sitting at can be tricky. The easiest solution is to use the interactive desktop applet in the OnDemand portal. This will start a job on the cluster which presents a full graphical desktop to you through your web browser. You can then open a terminal window, module load ansys-em and invoke the ansysedt to start the GUI. Note that it can take a while (on order of 10 minutes) to start up the first time. Once it starts up, you can design your job and or run it on the compute node assigned to the desktop (as it is a compute node, not a login node, you are allowed to perform computationally intensive tasks.)

Alternatively, you can start the GUI on a login node with display sent back to an X server on your workstation. You need to have an X server running on the workstation where you are sitting (see the section on Graphics for more information). As this runs on the login nodes, you are not allowed to do anything real computations there, and memory will be restricted.

In both cases, it is assumed that you are going directly from the workstation at which you are seated to the OnDemand portal/login node. Going through another layer of remote connection can cause problems.

Submitting batch jobs

For production runs it is generally best to run Ansys EDT in batch mode. This also has the benefit of allowing one to use multiple CPU cores across multiple nodes using the Ansys RSM service. This section assumes you already have an ansys project file (.aedt file), often created from the GUI. You can then submit it with a Slurm/sbatch job submission script similar to this sample script ansys-em_job.sh.

This job script sets the environmental variable PBS_JOBID to the Slurm job id (SLURM_JOBID) and generates an appropriate batch options file. It then proceeds to invoke ansysedt on the MyProject.aedt project file. You will want to adjust the walltime and number of cores/nodes/etc requested, as well as the name of the input .aedt in the script.