Hprc banner tamu.png

Difference between revisions of "SW:ANSYS:Workbench"

From TAMU HPRC
Jump to: navigation, search
Line 20: Line 20:
 
To load a particular version of ANSYS on Ada (Example: 17.1):
 
To load a particular version of ANSYS on Ada (Example: 17.1):
 
   [netID@cluser ~]$ '''module load ANSYS/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.<br>
 +
To bypass this bug, load the '''OpenGL/NVIDIA''' module before running the Ansys Workbench:
 +
[ netID@cluster ~]$ '''module load OpenGL/NVIDIA'''
  
 
{{:SW:Login_Node_Warning}}
 
{{:SW:Login_Node_Warning}}

Revision as of 15:03, 2 March 2017

Workbench

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

Access

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

IMPORTANT NOTE REGARDING THE ANSYS LICENSE:

   Terms of the ANSYS Academic license require that all users be within 50 miles 
       of the TAMU main campus in College Station, TX. 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

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 (20 cores, 64GB or 256GB). There are fewer VNC nodes than comparable compute nodes.

For more information, including instructions, on using software on the VNC nodes, please visit our Ada 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

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

#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 5000MB per process/CPU for the job (5GB * 2 Cores = 10GB per node) 
#BSUB -M 5000		  # sets to 5,000MB (~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 load ANSYS/17.1

## Launch Workbench with proper parameters
runwb2 -R FileName.wbjn -B

Where FileName is a Workbench Journal file.

To submit the batch job, run:

 [netID@cluser ~]$ bsub < jobscript

where jobscript would look like the example above.

Terra Example

TO BE ADDED LATER.