Hprc banner tamu.png


Revision as of 14:31, 1 November 2017 by Rodriguez.dylan (talk | contribs) (Access)
Jump to: navigation, search



ANSYS Workbench simulation software enables organizations to confidently predict how their products will operate in the real world. - Homepage: http://www.ansys.com/Products/Platform


ANSYS Workbench is open to all HPRC users when used within the terms of our ANSYS license agreement.


   Use of ANSYS is only permitted for users that are affiliated with Texas A&M at 
   College Station.  Users meeting this criteria are permitted to use ANSYS on HPRC 
   systems from anywhere in the United States (including Alaska and Hawaii).  Use 
   of this software outside the designated area represents a breach of the license 
   and any users caught  doing so may be subject to account suspension and/or other action.

If you have particular concerns about whether specific usage falls within the TAMU HPRC license, please send an email to the HPRC Helpdesk. Usage of ANSYS Workbench is restricted by the number of available tokens. To see the number of available tokens, use the License Checker Tool.

Loading the Module

To see all versions of ANSYS available on Ada:

 [netID@cluser ~]$ module spider ANSYS

To load a particular version of ANSYS on Ada (Example: 17.1):

 [netID@cluser ~]$ module load ANSYS/17.1

Known Issues

There is a known issue when using the Ansys GUI for any version of Ansys. The Geometry Editor in the Ansys Workbench will not run properly without also loading an NVIDIA module.
To bypass this bug, load the OpenGL/NVIDIA module before running the Ansys Workbench:

[ netID@cluster ~]$ module load OpenGL/NVIDIA

There is a known issue with all Ansys versions on Terra that requires unsetting a Slurm environment variable. To prevent this error, please make sure to have the following line in your job script before the launch command.


The same error occurs when using the Ansys GUI in a VNC job on Terra. To prevent this error, please use the following command in your VNC job:

[ netID@terra ~]$ unset SLURM_GTIDS

Usage on the Login Nodes

Please limit interactive processing to short, non-intensive usage. Use non-interactive batch jobs for resource-intensive and/or multiple-core processing. Users are requested to be responsible and courteous to other users when using software on the login nodes.

The most important processing limits here are:

  • ONE HOUR of PROCESSING TIME per login session.
  • EIGHT CORES per login session on the same node or (cumulatively) across all login nodes.

Anyone found violating the processing limits will have their processes killed without warning. Repeated violation of these limits will result in account suspension.
Note: Your login session will disconnect after one hour of inactivity.

Usage on the VNC Nodes

The VNC nodes allow for usage of the a graphical user interface (GUI) without disrupting other users.

VNC jobs and GUI usage do come with restrictions. All VNC jobs are limited to a single node (Terra: 28 cores/64GB). There are fewer VNC nodes than comparable compute nodes.

For more information, including instructions, on using software on the VNC nodes, please visit our Terra Remote Visualization page.

Running the ANSYS Workbench GUI

While in a VNC job, use runwb2 (with vglrun) to start the ANSYS GUI:

 [netID@gpu ~]$ vglrun runwb2

ANSYS Workbench GUI Quick Start Guide

For moderately detailed instructions on launching the ANSYS Workbench GUI for the first time, please see the ANSYS Workbench Quick Start Guide.

Usage on the Compute Nodes

Non-interactive batch jobs on the compute nodes allows for resource-demanding processing. Non-interactive jobs have higher limits on the number of cores, amount of memory, and runtime length.

For instructions on how to create and submit a batch job, please see the appropriate wiki page for each respective cluster:

Ada Example

Example 1: A serial (single core) Workbench Job example:

#BSUB -J WorkbenchJob1       # sets the job name to WorkbenchJob1.
#BSUB -L /bin/bash           # uses the bash login shell to initialize the job's execution environment.
#BSUB -W 5:00                # sets to 5 hours the job's runtime wall-clock limit.
#BSUB -n 1                   # assigns 1 core for execution.
#BSUB -R "span[ptile=1]"     # assigns 1 core per node.
#BSUB -R "rusage[mem=5000]"  # reserves ~5GB per process/CPU for the job 
#BSUB -M 5000                # sets to ~5GB the per process enforceable memory limit.
#BSUB -o stdout1.%J          # directs the job's standard output to stdout1.jobid 

## Load the necessary modules
module purge
module load ANSYS/17.1

## Launch the solver with proper parameters
runwb2 -R fileName.wbjn -B

To submit the batch job, run: (where jobscript is a file that looks like one of the above examples)

[ NetID@ada1 ~]$ bsub < jobscript

Terra Example

Example 1: A serial (single core) Workbench Job example: (Last updated March 24, 2017)

#SBATCH --export=NONE
#SBATCH --get-user-env=L

#SBATCH --job-name=WorkbenchJob # Sets the job name to WorkbenchJob
#SBATCH --time=5:00:00          # Sets the runtime limit to 5 hr
#SBATCH --ntasks=1              # Requests 1 core
#SBATCH --ntasks-per-node=1     # Requests 1 core per node (1 node)
#SBATCH --mem=5G                # Requests 5GB of memory per node
#SBATCH --output=stdout1.o%J    # Sends stdout and stderr to stdout1.o[jobID]

## Load the necessary modules
module purge
module load ANSYS/18.0

## Known error fix

## Launch the solver with proper parameters
runwb2 -R fileName.wbjn -B

To submit the batch job, run: (where jobscript is a file that looks like one of the above examples)

[ NetID@terra ~]$ sbatch jobscript