SW:LSDYNA

LS-DYNA

LS-DYNA is a general-purpose finite element program capable of simulating complex real world problems. - Homepage: http://www.lstc.com/products/ls-dyna

Access

LS-DYNA is available to any users within an academic department which has purchased their own license. We host the license on behalf of the licensed department(s).

Loading the Module

To see all versions of LS-DYNA available on Ada:

 module spider LS-DYNA

To load the default LS-DYNA module on Ada:

 module load LS-DYNA

To load a particular version of LS-DYNA on Ada (Example: R8.1.0):

 module load LS-DYNA/R8.1.0

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 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:

• Terra: About Terra Batch Processing
• Grace: About Grace Batch Processing

Ada Example

A single precision example:

#BSUB -J LSDYNAJob1        # sets the job name to LSDYNAJob1
#BSUB -L /bin/bash         # uses the bash login shell to initialize the job's execution environment
#BSUB -W 48:00             # sets to 48 hours the job's runtime wall-clock limit
#BSUB -n 40                # assigns 40 cores for execution.
#BSUB -R "span[ptile=20]"  # assigns 20 cores per node.
#BSUB -R "rusage[mem=1500]"  # reserves 1500MB per process/CPU for the job
#BSUB -M 1500              # sets to 1500MB (~1.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 LS-DYNA/R7.1.2

## Run LS-DYNA with the proper parameters
mpirun ls-dyna_mpp I=InputFile O=OutputFile MEMORY=300m D=d3dump

A double precision example:

#BSUB -J LSDYNAJob1        # sets the job name to LSDYNAJob1
#BSUB -L /bin/bash         # uses the bash login shell to initialize the job's execution environment
#BSUB -W 48:00             # sets to 48 hours the job's runtime wall-clock limit
#BSUB -n 40                # assigns 40 cores for execution.
#BSUB -R "span[ptile=20]"  # assigns 20 cores per node.
#BSUB -R "rusage[mem=2500]"  # reserves 2500MB per process/CPU for the job
#BSUB -M 2500              # sets to 2500MB (~2.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 LS-DYNA/R7.1.2

## Run LS-DYNA with the proper parameters
mpirun ls-dyna_mpp_d I=InputFile O=OutputFile MEMORY=300m D=d3dump

To submit the batch job, run:

bsub < jobscript

where jobscript would look like the example above.

Terra Example

TO BE ADDED LATER

Memory Specification

The LS-DYNA command line option MEMORY specifies memory per node with a base unit words. The argument can be specified in words or megawords (denoted by m). For single precision LS-DYNA, a word is 4 bytes and a megaword is 4 MB. For double precision, a word is 8 bytes and a megaword is 8MB.

Example: (Single Precision)

MEMORY=300m     #300 megawords = 300 megawords * 4 MB = 1200 MB (~1.2GB)
MEMORY=600      #600 words = 600 words * 4 B = 2400 KB

Example: (Double Precision)

MEMORY=300m     #300 megawords = 300 megawords * 8 MB = 2400 MB (~2.4GB)
MEMORY=600      #600 words = 600 words * 8 B = 4800 KB

Checking Input Before Running

If there are no licenses currently available, or if you would not like to check out licenses. There is a way to initialize your model and check for errors without using any licenses. This can be done with the mcheck command option.

Example:

#BSUB -J LSDYNAJob1        # sets the job name to LSDYNAJob1
#BSUB -L /bin/bash         # uses the bash login shell to initialize the job's execution environment
#BSUB -W 48:00             # sets to 48 hours the job's runtime wall-clock limit
#BSUB -n 40                # assigns 40 cores for execution.
#BSUB -R "span[ptile=20]"  # assigns 20 cores per node.
#BSUB -R "rusage[mem=2500]"  # reserves 2500MB per process/CPU for the job
#BSUB -M 2500              # sets to 2500MB (~2.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 LS-DYNA/R7.1.2

## Run LS-DYNA with the proper parameters
mpirun ls-dyna_mpp_d I=InputFile O=OutputFile MEMORY=300m mcheck=1

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.

More Information

To find more information on LS-DYNA, please consult the LS-DYNA manuals located at http://www.dynasupport.com/manuals.