Beruflich Dokumente
Kultur Dokumente
0
Application Installation Guide
Revision 2
www.altair.com
FTP site
Location
Telephone
North America
248.614.2425
hwsupport@altair.com
China
86.400..619.6186
support@altair.com.cn
France
33.1.4133.0992
francesupport@altair.com
Germany
49.7031.6208.22
hwsupport@altair.de
India
91.80.6629.4500
1800.425.0234 (toll free)
support@india.altair.com
Italy
39.800.905.595
support@altairengineering.it
Japan
81.3.5396.2881
support@altairjp.co.jp
Korea
82.70.4050.9200
help@altair.co.kr
Scandinavia
46.46.286.2052
support@altair.se
United Kingdom
01926.468.600
support@uk.altair.com
Brazil
55.11.3884.0414
br_support@altair.com
Australia
61.3.9016.9042
anzsupport@altair.com
New Zealand
64.9.413.7981
anzsupport@altair.com
Altair HyperWorks 11.0 Installation Guide for Window, Unix and Linux
Listed below are Altair HyperWorks applications. Copyright Altair Engineering Inc., All Rights Reserved for:
HyperMesh 1990-2011; HyperCrash 2001-2011; OptiStruct 1996-2011; RADIOSS1986-2011;
HyperView1999-2011; HyperView Player 2001-2011; HyperStudy 1999-2011; HyperGraph1995-2011;
MotionView 1993-2011; MotionSolve 2002-2011; HyperForm 1998-2011; HyperXtrude 1999-2011;
Process Manager 2003-2011; Templex 1990-2011; Data Manager 2005-2011; MediaView 1999-2011;
BatchMesher 2003-2011; TextView 1996-2011; HyperMath 2007-2011; ScriptView 2007-2011;
Manufacturing Solutions 2005-2011; HyperWeld 2009-2011; HyperMold 2009-2011; solidThinking 19932011; solidThinking Inspired 2009-2011; Durability Director 2009-2011; Suspension Director 2009-2011;
AcuSolve 1997-2011; and AcuConsole 2006-2011.
In addition to HyperWorks trademarks noted above, GridWorks.
In addition to HyperWorks trademarks noted above, GridWorks, PBS Gridworks, PBS Professional, PBS
and Portable Batch System are trademarks of ALTAIR ENGINEERING INC., as is patent # 6,859,792. All are protected
under U.S. and international laws and treaties. All other marks are the property of their respective owners.
Overview ................................................................................................................................................ 5
HyperWorks 11.0 Software and Hardware Release Notes ................................................................ 8
Chapter 1: Preparing to Install HyperWorks .................................................................................... 13
1.1 Installation Media ...................................................................................................................... 13
1.2 Hardware and Operating System ............................................................................................. 14
1.3 System Requirements .............................................................................................................. 16
Chapter 2: Installing HyperWorks ..................................................................................................... 20
2.1 Installing HyperWorks: Local Install.......................................................................................... 20
2.2 Installing HyperWorks: Server/Client Installation ..................................................................... 26
2.3 Connecting to the Altair License Management System............................................................ 28
2.4 Starting HyperWorks Applications ............................................................................................ 29
2.5 Setting Up HyperWorks Help.................................................................................................... 32
Chapter 3: Installing AcuSolve .......................................................................................................... 35
3.1 Install AcuSolve/AcuConsole .................................................................................................... 36
3.2 Connecting to Altair Licensing Server ...................................................................................... 37
3.3 Integration of AcuSolve CFD Solutions into the HyperWorks Environment ............................. 38
Chapter 4: Installing RADIOSS HMPP............................................................................................... 41
4.1 Installing RADIOSS HMPP on IBM AIX Cluster ....................................................................... 46
4.2 Installing RADIOSS HMPP on SGI ALTIX Itanium2................................................................. 48
4. 3 Installing RADIOSS HMPP on Intel Itanium2 Linux Cluster using Platform MPI (formerly HP
MPI) .................................................................................................................................................. 49
4.4 Installing RADIOSS HMPP on x86-64 Linux Cluster using Platform MPI (formerly HP MPI) .. 52
4. 5 Installing RADIOSS HMPP on x86-64 Linux Cluster using Intel MPI...................................... 55
4. 6 Installing RADIOSS HMPP on AMD Operton or Intel EM64T Solaris 10 Cluster ................... 62
4. 7 Installing RADIOSS HMPP on Windows Server 2003 Computer Cluster using MS MPI ....... 65
3
4. 8 Install RADIOSS HMPP on Windows 64 Cluster using Platform MPI (formerly HP MPI) ....... 73
Chapter 5: Installing OptiStruct SPMD ............................................................................................. 77
5.1 Hardware and Operating Systems ........................................................................................... 78
5.2 Installing OptiStruct SPMD on Linux Cluster ............................................................................ 79
5.3 Launching OptiStruct SPMD on Linux Cluster ......................................................................... 81
5.4 Installing OptiStruct SPMD on AIX Cluster ............................................................................... 82
5.5 Launching OptiStruct SPMD on AIX Cluster ............................................................................ 83
5.6 Installing OptiStruct SPMD on Windows Machines .................................................................. 84
5.7 Launching OptiStruct SPMD on Windows Machines ............................................................... 84
5.8 Frequently Asked Questions .................................................................................................... 86
Appendix A: HyperWorks Directory Structure ................................................................................. 88
Appendix B: Recommended Graphic Boards .................................................................................. 91
Appendix C: Setting Up the CAD Translators .................................................................................. 93
C.1 UG Environment Variable Settings .......................................................................................... 93
C.2 Set up Catia V5 License .......................................................................................................... 94
Appendix D: Local Installation on Windows (64-bit) - GUI Mode ................................................... 95
Appendix E: Server Installation on Windows (64-bit) - GUI Mode ............................................... 100
Appendix F: Local Installation on Linux (64-bit) - GUI Mode........................................................ 106
Appendix G: Local Installation on Linux (64-bit) - Console Mode ............................................... 110
Appendix H: Uninstall HyperWorks ................................................................................................ 113
Appendix I: RADIOSS HMPP to MADYMO 7.1 MPP Coupling .................................................... 114
I.1 Supported Platforms ................................................................................................................ 114
I.2 Install and Run RADIOSS HMPP to MADYMO 7.1 MPP Coupling ........................................ 114
Appendix J: HyperWorks Installation Known Limitiations ........................................................... 118
4
Overview
Introduction
This guide provides instructions for the installation and operation of HyperWorks software on
supported platforms. The procedures for connecting to an Altair HyperWorks Units licensing system,
execution of the applications and connecting the application clients to existing HyperWorks help,
including local, networked and web help, are explained.
The contents of this guide include:
Appendices
Chapter 1 provides general installation procedures for required items, hardware and operating
system considerations and suggestions for installation configuration on various platforms.
Chapter 2 provides detailed installation instructions, connecting to license server, and invoking
HyperWorks application on Windows, Linux and Unix supported platforms.
Chapter 3 provides detailed instructions of installing AcuSolve and integration of AcuSolve and
HyperWorks.
Chapter 4 contains an introduction to RADIOSS HMPP and procedures for installing and executing
RADIOSS HMPP on various supported platforms.
Chapter 5 contains an introduction to OptiStruct SMPD and procedures for installing and executing
OptiStruct SMPD on various supported platforms.
Appendices provide additional information about HyperWorks applications, including examples of
installation HyperWorks.
HyperWorks 11.0 uses InstallAnywhere 2010 as its installation tool. The HyperWorks 11.0 installers
are InstallAnywhere web installers. InstallAnywhere provides a consistent look and feel of the
HyperWorks installation wizard across all platforms supported by Altair HyperWorks products.
HyperWorks 11.0 adopts a new licensing technology and is no longer based on FlexLM. This new
technology further improves the HyperWorks licensing model and allows Altair to integrate the
business model and promptly respond to issues. In order to run HyperWorks 11.0 applications, you
need to connect the applications to the Altair License Management System 11.0. Details of the
installation and how to start the Altair License Manager can be found in the Altair License
Management System 11.0.1 Installation Guide. The license packages are available on the Altair web
site.
Overview
About HyperWorks
HyperWorks, The Platform for Innovation, is built on a foundation of design optimization,
performance data management, and process automation. HyperWorks is an enterprise simulation
solution for rapid design exploration and decision-making. As one of the most comprehensive CAE
solutions in the industry, HyperWorks provides a tightly integrated suite of best-in-class tools for
modeling, analysis, optimization, visualization, reporting, and performance data management.
Leveraging a revolutionary pay-for-use token-based business model, HyperWorks delivers
increased value and flexibility over other software licensing models. Firmly committed to an opensystems philosophy, HyperWorks continues to lead the industry with the broadest interoperability to
commercial CAD and CAE solutions.
HyperWorks comprises a suite of applications that includes HyperMesh, HyperCrash, OptiStruct,
RADIOSS, HyperView, HyperView Player, HyperStudy, HyperGraph, MotionView,
MotionSolve, HyperForm, HyperXtrude, Process Manager, Templex, Data Manager,
MediaView, BatchMesher, TextView, HyperMath, ScriptView, Manufacturing Solutions,
HyperWeld, HyperMold, solidThinking, solidThinking Inspired, Durability Director,
Suspension Director, AcuSolve, and AcuConsole, providing modeling and assembly, robust
design and optimization, design analysis, visualization and reporting, virtual manufacturing, and
automation and data management.
Altair HyperWorks license management is no longer based on Flexera Softwares FlexNet Publisher
(formerly known as FLEXlm). It is replaced by the new Altair Licensing System. This allows for more
flexibility to address customers licensing needs and for further innovations to the HyperWorks
business model.
HyperWorks 11.0 licensing is based on HyperWorks Units (HWUs). HyperWorks unit licenses are
server licenses. Customers can launch any application within the HyperWorks suite as long as there
are sufficient HyperWorks units to grant the license check out.
To invoke HyperWorks 11.0 applications, after completing the HyperWorks 11.0 installation, you need
to point the applications to an activated Altair License Manager or a valid node stand-alone license by
setting the proper environment variable.
The HyperWorks 11.0 package does not include the license package that sets up the Altair License
Manager. Download the Altair license package from Altair web site and follow the Altair License
Management System 11.0.1 Installation and Operation Guide to install and activate the Altair License
Manager properly.
In some cases, Altair provides feature based licenses, which allow a particular application to run as
long as the feature exists in the license file. A feature license is a standalone license that does not
consume HyperWorks units.
All words from the user interface, including options, menus, buttons, and dialog box
names.
Example: On the Welcome screen, click Next.
Courier The path of a program or folder; a web address; a file name or component; text that the
user is expected to enter.
Example: The default path is C:\Altair\hw11.0.
Italic
For emphasis or for introducing a new term; for names of topics (headings) within this
guide.
Overview
Warnings appear in these boxes. Their content is designed to prevent serious installation
problems.
Questions regarding the software and license installation may be directed to Altair Support. See the
Contact page for further contact information.
Altair iExchange
In addition to many other useful features, the Altair Client Center now offers an exciting new online
message board system called iExchange. This message board is open to all HyperWorks users,
allowing you to share information with, and gain insight from engineering professionals around the
world as well as Altair staff.
Access iExchange now by registering and logging in to the Altair Client Center
(http://www.altairhyperworks.com/clientcenter); and then complete the iExchange profile.
solidThinking
Inspired
AcuSolve
Hardware Platforms
Supported Hardware Platform Additions
Operating system
Windows 7
RHEL 5.4
AcuSolve/AcuConsole
Integration into
HyperWorks
RHEL4.x/5.2
SLED 10 SP1
HPUX 11.11
Installation
New Features
New Installation Third
Party Software
Installation
/Uninstallation
Installation Information
Invoking
Installation
Packaging
Enhancements
Server/Client
installation
Known Limitations
Un-installation
10
Installation
Server/Client
Installation
Help Search
AcuSolve/AcuConsole
Separate Installation
Online Help
Help
New Features
11
applications, users can invoke the online help via Altair Web
site from within the application.
Title Bar
Version
Replaced licensing utility tool lmutil with the almutil and lmxconfig.
Enhancements
Search Capability
Known Limitation
Search
Utilities/Tools
New Features
Lmxutil
Enhancements
Help Menu
Resolved Issues
HW Inventory
12
Install and activate an Altair 11.0 License Manager if one does not already exist.
Set up an environment variable that points the HyperWorks application to an activated and
running Altair license server.
The software to install Altair License Manager is a separate package from the HyperWorks
11.0 application packages. Download the Altair license package from the Altair web site and
follow the Altair License Management System version 11.0.1 Installation and Operation
Guide to install and start the Altair License Manager properly.
HyperWorks software DVDs media, Altair License Manager DVD, delivered from Altair, or
HyperWorks image packages downloaded from the Altair web site
Sufficient disk space: up to 6 GB per platform and 6 GB of temp space are required to install
the full suite of HyperWorks 11.0 applications)
The information in this chapter regarding proper media and hardware requirements will help prepare
users for a successful HyperWorks installation. Go to Chapters 2, 3 or 4 for information on installing
HyperWorks 11.0 on various platforms.
_______________________________________________________________________________
HyperWorks 11.0 Quick Installation Guide, HyperWorks 11.0 Release Notes, and the HyperWorks
11.0 supported hardware and operating system list.
The software is also available for registered customers to download from the Altair web site through
the Altair Client Center (http://www.altairhyperworks.com/clientcenter).
Download the images for the platforms on which you expect to launch HyperWorks. There are three
packages required for a complete HyperWorks installation on each platform: standard HyperWorks
applications, Help file, and Altair AcuSolve CFD Solutions.
Altair License Manager is not packaged in the HyperWorks product images. You need to download
and install it separately before installing the HyperWorks suite.
________________________________________________________________________________
Platforms
OS
Version
GUI Products
Solvers
x86
YES
YES
x86_64
YES
YES
x86
NO
YES
x86_64
NO
YES
x86
YES
YES
x86_64
YES
YES
IA-64
NO
YES
IA-64
NO
YES
Power 4/5
NO
Solaris 10
x86_64
NO
YES
10.6
x86_64
YES
YES
XP/Vista/7
Windows2
3
Server 2003/2008
RHEL 5.4
SLED 11
Linux4
SGI ProPack 4
(SLES 9)
YES
Unix
**Mac OSX
**The Mac OS X package will not ship on the release DVD media of HyperWorks 11.0. It will only be available via
the Altair website as a separate downloadable installer package.
14
HyperWorks solver products include RADIOSS, OptiStruct, MotionSolve, and HyperXtrude solver. The HyperWorks
solvers support AMD Opteron/Athlon64, Intel EM64T, Itanium2 (non-Windows based) and IBM AIX Power 4/5
processors and system architectures.
RADIOSS and OptiStruct provide H-MPP and SPMD parallelization using 3
compatible and certified.
NOTE:
rd
HTire, FTire and running MotionSolve for the MDL Wizard Library models is only supported on Windows
and Linux 32-bit (x86) and 64-bit (x86_64) platforms.
HyperWorks Solvers may be available or made available on platforms other than those listed as officially
supported. Please contact an Altair regional support office or go to the Altair web site under Contact Us
and submit a query for more details.
HyperWorks 11.0 products have a minimum requirement of the Microsoft Visual C++ 2005 SP1 (version
8.0.50727.4053) and solidThinking/Inspired requires 2008 SP1 (version 9.0.21022.8) redistributable package and
these runtimes are distributed within the HyperWorks package. Process Manager, HyperMath and ScriptView are
native 32-bit applications that are supported on both 32-bit and 64-bit Windows platforms.
Only SMP parallelization is supported for HyperWorks 11.0 solvers on Windows (x86), Linux (x86) and Mac OS X
(x86_64) architectures.
GLIBC version 2.3.4 (glibc-2.3.4-2.25) includes native and compatible 32-bit packages
GCC 3.4.3 (gcc 3.4.3 20050227) includes native and compatible 32-bit packages
LIBSTDC++ packages:
a) libstdc++-3.4.3-22.1 (libstdc++.so.6) 64-bit/32-bit
b) compat-libstdc++-33-3.2.3 (libstdc++.so.5)- 64-bit/32-bit
NOTE: Altair bundles custom Tcl/Tk 8.5.6 packages with HyperWorks 11.0 and sets the environment variable
XLIB_SKIP_ARGB_VISUALS=1 in the startup scripts, which may degrade GUI menu performance. To override this
option set the variable XLIB_SKIP_ARGB_VISUALS=0 within the systems or users environment.
Additional Linux library packages (minimum versions):
POSIX shared memory (for 3D applications)/ELF TLS (thread local storage) libraries
X-org 6.8.2 packages (or XFree86 equivalent)and OpenMotif libX11, libXm.so.3, libXp.so.6, etc
Kernel source/header files (used to compile 3D NVIDIA/AMD ATI OpenGL vendor driver modules)
Tools: rpm/fontconfig/freetype/zlib/gzip/tar/gtar
Fonts (scalable): Helvetica, Times, New Century schoolbook, b&h luxi sans/serif, typeface, bitstream vera
sans/serif, iso8859-1 (75dpi/100dpi) and Utopia
HyperMesh Batch, BatchMesher, temple and the HyperGraph translator tools will be available in command line
execution mode under the IBM AIX5.3 platforms. HyperView translator tool will also be available on Linux Itanium
platforms. CAD formats for UG and CATIA v4/v5 data types are not supported under IBM AIX 5.3 for HyperMesh
batch programs. HyperXtrude GUI component is included under the HyperWorks GUI supported platforms only.
15
OS X v.10.6 Snow Leopard (Darwin 10.6.0) and X11 2.3.5 (No Mac OS X PowerPC support)
Unsupported HyperWorks products under the Mac OS X:
UG, JT, ACIS, Parasolid, ProE, SolidWorks, STEP, CATIA v4/v5 are not available data types under the
Mac OS X platform.
HyperWorks Solvers: will only support SMP computations on the Mac OS X 10.6 Intel (x86_64) architecture for
HyperWorks 11.0.
Acronym
Description
RHEL
SLED
SLES
MPI
SMP
SPMD
HMPP
_____________________________________________________________________________________________________
HyperWorks Solvers
Linux RHEL 5.2/SLED 11
Sun Solaris 10 (x86_64)
Memory
16
XP/Vista/7
Solvers only
Windows
~ 4.2 GB
~ 5.5 GB
**Approximately 6 GB of free
disk space is required for
temporary install files (TMP)
for a complete HyperWorks
11.0 installation in addition to
the installed files space
needed. The temporary files
are removed upon the
completion of the installer.**
Graphics Hardware
Linux 32-bit
Linux 64-bit
Solaris 10 (solvers)
~ 5.8 GB
~ 6.4 GB
~ 621 MB
Windows 64-bit
patches/drivers
1280x1024 screen resolution
*Browsers/Online help
(plug-in)
~ 6.2 GB
Local Help installs may require modifying the browser to allow running active content from the hard disk. For
search capability, the end-user needs a browser supporting either ActiveX (IE on Windows) or Java plug-in
installed on their machine. For details on setting the Java plug-in for Linux, reference the information in the
following link: http://www.java.com/en/download/help/linux_install.xml
17
If you have purchased a hardware dongle to use for licensing, you must obtain the dongle ID via the
software before requesting your license file. Hardware dongles are supported on the following
platforms:
Windows
OS X
In order for the dongle to function properly, you must first install the correct drives for your platform.
These drives are available from Aladdin, the manufacturer of the key. Download and install the driver
according the directions available at the following URL:
http://www.aladdin.com/support/hasp/enduser.aspx
Once the driver is installed and the dongle is in place, use the almutil hostid command to query
for all the hostids on the machine and report the dongle Hostid.
Non-US Keyboards
HyperWorks ships with the keyboard configuration set for a US keyboard. Some countries use
extended keyboards to generate native characters not present in the US ASCII character set. Use
the following instructions for your operating system to install a local keyboard configuration.
Windows VISTA
Follow these instructions to configure your non-US keyboard on Windows:
1. From the Start menu, select Control Panel.
2. Select Clock, Language and Regional Options.
3. Select Change keyboard or other input methods tab.
4. Click Change keyboards and select the proper one from the drop-down list.
5. Click OK.
6. Click OK to close the dialog.
Windows 7
Follow these instructions to configure your non-US keyboard on Windows:
18
19
Platform
Size (GB)
hw11.0_win32.exe
Windows (32-bit)
1.7
hw11.0_win64.exe
Windows (64-bit)
1.9
hw11.0_linux32.bin
Linux (32-bit)
1.3
hw11.0_linux64.bin
Linux (64-bit)
1.4
hw11.0_batch_aix64.bin
0.9
Platform
Size (GB)
help11.0_win32.exe
Windows (32-bit)
1.6
help11.0_win64.exe
Windows (64-bit)
1.5
help11.0_linux32.bin
Linux (32-bit)
1.6
help11.0_linux64.bin
Linux (64-bit)
1.6
help11.0_aix64.bin
1.6
AcuSolve Filename
Platform
Size (GB)
AcuSolve-V1.8a-WIN32.msi
Windows (32-bit)
0.6
AcuSolve-V1.8a-WIN64.msi
Windows (64-bit)
0.6
AcuSolve-V1.8a-LINUX.gz
Linux (32-bit)
0.5
AcuSolve-V1.8a-LINUX64.gz
Linux (64-bit)
0.7
Containing AcuSolve and AcuConsole applications (only available from Altair web site)
The images downloaded from the Altair web site can be in two different package types: one file per
platform or split to multiple files that are easy to download. The split images are 250 MB per file.
Run the unsplit script (available with each split image folder) to cat these files together before the
installation.
To install Help along with the application, download and place the Help Files executable file in the
same residing directory as the main HyperWorks installer. Help Files contain the Help, tutorial model
files, and the demo/ files. The user has the option to select and install complete Help, tutorials and
demo files or a combination of the three options. Reference step 9 below.
2. Insert the DVD, or place the downloaded files in a temporary directory. The Help Files executable
file should reside in the same directory as the main HyperWorks installer.
3.
a. On Windows, double click the installer executable file to start the installation wizard.
Note: If UAC (User Account Control) is enabled then a prompt will be displayed for elevated
permissions. Click Yes to continue with installation
b. On Linux/Unix, run the sh command on the installer binary. For example: sh
hw11_linux64.bin
4. The HyperWorks installer will now extract the JVM (Java Virtual Machine) and the install modules
to the TMP location of the machine.
5. The multi-language selector prompt will be displayed. Select the proper locale and click OK to
continue. The default locale setting is specific to the install machine regional settings.
The language selection only corresponds to the installer settings, not to the HyperWorks
product language settings. Altair HyperWorks products are in English.
6. The Introduction and Copyright panels are displayed for viewing. Click Next to continue.
7. (Windows only) The Choose Installation Type panel is displayed. Choose install type, either
Local or Server type installs and click Next.
9. (Windows only) The Choose Shortcut Folder panel is displayed. This allows for users to
customize:
a. Start Menu Folder name. The default is Altair HyperWorks 11.0 (64-bit), where the bit type
is dependent on the version of the installer.
b. The installation of Desktop shortcuts. The default option is set to not install desktop shortcuts.
Choose the preferred options and click Next to continue.
For Windows Server type installs the Choose Shortcut Folder (Server) panel also allows
for more customization options for users to choose the shortcut folder install location, which
defaults to the All Users shortcut folder location. For Server and Client installs the word
Server and Client will be prefixed to the bit type, example Altair HyperWorks 11.0 (Server 64bit).
22
10. The Choose Install Set panel is displayed. Select Complete or Custom installer types and click
Next to continue.
a. Selecting Custom will allow for choosing select products and help files install combinations.
b. If Help Files is selected, then the corresponding help installer executable must reside in the
same directory as the installer. (See Section 2.1a for filenames and platform types.)
11. If Help is selected to be installed then continue to next step. If Help is not selected, the Help
Configuration panel is displayed. The three alternate Help configurations are:
a. Connect to a network installed Help location.
This will prompt for the pre-installed Help location. The variable used is HW_MSG_HELP in the
hwhelp.cfg in the install directory.
b. Connect to Altair web site Help (Default)
Requires internet web access.
c.
Set Up Later
Requires manipulation of the hwhelp.cfg file located in the installation folder for manual
setup.
12. (Windows Server Install Types Only) The UNC (Uniform Naming Convention) mount point
panel is displayed if:
a. Server install type was selected.
b. The install path used contained a Windows drive letter, example C:\pathname\folder
13. Input the UNC path and click Next to continue.
NOTE: The user input needs to be in the form of the UNC standard
\\MachineName\SharedFolder\InstallFolder to be accepted.
See Section 2.2 for how to set up the client machine.
14. The HyperWorks AcuSolve Notice prompt message is displayed. Review the message and click
OK to continue.
15. The Pre-Installation Summary panel is displayed. Review the selections and click Install to
continue.
Install times are machine hardware dependant. Anti-virus software may lengthen the install
times.
16. Once the installation completes, click Done to exit the install wizard.
1. Download the AcuSolve CFD solutions installer separately from the above Altair HyperWorks
installer.
2. To start the AcuSolve CFD solutions installer:
a. On Windows, double click the executable to start the installer.
b. On Linux:
i.
ii.
Change directory (cd) into the newly uncompressed folder from the step above
iii. Type ./INSTALL in the terminal and follow the on-screen prompts and questions
iv. Set the environment by sourcing the .acusim file
NOTE: Reference the README.txt file for additional information.
3. After the AcuSolve CFD solutions installation completes, the acuSetHW utility will be executed
automatically to establish the connection between the Altair HyperWorks and the AcuSolve tools
suite.
To run AcuSolve, Perl 5.0 or higher must be installed on the system. If not installed, it can be
downloaded from http://www.activestate.com/activeperl/downloads
See Appendix D, E, and F for detailed instructions on installing HyperWorks via GUI mode.
See Appendix G for details of installing HyperWorks via console mode on Linux/Unix.
DONOT_INSTALL_DESKTOP_SHORTCUTS=0
The installer will use double backslashes \\ on Windows platforms for the directory names
and forward slash / on Linux/Unix platforms.
1. Go to the HyperWorks network server install NETSETUP directory location and run the
NETSETUP.bat file.
a. Go to Networks
b. Click on the machine and install location of the HyperWorks server install
c.
d. Go to the win64 folder (on a 32-bit Windows install the folder is win32)
e. Click on the NETSETUP.bat file
2. A command prompt terminal window will be displayed showing that the installer is unpacking on
the client machines. The locale language selection prompt will then be displayed. Select the
locale language and click OK to continue.
3. The HyperWorks NETSETUP client Start Menu and Desktop Shortcuts options panel is
displayed. Make changes if needed and select Next to continue.
4. The HyperWorks NETSETUP Pre-Installation Summary panel is displayed. Review summary
and click Install to complete the HyperWorks NETSETUP client install.
5. This will create the appropriate Start Menu and Desktop Shortcuts to the client machine. Once it
completes, click Done to exit the install wizard.
d. Go to the win64 folder (on a 32-bit Windows install the folder is win32)
e. Click on the NETSETUPproperties.bat file
2. A command prompt will be displayed to make sure the end user has write permissions to the
NETSETUP network location, where the properties response file gets created. Type y and press
Enter to continue.
27
3. A command prompt terminal window will be displayed showing that the installer is unpacking on
the client machines. The locale language selection prompt will then be displayed. Select the
locale language and click OK to continue.
4. The HyperWorks NETSETUP client Start Menu and Desktop Shortcuts options panel is
displayed. Make changes if needed and select Next to continue.
5. The HyperWorks NETSETUP Pre-Installation Summary panel is displayed. Review summary
and click Install to complete the HyperWorks NETSETUP client install.
6. This will create the appropriate Start Menu and Desktop Shortcuts to the client machine. Once it
completes, click Done to exit installer. The installer will now create a file under the NETSETUP
platform folder called NETSETUP_installer.properties. This will be used for future client
NETSETUP installs.
7. All future silent client NETSETUP installs only require the user to click on the
NETSETUPsilentinstall.bat file, if the defaults associated to the
NETSETUP_installer.properties file will suffice.
ALTAIR_LICENSE_PATH=6200@server.foo.bar.com
ALTAIR_LICENSE_PATH=6200@srv1:6200@srv2:6200@srv3
ALTAIR_LICENSE_PATH=/usr/local/altair/licensing11.0/altair_lic.dat
For High Availability License (HAL) System and/or Multiple Servers setups, list the three servers in the
order: primary; secondary; tertiary.
Node-Locked License
For node-locked license (a license that is locked to a local machine), you can either place the license
file in the <install_dir>/altair/security/ directory, or set the environment variable,
ALTAIR_LICENSE_PATH, to point to the appropriate location where the license file resides. The
default name that Altair products use for this license file is altair_lic.dat.
Options
Descriptions
datamanager
es_cfd
29
es_crash
es_droptest
es_nvh
hc
Launch HyperCrash
hfsolver
hg
Launch HyperGraph
hm
Launch HyperMesh
hmbatch
-c<command filename>
Launch HyperMesh using batch mode
-tcl <file>
hmdesktop
hst
Launch HyperStudy
hst
-studyfile=<filename>
hstbatch
hv
Launch HyperView
hvp
hx
Launch HyperXtrude
hw_batchmesh
blanknest
Launch BlankNesting
hmath
Launch HyperMath
hmathbatch
mdl_batch
-c<session filename>
motionsolve
Launch MotionSolve
mview
Launch MotionView
mfs_forging
mfs_hyperweld
mfs_hf
mfs_hx
30
mfs_hypermold
optistruct
Launch OptiStruct
ossmooth
Launch OSSmooth
pmstudio
radioss
Launch RADIOSS.
resmap
sview
Launch ScriptView
templex
Template.tpl <output>
Launch Templex
Perform the following steps if you would like to change the default working directory.
1. Click Start and select Programs.
2. From the Programs menu click Altair HyperWorks 11.0.
3. Open the current version of HyperWorks to see the available applications.
31
4. Right-click on the HyperWorks application for which you want to set the working directory.
5. From the menu, select Properties.
6. Select the Shortcut tab.
7. In the Start in text box, enter the explicit path name of the folder from which you want to run the
HyperWorks application.
8. Click OK.
Your user files are created in the directory specified in Step 7.
For example, if you had selected HyperMesh, the command.cmf, and hmmenu.set would go to this
directory.
If you create a shortcut directly from the <install_location>\application\bin directory, the
start in directory of the shortcut will be from that directory. We recommend that you change the start
in path to: "%userprofile%\my documents[%userprofile%\documents]" or any directory you
prefer.
In order for HyperWorks help to work properly, you must set up a valid browser on the machine from
where the application is launched. For Windows, HyperWorks uses the default Windows browser. For
Unix and Linux, the valid browser is set during the installation time. You can verify the browser
setting stored in the hwhelp.cfg file. The hwhelp.cfg file is located in the <installation
directory>/altair/ directory.
If Help is pre-installed on a shared network location, the information will be stored in the hwhelp.cfg
file as well. A typical hwhelp.cfg file should contain the following information:
HW_MSG_BROWSER /usr/bin/firefox
HW_MSG_HELP <install_Dir>/altair/help
If HW_MSG_HELP is not set in the hwhelp.cfg file, HyperWorks application will connect to the Altair
web site help automatically.
32
The help server on UNIX platforms does not support tilde (~) completion of paths.
Please make sure that you use the full path for the items HW_MSG_HELP and
HW_MSG_BROWSER if you set them as environment variables or in hwhelp.cfg. (e.g.
Use /path/to/help_user/my_help instead of ~help_user/my_help).
Option
Usage
altair/scripts/help
help
hw
hwd
hwsolvers
hwe
hwtools
hwtut
engsol
mfs
mathsol
mbdsol
hst
33
hc
hvp
sv
34
35
Platform
AcuSolve-V1.8a-WIN32.msi
Windows (32-bit)
0.6
AcuSolve-V1.8a-WIN64.msi
Windows (64-bit)
0.6
AcuSolve-V1.8a-LINUX.gz
Linux (32-bit)
0.5
AcuSolve-V1.8a-LINUX64.gz
Linux (64-bit)
0.7
Required space
Windows (32-bit)
1.36 GB
Windows (64-bit)
1.53 GB
Linux (32-bit)
1.4 GB
Linux (64-bit)
2.0 GB
http://www.activestate.com/activeperl/downloads
36
On Windows
Follow the steps described below to install the distribution on a Windows XP/Vista/7 or Windows
XP64/XP/Vista7 platform.
1. Download the package and save the file to a temporary directory, for example, /usr/tmp. Go to
the directory.
2. Double click on the self extracting executables to start the installation and follow the installation
wizard to complete the process.
3. Connect to the Altair license server as described in Section 3.2.
37
On Linux/Unix
ALTAIR_LICENSE_PATH=6200@server.foo.bar.com
ALTAIR_LICENSE_PATH=6200@srv1:6200@srv2:6200@srv3
ALTAIR_LICENSE_PATH=/usr/local/altair/licensing11.0/altair_lic.dat
For High Availability License (HAL) System and/or Multiple Servers setups, list the three servers in the
order: primary; secondary; tertiary.
3. Specify the location of the HyperWorks installation home directory. The path can be typed in the
space provided or the user can navigate for the path via the Browse button.
4. Click Ok to install and update the placeholders of a HyperWorks installation and link to the
AcuSolve CFD Solutions. The Cancel button will abort the integration process to install and link
AcuSolve CFD Solutions with HyperWorks. The Help button provides and displays additional
information about the program.
5. These steps update the placeholders created within the HyperWorks installation by copying the
files acuConsole.bat, acuJob.bat and acusim.bat from the AcuSolve installation.
6. After a successful install/update and link of the HyperWorks installation the dialog below will be
displayed. If the install/update was unsuccessful, then a dialog will be displayed providing
possible reasons for the failures.
7. The AcuConsole GUI is launched using the Start Menu item AcuConsole. AcuSolve and other
post processing tools can be launched with the Start Menu item AcuSolve Job Launcher.
8. To launch a command prompt in which all the AcuSolve environment variables are set, click on
Start Menu item AcuSolve Cmd Prompt. From this command prompt, you can launch all
AcuSolve related applications such as AcuSolve, AcuConsole, etc.
39
3. Specify the location of the HyperWorks installation home directory. The path can be typed in the
space provided or the user can navigate for the path via the Browse button.
4. Click Ok to install and update the placeholders of a HyperWorks installation and link to the
AcuSolve CFD Solutions. The Cancel button will abort the integration process to install and link
AcuSolve CFD Solutions with HyperWorks. The Help button provides and displays additional
information about the program.
5. These steps update the placeholders created within the HyperWorks installation by copying three
scripts, acuConsole.sh, acuJob.sh and acusim.sh, from the AcuSolve installation to the
HyperWorks installation:
<HyperWorks_Install_dir>/scripts/invoke/.
6. After a successful install/update and link of the HyperWorks installation the below dialog will be
displayed. If the install/update was unsuccessful then a dialog will be displayed providing
possible reasons for the failures.
7. The AcuConsole GUI is launched using the script, acuconsole.sh. AcuSolve and other post
processing tools can be launched by executing the script, acujob.sh.
8. A terminal with all the AcuSolve environment variables can also be launched using the script,
acusim.sh
40
Customer Benefits
This new approach allows Altair to reach an impressive level of scalability. RADIOSS HMPP can
scale up to 512 cores and more for a real performance breakthrough.
RADIOSS HMPP is independent of the computer architecture, more flexible and efficiently adapted to
any hardware resources. It can run on distributed memory machines, shared memory machines,
workstation cluster, or a high performance computation cluster. It can better exploit the inside power
of highly multi-core machines and optimize the software according to the hardware.
It decreases installation and maintenance costs by having a unique parallel version instead of 2 types
of executables.
It improves the quality of the code in term of numerical results by having a full convergence between
SMP and SPMD results. Parith/ON gives a unique answer independent of the number of SPMD
domains and the number of SMP threads used.
Example:
In the example below, the hardware is composed of n nodes of a cluster. Each node is a dual
processor machine and each processor is a dual core. On each node the memory is shared between
processors but the memory is distributed between the nodes.
41
Network Interconnect
Node1
Node2
M1
NodeN
M2
Mn
Socket1
Socket2
Socket1
Socket2
C1
C2
C3
C4
C1
C2
C3
T
H
R
E
A
D
T
H
R
E
A
D
T
H
R
E
A
D
T
H
R
E
A
D
T
H
R
E
A
D
T
H
R
E
A
D
...
Socket1
Socket2
C4
C1
C2
C3
C4
T
H
R
E
A
D
T
H
R
E
A
D
T
H
R
E
A
D
T
H
R
E
A
D
T
H
R
E
A
D
T
H
R
E
A
D
Example of Hybrid version, where each SPMD domain uses 2 SMP threads
With the Hybrid version, it is easy to optimize the software to run on such complex architecture. On
the figure above, each SPMD domain is computed by a different processor. The number of threads
per domain is set to two, so each core of a processor is running a thread of the associated SPMD
domain.
42
As an alternative, this can be set without changing the input, directly from the RADIOSS Starter
command line:
./s_11.0_linux64 nspmd 16 nthread 2 i ROOTNAME_0000.rad
Notes:
-np value of mpirun must match nspmd value (or Nspmd input field)
This chapter covers information you need to install RADIOSS HMPP on various platforms.
Notes:
In order to facilitate transition to the HMPP version, it is possible to bypass MPI installation and use
special binaries only SMP capable (see table below). They work the same and give same numerical
answers, except that they do not require MPI and do not need mpirun to start but are restricted to
Nspmd=1. To avoid confusion, the HMPP Engine executables are suffixed with their MPI libraries
(example _impi for Intel MPI). The Starter executables are common.
Under Linux and Windows, the Extended Single Precision version also exists. Such executables are
suffixed with _sp. They offer improving performance by using single precision arithmetic while
keeping reasonable accuracy.
Executable Tables
In version 11, name of executables have been reviewed in order to be more meaningful.
Double precision
HW
platform
Parallel
Starter 11.0
Engine 11.0
radflex
Platform
info
Platform
release
win32
smp
s_11.0_win32.exe
e_11.0_win32.exe
radflex_11_win32.exe
Windows
32 bits,
Intel
compiler
win32
p4win32
win64
smp
s_11.0_win64.exe
e_11.0_win64.exe
radflex_11_win32.exe
Windows
64 bits,
Intel
compiler
win64
p4win64
radflex_11_win32.exe
Windows
64 bits,
Intel
compiler,
MS MPI
win64
msmpi
p4win64_spmd
radflex_11_win32.exe
Windows
64 bits,
Intel
compiler,
Platform
MPI
win64
plmpi
hpp4win64_spmd
win64
win64
hybrid
hybrid
s_11.0_win64.exe
s_11.0_win64.exe
e_11.0_win64_msmpi.exe
e_11.0_win64_plmpi.exe
43
linux32
smp
s_11.0_pgi_linux3
e_11.0_pgi_linux32
2
radflex_11_linux32
Linux 32
bits, PGI
compiler
linux32 pgi
p4linux9
linux32
smp
s_11.0_linux32
e_11.0_linux32
radflex_11_linux32
Linux 32
bits, Intel
compiler
linux32
p4linux932
linux64
smp
s_11.0_linux64
e_11.0_linux64
radflex_11_linux32
Linux 64
bits, Intel
compiler
linux64
p4linux964
linux64
smp
s_11.0_pgi_linux6
e_11.0_pgi_linux64
4
radflex_11_linux32
Linux 64
bits, PGI
compiler
linux64 pgi
linux964
linux64
hybrid
s_11.0_pgi_linux6
e_11.0_pgi_linux64_opmpi
4
radflex_11_linux32
Linux 64
bits, PGI
compiler,
Open MPI
linux64 pgi
opmpi
oplinux964_spmd
linux64
hybrid
s_11.0_pgi_linux6
e_11.0_pgi_linux64_plmpi
4
radflex_11_linux32
Linux 64
bits, PGI
compiler,
Platform
MPI
linux64 pgi
plmpi
hplinux964_spmd
linux64
hybrid
s_11.0_linux64
radflex_11_linux32
Linux 64
bits, Intel
compiler,
Intel MPI
linux64
impi
p4linux964_spmd
linux64
plmpi
hpp4linux964_spmd
e_11.0_linux64_impi
linux64
hybrid
s_11.0_linux64
e_11.0_linux64_plmpi
radflex_11_linux32
Linux 64
bits, Intel
compiler,
Platform
MPI
linuxia64
smp
s_11.0_linuxia64
e_11.0_linuxia64
radflex_11_linuxia64
Linux
Itanium 64
bits, Intel
compiler
linuxia64
il9
radflex_11_linuxia64
Linux
Itanium 64
bits, Intel
compiler,
Platform
MPI
linuxia64
plmpi
il9hp_spmd
linuxia64
sgimpi
il9sgi_spmd
linuxia64
hybrid
s_11.0_linuxia64
e_11.0_linuxia64_plmpi
linuxia64
hybrid
s_11.0_linuxia64
e_11.0_linuxia64_sgimpi
radflex_11_linuxia64
Linux
Itanium 64
bits, Intel
compiler,
SGI MPI
aix64
smp
s_11.0_aix64
e_11.0_aix64
radflex_11_aix64
AIX 64 bits,
IBM
compiler
aix64
pwr4
aix64
hybrid
s_11.0_aix64
e_11.0_aix64_aixmpi
radflex_11_aix64
AIX 64 bits,
IBM
compiler,
POE MPI
aix64
aixmpi
pwr4_spmd
solarisx64
smp
s_11.0_solarisx64 e_11.0_solarisx64
radflex_11_solarisx64
Solaris 64
bits, SUN
compiler
solarisx64
sol10x64
solarisx64
hybrid
s_11.0_solarisx64 sol10x64_mpp
radflex_11_solarisx64
Solaris 64
bits, SUN
compiler,
SUN MPI
solarisx64
sunmpi
sol10x64_spmd
macosx64
smp
s_11.0_macosx64
radflex_11_macosx64
Mac OS/X
64 bits,
Intel
compiler
macosx
macosx64
black
available executables
grey
depreciated executables
e_11.0_macosx64
44
Single precision
HW
platform
Parallel
Starter 11.0
Engine 11.0
radflex
Platform info
Platform release
win32
smp
s_11.0_win32_sp.exe
e_11.0_win32_sp.exe
radflex_11_win32.exe
Windows 32 bits,
Intel compiler,
single precision
win32 sp
win64
smp
s_11.0_win64_sp.exe
e_11.0_win64_sp.exe
radflex_11_win32.exe
Windows 64 bits,
Intel compiler,
single precision
win64 sp
win64
hybrid
s_11.0_win64_sp.exe
e_11.0_win64_msmpi_sp.exe
radflex_11_win32.exe
Windows 64 bits,
Intel compiler, MS
MPI, single
precision
win64 msmpi sp
win64
hybrid
s_11.0_win64_sp.exe
e_11.0_win64_plmpi_sp.exe
radflex_11_win32.exe
Windows 64 bits,
Intel compiler,
Platform MPI,
single precision
win64 plmpi sp
linux32
smp
s_11.0_pgi_linux32_sp
e_11.0_pgi_linux32_sp
radflex_11_linux32
linux32 pgi sp
linux32
smp
s_11.0_linux32_sp
e_11.0_linux32_sp
radflex_11_linux32
linux32 sp
linux64
smp
S_11.0_linux64_pgi_sp
E_11.0_linux64_pgi_sp
radflex11_linux32
linux64 pgi sp
linux64
smp
s_11.0_linux64_sp
e_11.0_linux64_sp
radflex_11_linux32
linux64 sp
linux64
hybrid
s_11.0_pgi_linux64
e_11.0_pgi_linux64_opmpi_sp
radflex_11_linux32
linux64
hybrid
s_11.0_pgi_linux64
e_11.0_pgi_linux64_plmpi_sp
radflex_11_linux32
linux64
hybrid
s_11.0_linux64_sp
e_11.0_linux64_impi_sp
radflex_11_linux32
linux64 impi sp
linux64
hybrid
s_11.0_linux64_sp
e_11.0_linux64_plmpi_sp
radflex_11_linux32
linux64 plmpi sp
linuxia64
smp
s_11.0_linuxia64_sp
e_11.0_linuxia64_sp
radflex_11_linuxia64
Linux Itanium 64
bits, Intel
compiler, single
precision
linuxia64 sp
radflex_11_linuxia64
Linux Itanium 64
bits, Intel
compiler, Platform
MPI, single
precision
linuxia64 plmpi sp
linuxia64 sgimpi sp
solarisx64 sp
linuxia64
linuxia64
hybrid
hybrid
solarisx64 smp
s_11.0_linuxia64_sp
e_11.0_linuxia64_plmpi_sp
s_11.0_linuxia64_sp
e_11.0_linuxia64_sgimpi_sp
radflex_11_linuxia64
Linux Itanium 64
bits, Intel
compiler, SGI
MPI, single
precision
s_11.0_solarisx64_sp
e_11.0_solarisx64_sp
radflex_11_solarisx64
Solaris 64 bits,
SUN compiler,
45
single precision
solarisx64 hybrid
s_11.0_solarisx64_sp
e_11.0_solarisx64_sunmpi_sp
radflex_11_solarisx64
Solaris 64 bits,
SUN compiler,
SUN MPI, single
precision
solarisx64 sunmpi sp
macosx64 smp
s_11.0_macosx64_sp
e_11.0_macosx64_sp
radflex_11_macosx64
macosx sp
black
available executables
grey
depreciated executables
Hostfile:
All the nodes of the cluster must be declared in a text file named "hostfile". The syntax of this file
is as follows:
Example: to set the hostfile with two nodes with four and two processors (host1 4, host2 2), the
hostfile will have the following pattern:
[radioss@host1] more hostfile
46
host1
host1
host1
host1
host2
host2
where:
[n]: is the number of SPMD domains.
[t]: is the number of SMP threads per domain.
[ROOTNAME]: is the rootname of the dataset.
The SGI Propack 4 packages need to be installed. Array service must be activated.
radioss@host1~]$ cp
$ALTAIR_HOME/hwsolvers/bin/linuxia64/radflex_11_linux32
[radioss@host1~]$ $ALTAIR_HOME/hwsolvers/bin/linuxia64/s_11.0_linuxia64
-input [ROOTNAME]_0000.rad np [n]
[radioss@host1~]$ mpirun -np [n]
$ALTAIR_HOME/hwsolvers/bin/linuxia64/e_11.0_linuxia64_sgimpi input
[ROOTNAME]_0001.rad nt [t]
where:
[n]: is the number of SPMD domains
[t]: is the number of SMP threads per domain
[ROOTNAME]: is the rootname of the dataset
RSH installation:
HP MPI uses rsh to launch RADIOSS on all different nodes. Computation nodes need to be
accessed by all other nodes without typing password. Refer to the rsh man pages or Linux pam.d
daemon for installation instructions.
To check the functionality of rsh, following test can be performed on the different nodes:
[radioss@host1] rsh host1 ls
[radioss@host1] rsh host2 ls
...
[radioss@host1] rsh host[n] ls
[radioss@host1~]$ $ALTAIR_HOME/hwsolvers/bin/linuxia64/s_11.0_linuxia64
-input [ROOTNAME]_0000.rad np [Nspmd]
[radioss@host1~]$ [HP MPI path]/bin/mpirun -stdio=i0 [-TCP|-GM|-ITAPI|ELAN] -f appfile -- -input [ROOTNAME]_0001.rad nt [t]
where:
-np [Nspmd] : Specifies the number of SPMD domains for RADIOSS Starter
[HP MPI path]: is the PATH where HP MPI is installed
[-TCP|-GM|-ITAPI|-ELAN] : To set the Interconnect to use
[ROOTNAME]: is the rootname of the dataset
-nt[t]: is the number of SMP threads per SPMD domain
[appfile]: is a file describing each node of the computation. This file is as follows:
-h host1 -e MPI_FLAGS=y,E -e MPI_WORKDIR=[Computation path] -np [n]
[Engine path]/e_11.0_linuxia64_plmpi
-h host2 -e MPI_FLAGS=y,E -e MPI_WORKDIR=[Computation path] -np [n]
[Engine path]/e_11.0_linuxia64_plmpi
-h host3 -e MPI_FLAGS=y,E -e MPI_WORKDIR=[Computation path] -np [n]
[Engine path]/e_11.0_linuxia64_plmpi
...
-h hostp -e MPI_FLAGS=y,E -e MPI_WORKDIR=[Computation path] -np [n]
[Engine path]/e_11.0_linuxia64_plmpi
51
The account used to run RADIOSS must exist on every cluster's node.
RADIOSS executables must be reachable from all cluster nodes (same path on all nodes).
The computation directory must be the same (same path) on all cluster nodes.
SSH/RHS installation:
HP MPI uses ssh to launch RADIOSS on all different nodes. Computation nodes need to be
accessed by all other nodes without typing a password. Refer to ssh man pages to generate and
install properly rsa keys (ssh-keygen tool).
To check the functionality of ssh, the following test can be performed on the different nodes:
[radioss@host1] ssh host1 ls
[radioss@host1] ssh host2 ls
...
[radioss@host1] ssh host[n] ls
52
Alternatively rsh can be used. To enable rsh, the MPI_REMSH environment variable must be set to
rsh:
[radioss@host1] setenv MPI_REMSH rsh
HP MPI installation:
HP MPI is distributed by HP as a Linux rpm. It must be installed having root privilege on each node
running the command (please refer to the HP MPI release notes for more information):
rpm Uvh hpmpi-2.02.05-??.x86_64.rpm
On a cluster:
[radioss@host1~]$ cp
$ALTAIR_HOME/hwsolvers/bin/linux64/radflex_11_linux32
[radioss@host1~]$ $ALTAIR_HOME/hwsolvers/bin/linux64/s_11.0_linux64
input [ROOTNAME]_0000.rad np [Nspmd]
54
stacksize limit
stacksize limit must be set to unlimited with an unlimited value of more than 400Mbytes.
KMP_STACKSIZE environment variable, the stacksize per thread, must also be set to 400Mbytes.
Example under csh:
limit stacksize unlimited
setenv KMP_STACKSIZE 400m
memlock limit
The file /etc/security/limits.conf should be check and modified to contain the line below:
* soft memlock unlimited
* hard memlock unlimited
This will avoid error in case the memlock limit is not enough.
3. If the cluster network is Infiniband using OFED drivers: the Linux kernel level must be 2.6.18 or
higher, the OFED drivers must be OFED 1.3 or higher.
4. It is highly recommended to have the same hardware and OS level on all nodes.
5. The MPI library: is Intel MPI intel-mpi-em64t-3.2 or above.
The Intel MPI runtime kit is available for free at http://www.intel.com.
The account used to run RADIOSS must exist on every cluster's node.
RADIOSS executables must be reachable from all cluster nodes (same path on all nodes).
The computation directory must be the same (same path) on all cluster nodes.
RHS installation:
Intel MPI uses rsh to launch RADIOSS on all different nodes. Computation nodes need to be
accessed by all other nodes without typing passwords. Refer to the rsh man pages or Linux pam.d
daemon for installation instructions.
To check the functionality of rsh, the following test can be performed on the different nodes:
[radioss@host1] rsh host1 ls
[radioss@host1] rsh host2 ls
...
[radioss@host1] rsh host[n] ls
56
-r [rsh]: is the remote shell command used. If ssh is chosen, use -r ssh
5. Check that all daemons are correctly launched.
The mpdtrace tool checks if all nodes are available for Intel MPI. The result is the printout of all
hostnames on which Intel MPI is ready to be run:
[radioss@host1~]$[path to INTEL MPI]/bin64/mpdtrace
host1
host2
...
host[n]
More details about launching the Intel MPI daemons can be found in the Getting-started.pdf
document present in [path to intel mpi]/doc.
To use other interconnects, you need to set the I_MPI_DEVICE environment variable:
I_MPI_DEVICE can have following values:
rdma[:] InfiniBand*, Myrinet*, etc. (via specified DAPL* provider)
rdssm[:] TCP + shared-memory + DAPL* (for SMP clusters connected via
RDMA capable fabrics). This is the recommended value.
I_MPI_PIN_DOMAIN
On some old systems, setting I_MPI_PIN_DOMAIN to auto may not work properly if the
system is not affinity capable (see KMP_AFFINITY). In this case it is advised to set
I_MPI_PIN_DOMAIN to omp.
58
I_MPI_ADJUST_BCAST
I_MPI_ADJUST_REDUCE
KMP_AFFINITNY
In order to check if the system is affinity capable, the user may set KMP_AFFINITY to
verbose.
OMP_NUM_THREADS
Instead of using nt parameter, the user can set the number of threads the using
environment variable OMP_NUM_THREADS. Using this environment variable may help the
system to better determine affinity (see KMP_AFFINITY=verbose).
LD_LIBRARY_PATH
You need to set the LD_LIBRARY_PATH to the path where the vendor libdapl.so is
installed. Check the Interconnect vendor for availability of libdapl.so library.
The use of libdapl.so requires kernel 2.6.18 or newer to be installed on the machine.
Example:
[radioss@host1~]$setenv LD_LIBRARY_PATH /usr/local/ibgd/lib
[radioss@host1~]$setenv I_MPI_DEVICE rdssm
[radioss@host1~]$setenv I_MPI_PIN_DOMAIN auto
[radioss@host1~]$setenv KMP_AFFINITY compact
host1:4
host2:4
host3:4
host4:4
memlock limit
The file /etc/security/limits.conf should be checked and modified to contain the line below:
* soft memlock unlimited
61
SSH installation:
SUNWhpc default installation uses ssh to launch RADIOSS on all different nodes. ssh needs to be
configured to permit the connection on all hosts of the cluster without typing passwords. Refer to ssh
man pages to generate and properly install rsa keys (ssh-keygen tool)
To check the functionality of ssh, the following test can be performed on the different nodes:
[radioss@host1] ssh host1 ls
[radioss@host1] ssh host2 ls
...
[radioss@host1] ssh host[n] ls
62
LD_LIBRARY_PATH variable
The radflex_11_solarisx64 tool needs the liblmx-altair.so library from HyperWorks 11
installation. Set the LD_LIBRARY_PATH environment to $ALTAIR_HOME/hw/lib/solarisx64 :
[radioss@host1] setenv LD_LIBRARY_PATH $ALTAIR_HOME/hw/lib/solarisx64.
The MPI libraries are dynamically linked. To make the executables work, LD_LIBRARY_PATH needs
to be set to the path to low level interconnect driver libraries if used and the path to SUNWhpc
libraries.
In csh shell:
[radioss@host1~]$ setenv LD_LIBRARY_PATH /opt/SUNWhpc/lib/amd64/
In sh/ksh/bash shell:
LD_LIBRARY_PATH=/opt/SUNWhpc/lib/amd64/
[radioss@host1~]$ export LD_LIBRARY_PATH
The result of ldd must be as follows:
[radioss@host1 ]$ ldd e11_solarisx64_sunmpi
libm.so.2 => /lib/64/libm.so.2
libkstat.so.1 => /lib/64/libkstat.so.1
libmpi.so.0 =>
/opt/SUNWhpc/lib/amd64/libmpi.so.0
libmpi_f77.so.0 => /opt/SUNWhpc/lib/amd64/libmpi_f77.so.0
libfui.so.2 =>
/opt/SUNWspro/lib/amd64/libfui.so.2
libfai.so.1 =>
/opt/SUNWspro/lib/amd64/libfai.so.1
libfsu.so.1 =>
/opt/SUNWspro/lib/amd64/libfsu.so.1
libsunmath.so.1 => /opt/SUNWspro/lib/amd64/libsunmath.so.1
libmtsk.so.1 => /lib/64/libmtsk.so.1
libc.so.1 =>
/lib/64/libc.so.1
libopen-rte.so.0 => /opt/SUNWhpc/lib/amd64//libopen-rte.so.0
libopen-pal.so.0 => /opt/SUNWhpc/lib/amd64//libopen-pal.so.0
libdl.so.1 =>
/lib/64/libdl.so.1
libsocket.so.1 => /lib/64/libsocket.so.1
libnsl.so.1 =>
/lib/64/libnsl.so.
librt.so.1 =>
/lib/64/librt.so.1
libm.so.1 =>
/lib/64/libm.so.1
libpthread.so.1 => /lib/64/libpthread.so.1
libmp.so.2 =>
/lib/64/libmp.so.2
libmd.so.1 =>
/lib/64/libmd.so.1
libscf.so.1 =>
/lib/64/libscf.so.1
libaio.so.1 =>
/lib/64/libaio.so.1
libdoor.so.1 => /lib/64/libdoor.so.1
libuutil.so.1 => /lib/64/libuutil.so.1
libgen.so.1 =>
/lib/64/libgen.so.1
On a Solaris 10 cluster:
[radioss@host1~]$ cp
$ALTAIR_HOME/hwsolvers/bin/sun10x64/radflex_11_solarisx64
[radioss@host1~]$
$ALTAIR_HOME/hwsolvers/bin/sun10x64/e_11.0_solarisx64_sunmpi -input
[ROOTNAME]_0000.rad np [n]
[radioss@host1~]$ /opt/SUNWhpc/bin/mpirun --mca btl
[tcp|openib|mvapi|gm|mx],self -hostfile [hf] -np [n]
$ALTAIR_HOME/hwsolvers/bin/sun10x64/e_11.0_solarisx64_sunmpi -input
[ROOTNAME]_0001.rad nt [t]
where:
--mca btl [tcp|openib|mvapi|gm|mx],self: is the interconnect flag to set according to
the cluster's interconnect. This setting must belong to the configured interconnect.
[hf]: is a file containing the node's hostname for each processor of the computation.
[n]: is the number of SPMD domains.
-nt[t]: is the number of SMP threads per SPMD domain.
[ROOTNAME]: is the rootname of the dataset.
Notes
1. --mca btl [interconnect],self flag :
These flags must be set properly according to the cluster network interconnect :
a. On a Infiniband cluster with OPEN-IB drivers, the set is: --mca btl openib,self
b. On a cluster with Gigabit, the set is: --mca btl tcp,self
If the cluster has only Gigabit interconnect, the --mca flag can be left.
Opteron machines can benefit from the memory affinity flag. This improves the performance due to
better memory processor affinity on Opteron processors. The flag to set is : --mca
mpi_paffinity_alone 1
The hostfile [hf] is a text file with hosts specified one per line. Each host can also specify a
maximum number of slots to be used on that host (that is, the number of available processors on that
host). Comments are also supported.
For example:
64
The executable and the RADIOSS data sets need to be reachable by the cluster.
Data sets and RADIOSS executing environment must be accessible from all nodes (computation and
master node) using shared file systems.
To set cluster-wide environment variables (example: ALTAIR_LM_LICENSE_FILE) use the cluscfg
command. This tool requires cluster administrative rights. Refer to the Compute Clusters Users
Guide for more information.
PATH environment setting:
The radflex_11_win64 tool needs the liblmx-altair.dll library from HyperWorks 11
installation.
Add to the PATH environment variable: %ALTAIR_HOME%/hw/bin/win64
<Tasks xmlns="http://www.microsoft.com/ComputeCluster/">
<Task MaximumNumberOfProcessors="1" MinimumNumberOfProcessors="1"
Depend="" WorkDirectory="%WORKDIR%" Name="Copy radflex_11_win32.exe"
CommandLine="copy %ALTAIR_HOME%\hwsolvers\bin\win64\radflex_11_win64.exe
." IsExclusive="false" IsRerunnable="true" Runtime="Infinite">
<EnvironmentVariables />
</Task>
<Task MaximumNumberOfProcessors="1" MinimumNumberOfProcessors="1"
Depend="" WorkDirectory="%WORKDIR%" Stdout="Starter.out"
Stderr="Starter_err.out" Name="Run Starter"
CommandLine="%ALTAIR_HOME%\hwsolvers\bin\win64\s_11.0_win64.exe input
[ROOTNAME]_0000.rad -np n" IsExclusive="true" IsRerunnable="false"
Runtime="Infinite">
<EnvironmentVariables />
</Task>
<Task MaximumNumberOfProcessors="4" MinimumNumberOfProcessors="4"
Depend="" WorkDirectory="%WORKDIR%" Stdin="" Stdout="Engine.out"
Stderr="Engine_err.out" Name="Run Engine" CommandLine="mpiexec -hosts
%CCP_NODES% %ALTAIR_HOME%\hwsolvers\bin\win64\e_11.0_win64_msmpp.exe
input [ROOTNAME]_0001.rad nt t" IsExclusive="true" IsRerunnable="false"
Runtime="Infinite">
<EnvironmentVariables />
</Task>
</Tasks>
</Job>
%WORKDIR% with the path to the working directory. The path must be absolute and include
the file server. Example: //fileserver/C$/EXECUTION
The first task copies radflex11_win32.exe from the installation path to the work directory.
Change the WorkDirectory entry according to the place where your data set runs. Use
network path syntax.
The second task launches RADIOSS Starter. Change the Stdin field to set the Starter input
data set and the WorkDirectory entry according to the place where your data set runs.
Use network path syntax.
67
equal. Set the WorkDirectory entry according to the place where your data set runs (use
network path syntax) and then set the Stdin field to set the Engine input data set.
68
69
Task number 2 is the Starter task. Check the Standard Input and the Work Directory fields.
70
71
The job can be saved as an xml template file to save any changes made in the job form. Click
Save As Template to save the job.
72
The account used to run RADIOSS must exist on every cluster's node.
RADIOSS executables must be reachable from all cluster nodes (same path on all nodes).
The computation directory must be the same (same path) on all cluster nodes.
HP MPI installation:
HP MPI is distributed by HP as a Windows executable. It must be installed having Administrator
privilege on each node executing the package:
HP-MPI-V2.0-060409.exe
4.8.e Troubleshooting
Use of Standard-in redirection in HP MPI for Windows64
Do not redirect the Engine input file, but use the engine input command line argument. The
redirection may cause an RADIOSS Engine to hang.
76
Task is a minimum distribution unit used in the parallelization. Each buckling analysis counted as subcase is one task. Each
Left-Hand Side (LHS) of static analysis subcases is counted as one task. Typically, the static analysis subcases sharing the
same SPC belong to a same task. Note that not all tasks can be run in parallel at the same time (e. g. buckling subcase can not
start before its STATSUB subcase finishes.).
77
Interconnection
CPU
CPU
CPU
Interconnection
M1
CPU1
CPU2 CPUn
Mn
CPU1
CPU2 CPUn
OptiStruct SPMD
Version
11.0
Platforms Supported
Notes
LINUX32, LINUX-ITANIUM,
LINUX64
Requires HP-MPI
(version 02.02.05.01)
OR Platform-MPI
(version 7.1)
OR Intel MPI
(version 3.2.011)
78
OptiStruct SPMD
OptiStruct SPMD
11.0
11.0
AIX
Requires IBMs
PPE.POE (version
3.2.0.0)
Requires HP-MPI
(version 2.0)
OR Platform-MPI
(version 7.1)
OR MS-MPI
(version Windows
HPC)
SSH Installation
HP-MPI default installation uses ssh to launch OptiStruct SPMD on all different nodes. ssh needs to
be configured to permit the connection on all hosts of the cluster without typing passwords. Refer to
ssh manual pages to generate and install rsa keys ( ssh-keygen tool).
To check the functionality of ssh, the following test can be performed on the different nodes:
[optistruct@host1] ssh host1 ls
[optistruct@host1] ssh host2 ls
...
[optistruct@host1] ssh host[n] ls
79
HP-MPI installation
HP-MPI needs to be reachable on all computation nodes on which OptiStruct SPMD will be launched.
1. Download the HP-MPI images for the platform you desire to use from the Altair ftp site.
2. Install the HP-MPI package on each node.
[root@host[i]]rpm -ivh hpmpi-2.02.05.01-20070708r[platform].rpm
Note: No license is needed for HP-MPI to run OptiStruct SPMD
3. Add $MPI_ROOT/hpmpi/lib/[platform] into LD_LIBRARY_PATH if needed.
Platform-MPI installation
Platform-MPI needs to be reachable on all computation nodes on which OptiStruct SPMD will be
launched.
1. Download the Platform-MPI images for the platform you desire to use from the Altair ftp site.
2. Install the Platform-MPI package on each node.
[root@host[i]]rpm -ivh platform_mpi-7.01.00-20091019r.[platform].rpm
Note: No license is needed for Platform-MPI to run OptiStruct SPMD
3. Add $MPI_ROOT/platform_mpi/lib/[platform] into LD_LIBRARY_PATH if needed.
Intel-MPI installation
Intel-MPI needs to be reachable on all computation nodes on which OptiStruct SPMD will be
launched.
1. Download the Intel-MPI images for the platform you desire to use from the Altair ftp site.
2. Install the Intel-MPI package on each node.
[root@host[i]] ./install.sh
Note: license is needed to install Intel-MPI libraries.
Note: No license is needed to for Intel-MPI to run OptiStruct SPMD.
3. Add $MPI_ROOT/intel/impi/3.2.2.006/lib into LD_LIBRARY_PATH if needed.
80
5.3.a On a single host (for HP-MPI, Platform-MPI and Intel MPI) using solver
script
[optistruct@host1~]$ $ALTAIR_HOME/path/to/optistruct_script mpi [MPI_TYPE] np [n]
[INPUTDECK] [OS_ARGS]
where:
optistruct_script: is the OptiStruct script
[MPI_TYPE]: is the mpi implementations used:
pl for HP-MPI and Platform-MPI
i for Intel MPI
[n] : is the number of processors
[INPUTDECK] : is the input deck file name
[OS_ARGS] : is the arguments to OS SPMD
Note: Adding command line option -testmpi verifies your MPI installation and setup.
5.3.c
81
Example: 4 CPU job on 2 dual-CPU hosts (the 2 machines are named : c1,c2)
[optistruct@host1~]$ cat appfile
-h c1 np 2 $ALTAIR_HOME/path/to/optistruct_spmd [INPUTDECK] -mpimode
-h c2 np 2 $ALTAIR_HOME/path/to/optistruct_spmd [INPUTDECK] mpimode
82
POE installation
IBMs PPE POE needs to be installed on all computation nodes on which OptiStruct SPMD will be
launched.
Note: OptiStruct SPMD must match the MPI implementation you use.
5.7.a On a single host using solver script (for HP-MPI, Platform-MPI and MSMPI)
[optistruct@host1~]$ $ALTAIR_HOME/path/to/optistruct_script mpi [MPI_TYPE] np [n]
[INPUTDECK] [OS_ARGS]
where:
optistruct_script: is the OptiStruct script
[MPI_TYPE]: is the mpi implementations used:
pl for HP-MPI and Platform-MPI
ms for MS-MPI
[n] : is the number of processors
[INPUTDECK] : is the input deck file name
[OS_ARGS] : is the arguments to OS SPMD
Note: Adding command line option -testmpi verifies your MPI installation and setup.
Example: 4 CPU job on 2 dual-CPU hosts (the 2 machines are named: c1,c2)
85
Example: 4 CPU job on 2 dual-CPU hosts (the 2 machines are named : c1,c2)
[optistruct@host1~]$ cat hostfile
-host c1 n 2 $ALTAIR_HOME/path/to/optistruct_spmd [INPUTDECK] -mpimode
-host c2 n 2 $ALTAIR_HOME/path/to/optistruct_spmd [INPUTDECK] mpimode
delay. Multiple tasks on the same machine may compete for disk access, and (in extreme situation)
even result in wall clock time slower than that for serial (non MPI) run. (See also questions 5.8.6.)
5.8.e Will OptiStruct SPMD use less memory on each node than in the serial
run?
No. Memory estimates for serial run and parallel run on each node are the same. They are based on
the solution of a single (most demanding) subcase.
5.8.f Will OptiStruct SPMD use less disk space on each node than in the serial
run?
Yes. Disk space usage on each node will be smaller, because only temporary files related to task(s)
solved on this node will be stored. But the total amount of the disk space will be larger than that in the
serial run and this can be noticed, especially in the parallel run on a shared memory machine.
87
Appendix A: HyperWorks
Directory Structure
HyperWorks UNIX Directory Structure
This is a sample of the typical HyperWorks Installation directory.
bin
icons
io
javaapps
hdm
hwa
pmgr
logs
scripts
security
altair_lic.dat
bin
platform
almutil.exe, lmxconfigtool.exe, lmxendutil.exe
templates
tutorials
uninstalls
utility
The following list identifies the application and its directory name used in the installation directory.
88
Application
Directory Name
BatchMesher
hm
Data Manager
javaapps
HyperMesh Client
hw
HyperGraph
hw
HyperGraph 3D
hw
HyperMath
hmx
HyperMesh
hm
HyperStudy
hst
HyperView
hw
HyperView Player
hw
MotionView
hw
MotionSolve
hwsolvers
Manufacturing Solutions
hm and hx
MediaView
hw
OptiStruct
hwsolvers
RADIOSS
hwsolvers
HyperCrash
hc
Process Manager
javaapps
TextView
hw
89
The NETSETUP directory appears only if Software Server was chosen as installation
type.
90
Appendix B: Recommended
Graphic Boards
The following table lists the recommended CAE/CAD graphic boards for use with the Altair
HyperWorks suite of applications. Please note that the most recent vendor drivers should be used
and all driver support for these cards should be addressed to the appropriate manufacturer of the
graphic board. Performance of HyperWorks may be degraded with compositing desktop efforts
enabled under Linux.
Note: HyperWorks 11.0 sets the environment variable XLIB_SKIP_ARGB_VISUALS=1 in the startup
scripts, which may degrade GUI menu performance. To override this option set the variable
XLIB_SKIP_ARGB_VISUALS=0 within the systems our users environment.
91
92
WINDOWS
UGII_BASE_DIR
UGII_ROOT_DIR
PATH
UGS_LICENSE_SERVER
UGS_LICENSE_BUNDLE
LINUX
UGII_BASE_DIR
UGII_ROOT_DIR
93
UGS_LICENSE_SERVER
UGS_LICENSE_BUNDLE
94
The HyperWorks installer will now extract the JVM (Java Virtual Machine) and the install modules
to the TMP location of the machine.
2. The multi-language selector prompt will be displayed. Select the proper locale and click OK to
continue. The default locale setting is specific to the install machine regional settings.
NOTE: The language selection only corresponds to the installer settings not to the HyperWorks
product language settings. Altair HyperWorks products are in English.
95
3. The Introduction and Copyright panels are displayed for viewing. Click Next to continue.
4. The Choose Installation Type panel is displayed. Choose install type Local for this example and
click Next.
5. The Choose Install Folder panel is displayed. Choose install path and click Next. The default
will be used for this example.
a. The default path is C:\Program Files\Altair\11.0 for Windows and the users
home folder and installer version on Linux/Unix.
b. The installer does not allow the use of characters # and ;
c.
96
6. The Choose Shortcut Folder panel is displayed. This allows for users to customize:
a. Start Menu Folder name. The default is Altair HyperWorks 11.0 (64-bit), where the bit type
is dependent on the version of the installer.
b. Whether or not to install Desktop shortcuts. The default option is set to not install desktop
shortcuts.
Choose the preferred options and click Next to continue. Default options used in this example.
7. The Choose Install Set panel is displayed. Select Custom installer type and click Next to
continue.
97
a. Selecting Custom will allow for choosing selective products and help files install
combinations.
b. If Help Files is selected then the corresponding help installer executable must reside in the
same directory as the installer to be installed. E.g.help11_win64.exe
8. The HyperWorks AcuSolve Notice prompt message is displayed. Review message and click
OK to continue.
98
9. The Pre-Installation Summary panel is displayed. Review selections and click Install to
continue.
NOTE: Install times are machine hardware dependant. Anti-Virus software may lengthen the
install times.
10. Once the installation completes, click Done to exit the installer.
99
2. The HyperWorks installer will now extract the JVM (Java Virtual Machine) and the install modules
to the TMP location of the machine.
3. The multi-language selector prompt will be displayed. Select the proper locale and click OK to
continue. The default locale setting is specific to the install machine regional settings.
NOTE: The language selection only corresponds to the installer settings not to the HyperWorks
product language settings. Altair HyperWorks products are in English.
100
4. The Introduction and Copyright panels are displayed for viewing. Click Next to continue.
5. The Choose Installation Type panel is displayed. Choose install type Local for this example and
click Next.
NOTE: HyperView Player, SolidThinking/Inspired and AcuSolve/CFD integration is not available
in the server type installs.
6. The Choose Install Folder panel is displayed. Choose install path and click Next. The default
will be used for this example.
a. The default path is C:\Program Files\Altair\11.0 for Windows and the users home
folder and installer version on Linux/Unix.
b. The installer does not allow the use of characters # and ;
c.
101
7. The Choose Shortcut Folder panel is displayed. This allows for users to customize:
a. Start Menu Folder name. The default is Altair HyperWorks 11.0 (64-bit), where the bit type is
dependent on the version of the installer.
b. Whether or not to install Desktop shortcuts. The default option is set to not install desktop
shortcuts.
Choose preferred options and click Next to continue. Default options are used in this example.
NOTE: For Windows Server type installs the Choose Shortcut Folder (Server) panel also allows
for more customization options for users to choose the shortcut folder install location, which
defaults to the All Users shortcut folder location. For Server and Client installs, the word Server
and Client will be pre-appended to the bit type, example Altair HyperWorks 11.0 (Server 64-bit).
8. The Choose Install Set panel is displayed. Select Custom installer type and click Next to
continue.
102
a. Selecting Custom will allow for choosing selective products and help files install
combinations.
9. The UNC (Uniform Naming Convention) mount point panel is displayed if:
a. Server install type was selected.
b. The install path used contained a Windows drive letter, example C:\pathname\folder
Input the UNC path and click Next to continue.
103
NOTE: The user input needs to be in the form of the UNC standard
\\MachineName\SharedFolder\InstallFolder to be accepted.
10. The HyperWorks AcuSolve Notice prompt message is displayed. Review message and click
OK to continue.
11. The Pre-Installation Summary panel is displayed. Review selections and click Install to
continue.
NOTE: Install times are machine hardware dependant. Anti-Virus software may lengthen the
install times.
104
12. Once the installation completes, click Done to exit the installer.
NOTE: For information on installing the Clients NETSETUP please reference section V. Windows
Network Server Installs Client NETSETUP Installs of the HyperWorks Full Install Guide.
105
Preparing to install...
Extracting the JRE from the installer archive...
Unpacking the JRE...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...
Launchinginstaller...
3. The multi-language selector prompt will be displayed. Select the proper locale and click OK to
continue. The default locale setting is specific to the install machine regional settings.
NOTE: The language selection only corresponds to the installer settings not to the HyperWorks
product language settings. Altair HyperWorks products are in English.
4. The Introduction and Copyright panels are displayed for viewing. Click Next to continue.
5. The Choose Install Folder panel is displayed. Choose install path and click Next. The default
will be used for this example.
106
a. The default path is C:\Program Files\Altair\11.0 for Windows and the users home
folder and installer version on Linux/Unix.
b. The installer does not allow the use of characters # and ;
c.
6. The Choose Install Set panel is displayed. Select Custom installer type and click Next to
continue.
a. Selecting Custom will allow for choosing selective products and help files install
combinations.
107
If Help Files Help- is not selected than proceed to Step 7-b below.
b. If Help is not selected under Help Files then the Help Configuration panel will prompt the
user with three alternatives:
i.
Connect to a network installed Help location. This will prompt for the network installed
Help location and the Unix/Linux browser path and file.
108
ii.
Connect to Altair website Help (default). This will prompt for the Unix/Linux browser path
and file.
iii. Set up later. This will not install help or set up a browser for Web Help.
8. The HyperWorks AcuSolve Notice prompt message is displayed. Review message and click
OK to continue.
9. The Pre-Installation Summary panel is displayed. Review selections and click Install to
continue.
NOTE: Install times are machine hardware dependant. Anti-Virus software may lengthen the
install times.
10. Once the installation completes, click Done to exit the installer.
109
Preparing to install...
Extracting the JRE from the installer archive...
Unpacking the JRE...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...
Launching installer...
Preparing CONSOLE Mode Installation...
NOTE: If the /tmp location on the machine is full, the installer will try to use the users home
folder for temp files or the user can set the environment variable IATEMPDIR to a custom
specified TMP location.
3. The multi-language selector prompt will be displayed. Select the proper locale and click OK to
continue. The default locale language is the regional setting of the install machine. Type the
number associated to the language of choice and hit enter to continue.
NOTE: The language selection only corresponds to the installer settings not to the HyperWorks
product language settings. Altair HyperWorks products are in English.
==============================================================================
Choose Locale...
---------------1- Bahasa Indonesia
2- Catal
3- Dansk
4- Deutsch
->5- English
110
678910111213141516-
Espaol
Euskara
Franais
Franais (Canada)
Italiano
Nederlands
Norsk
Portugus
Portugus (Brasil)
Suomi
Svenska
==============================================================================
ChooseInstallFolder
Selectthepathnametothelocationwhereyouwishtoinstallthesoftware:
Wherewouldyouliketoinstall?
DefaultInstallFolder:/users/userID/hw11
ENTERANABSOLUTEPATH,ORPRESS<ENTER>TOACCEPTTHEDEFAULT
:/caeapps/hw11/
6. The Choose Install Set panel is displayed. Type the number associated to a Complete install or
Customize install and press Enter. In this example select Custom installer type and press
Enter to continue.
=============================================================================
=
Choose Install Set
-----------------Please choose the Install Set to be installed by this installer.
->1- Complete
2- Customize...
ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS <ENTER> TO ACCEPT THE
DEFAULT
:2
111
7. The Choose Product Features prompt is displayed. An X is associated to a product that will be
installed. The default list has all the HyperWorks products selected for install. In order to unselect
a product for install, type the associated number of that product to unselect it from installing.
To illustrate this functionality an example will be provided. This example will unselect all products
and then re-select only the HyperWorks Solvers and Help Files to be installed.
a. Type 1 and press Enter.
b. Type back and press Enter to go back to previous prompt.
c.
The Product Feature List will now be all unchecked. Type 7,10 to select HyperWorks
Solvers and Help Files (includes Demos, Tutorials and Help) and press Enter.
d. This will install the product features associated to 1 and 7, HyperWorks Solvers and Help
Files. To verify your selection type back and press Enter to display the updated list
selection.
This console mode installer walkthrough will continue with only the HyperWorks Solvers and Help
Files selected for install.
NOTE: The Help binary for linux64 will need to reside in the same directory location as where the
installer resides in order for the Help Files to be installed.
8. The Help Configuration prompt is displayed.
.
If Help was selected then it will prompt for the internet browser full path and file to
associate with the HyperWorks Help, like /usr/bin/firefox. Example below:
==============================================================================
HelpConfiguration
TheHyperWorks11.0Helpisselected.Enterthebrowserbelowtobeabletocorrectlydisplay
HyperWorks11.0Help.
Typewebbrowserpathincludingfile(HW_MSG_BROWSER):(DEFAULT):/usr/bin/firefox
b. If Help is not selected under Help Files then the Help Configuration prompt will have three
alternatives:
.
Connect to a network installed Help location. This will prompt for the network
installed Help location and the Unix/Linux browser path and file.
Connect to Altair website Help (default). This will prompt for the Unix/Linux
browser path and file.
Set up later. This will not install help or set up a browser for Web Help.
9. The HyperWorks AcuSolve Notice prompt message is displayed. Review message and press
Enter to continue.
10. The Pre-Installation Summary panel is displayed. Review selections and press Enter to
continue.
NOTE: Install times are machine hardware dependant. Anti-Virus software may lengthen the
install times.
11. Once the installation completes, press Enter to exit the installer.
112
Appendix H: Uninstall
HyperWorks
This Appendix describes the procedure of uninstalling HyperWorks on Windows and Linux/Unix in
various approaches.
On Windows:
1. Go to Altair HyperWorks Start Menu item.
a. Click Start > All Programs
2. Go to where the Altair HyperWorks shortcuts are located, defaults to Altair HyperWorks 11.0
(64-bit) or Altair HyperWorks 11.0 (32-bit) for Windows 64-bit and 32-bit, respectively.
3. Click Tools > Admin Tools.
4. Click on Uninstall_HyperWorks11. This will launch the uninstaller to remove the Altair
HyperWorks install from the machine.
113
Architecture
OS
Linux64_plmpi
I.2 Install and Run RADIOSS HMPP to MADYMO 7.1 MPP Coupling
I.2.a System Requirements:
1. Operating system: INTEL EM64T or AMD Opteron systems under Linux with glibc 2.3 or higher:
Redhat Enterprise Linux 3
Redhat Enterprise Linux 4
Redhet Enterprise Linux 5
SuSe 9, SuSe 10, SuSe SLES 11
2. The interconnect to use is Gigabit Ethernet or Infiniband
3. It is highly recommended to have the same hardware and OS level on all nodes.
4. The MPI library: HPMPI 2.2.7 or HP MPI 2.2.5.1 must be installed on all the cluster nodes.
Currently the Radioss to MADYMO 7.1 MPP coupling does not work with HPMPI 2.3 or higher.
2. Follow the steps documented in Chapter 2 to complete the installation and licensing activation.
I.2.3.b MADYMO
1. Install MADYMO according to the MADYMO Installation Instructions.
Use the linux24-em64t platform.
2. Install the MADYMO license.
I.2.4
The configuration of the machine must conform to the specifications in Chapter 4.4 Install RADIOSS
HMPP on Linux cluster using Platform MPI
MADYMO environment needs to be reachable from all the computation nodes, with the same account
to run RADIOSS.
In sh/ksh/bash shell:
export MADETCPATH=$MADHOME/share/etc:.
export MADINCPATH=$MADHOME/share/etc:.
export MADBINPATH=$MADHOME/linux24_em64t/bin
Install HyperWorks 11 package for linux64.The radflex_11_linuxia64 tool needs the liblmxaltair.so library from HyperWorks 11 installation.
Set the LD_LIBRARY_PATH environment to $ALTAIR_HOME/hw/lib/linux64 :
[radioss@host1] setenv LD_LIBRARY_PATH $ALTAIR_HOME/hw/lib/linux64.
#! /bin/sh
np="-np 1"
job_name="$1"
117
Appendix J: HyperWorks
Installation Known Limitiations
Known Issues and Limitations
Uninstall Issues:
1. Files may be left behind in the installation directory after uninstaller completes (GUI Remove
Original Install Files Only, console and silent modes). Manual removal of these files is required.
2. A false warning message may appear at the end of the uninstaller stating that a log file/folder was
not able to be removed during the uninstall process. The file/folder will be removed a few
moments after pressing the Done button within the message window.
Miscellaneous:
1. On Linux, the Help Configuration prompt will add another set of double quotes if the back
command is used under the console mode installer. If new input is used, then the issue does not
occur.
2. On Linux, when installing via console mode an extra set of quotes will be added to the help
browser variable HW_MSG_BROWSER listed in the hwhelp.cfg file (e.g.
HW_MSG_BROWSER /usr/bin/firefox). Remove the extra set of double quotes to
make the help work correctly.
3. A Java plug-in is required for Help search on Linux.
4. ActiveX is required for Help search on Windows.
5. Help search on local hard disk installs requires access to local files to be allowed in the web
browser. There is not an issue if accessing the Altair web help.
118