LS-DYNA Download Page

System Requirements

Basic Considerations

Generally your executable will work if:

1. your CPU supports the targeted instruction set,
2. you have a compatible OpenMPI runtime,
3. and your operating system is newer than what it was built with.

The filename of the package encodes all three items. For example, the filename below indicates an OpenMPI version built on CentOS 7.8 targeting the AVX2 instruction set.

ls-dyna_mpp_s_R14_0_0_x64_centos78_ifort190_avx2_openmpi405.tgz_extractor.sh

1. Intel packages that have no CPU instruction in the name (usually happens with SMP) are always SSE2.
2. LS-DYNA is tolerant of differences between the runtime and build-time environments.
3. We run quality assurance checks on all of the platforms Ansys officially supports at the time of release.

Additional Details

1. Your system MUST support the CPU instruction set indicated on the package.
   • For example, an AVX512 executable will crash with an illegal instruction error unless the runtime environment supports that instruction.
2. Your interconnect driver must be compatible with your MPI runtime environment.
   • This is, by far, the most important consideration when running MPP or hybrid LS-DYNA.
   • Driver issues are responsible for a sizable fraction of all reported MPP LS-DYNA installation problems.
   • Getting a functional driver combined with an MPI runtime that is compatible with both (1) your LS-DYNA executable and (2) with the driver is more important than having the MPI runtime version match the build environment's.
3. The version of your local MPI runtime tools must be the same as or newer than the version of MPI used to build the LS-DYNA package.
4. The operating system used to run LS-DYNA must be newer than or equal to the build environment's.
   • All other things equal, it is better to match the run time and build time environments as closely as possible. Still, experience shows other considerations are more important.
   • Usually, it is only the operating system's major version number that matters. For example a CentOS 6.5 executable will run on all versions of CentOS 6.
   • The C library version of your operating system is what truly determines whether or not an executable is compatible with your system.
   • Almost always, a package built for one distribution (for example, CentOS) will run on another (for example, Ubuntu) provided the distribution's libc runtime is newer than the build environment's.