Hw11 Install Guide

Altair HyperWorks 11.0 Application Installation Guide

Revision 2

2 HyperWorks 11.0 Application Installation Guide Revision 2

Proprietary Information of Altair Engineering

Altair Engineering Contact Information

Web site www.altair.com

FTP site Address: ftp.altair.com or ftp2.altair.com or http://ftp.altair.com/ftp Login: ftp Password:

Location Telephone e-mail North America 248.614.2425 [email protected]

China 86.400..619.6186 [email protected]

France 33.1.4133.0992 [email protected]

Germany 49.7031.6208.22 [email protected]

India 91.80.6629.4500 1800.425.0234 (toll free)

[email protected]

Italy 39.800.905.595 [email protected]

Japan 81.3.5396.2881 [email protected]

Korea 82.70.4050.9200 [email protected]

Scandinavia 46.46.286.2052 [email protected]

United Kingdom 01926.468.600 [email protected]

Brazil 55.11.3884.0414 [email protected]

Australia 61.3.9016.9042 [email protected]

New Zealand 64.9.413.7981 [email protected]

The following countries have distributors for Altair Engineering:

Asia Pacific: Indonesia, Malaysia, Singapore, Taiwan, Thailand

Europe: Czech Republic, Hungary, Poland, Romania, Spain,Turkey.

2011 Altair Engineering, Inc. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated to another language without the written permission of Altair Engineering, Inc. To obtain this permission, write to the attention Altair Engineering legal department at: 1820 E. Big Beaver, Troy, Michigan, USA, or call +1-248-614-2400.

Altair

HyperWorks 11.0 Installation Guide for Window, Unix and Linux

Trademark and Registered Trademark Acknowledgments 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 1993-2011; 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



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



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:

Release Notes for HyperWorks Installation Chapter 1: Preparing to Install HyperWorks Chapter 2: Installing HyperWorks Chapter 3: Installing AcuSolve Chapter 4: Installing RADIOSS HMPP Chapter 5: Installing OptiStruct SMPD 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 open-systems 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.

Conventions Used in this Guide

This guide uses the following conventions:

Bold Italic

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



Example: See Minimum Requirements for more details.

Warnings and notes pertaining to the installation appear in boxes as in the following.

) Important notes appear in these boxes. These messages are informational.

! 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.

HyperWorks 11.0 Software and Hardware Release Notes




Altair HyperWorks, A 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 open-system philosophy, Altair HyperWorks continues to lead the industry with the broadest interoperability to commercial CAD and CAE solutions.

HyperWorks Software and Hardware Release Notes

Various changes have been made to the HyperWorks 11.0 software package including the HyperWorks products, hardware support, installation, invoking process, and online help.

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 innovate business models and promptly respond to issues. HyperWorks Units work much like GridWorks Units with one main difference: one HyperWorks Unit is equivalent to 100 GridWorks Units. A new license and a license server are required to run HyperWorks 11.0.

Changes to the Altair Licensing System are detailed in the Altair Licensing Release Notes.

Software Addition and Changes

New Applications

Engineering Solutions HyperWorks Engineering Solutions is a customized and highly automated modeling and visualization environment for NVH, CFD, Crash, Durability, Suspension, and Drop Test applications.

solidThinking solidThinking combines unique and powerful modeling and design communication tools surrounded by an interface that is at once familiar, intuitive and informative. This application is for Windows only.

Inspired solidThinking Inspired is a shape generation laboratory that uses mathematical algorithms to produce organic shapes in response to environmental conditions such as forces and pressures. The resulting shapes are poly meshes you can export to modeling systems such as solidThinking as a source of inspiration for your designs. This application is for Windows only.

AcuSolve AcuSolve is a leading general purpose finite element based




Computational Fluid Dynamics (CFD) flow solver with superior robustness, speed, and accuracy.

AcuConsole AcuConsole is a powerful and dedicated pre-processor for AcuSolve, capable of meshing complex geometries in an efficient manner.

Hardware Platforms

Supported Hardware Platform Additions

Operating system Support has been added for: Windows 7 RHEL 5.4

SLED 11.0 (X86-64) Mac OS X 10.6 ( available on FTP site only)

Discontinued Hardware Platform Support

Operating System Support for the following platforms has been dropped across all HyperWorks applications: RHEL4.x/5.2 Novell SUSE 9.2 SLED 10 SP1 HPUX 11.11

AcuSolve/AcuConsole Integration into HyperWorks

The integration of AcuSolve and AcuConsole into the HyperWorks installation is only supported for Windows 32/64 and Linux 32/64.

Installation

New Features

New Installation Third Party Software

HyperWorks installer has been updated to InstallAnywhere 2010 for all supported platforms.

Provides the same installer experience across all Linux/Unix and Windows platforms.

Easy use of InstallAnywhere response files for silent and large roll-out installations.




Installation Allows for GUI, silent, and console (non-GUI) installation modes.

Allows multiple installations and portability with the removal of Windows GUID registries.

Allows you to install both local and server/client installation on the same machine.

Allows for administrator and non-administrator installations. Added additional regional language support within the installer. Allows the applications to be installed in a directory with space.

The default location is in the C:\ Program Files directory.

Provides a new set of HyperWorks product icons.

Packaging Help package is packaged separately from the HyperWorks application package.

Enhancements

Server/Client installation

HyperWorks Server/Client installer is updated with more available options for placement of files and shortcuts.

Enable the silent installation capability to client NETSETUP

Installation /Uninstallation

Installer will warn end users if any HyperWorks applications are running during the installation or uninstallation process. It allows you to close the application and continue the installation or uninstallation.

Installation Information Installation log is available for user to review the installation information and verify if the installation is correct.

Invoking Created modularized invoke scripts which are POSIX compliant ( bash ).

Added Composite window manager handling under Linux operating systems.

Known Limitations

Un-installation Files may be left in the installation directory after uninstallation (GUI and Console mode) is completed. Manual removal of these files is required.

A false warning message at the end of the uninstaller stating that a log file was not able to be removed during the uninstall process appears. The file/folder will be removed a few moments after pressing the Done button.




Installation On Linux, the Help Configuration prompt will add another set of double quotes if the back command is used under console mode. If new input is used then this issue does not occur.

On Linux, when installing using the console mode, an extra set of quotes will be added to the help environment variable listed in the hwhelp.cfg file (for example: HW_MSG_BROWSER ""/usr/bin/firefox""). Remove the extra set of quotes to make the help work correctly.

Server/Client Installation

For Windows network server/client based installations, the integration of the AcuSolve CFD solutions into the HyperWorks framework is not supported.

For NETSETUP client installs, a UNC path must be used to get to the Server installation path through Windows Explorer or Windows Network.

Help Search Java plugin is required for help search on Linux. ActiveX is required for help search on Windows.

AcuSolve/AcuConsole

Separate Installation After the installation of HyperWorks, AcuSolve and AcuConsole can be installed separately using an independent installation package. Shortcuts (on Windows) and invoke scripts (on Linux) will then be generated automatically and AcuSolve/AcuConsole can be accessed through the HW installation. If AcuSolve has been installed first and HyperWorks

second, please execute acusetHW to enable the short cuts and invoke scripts in the HyperWorks installation directory. AcusetHW is included in the AcuSolve/AcuConsole installation.

The option to start AcuSolve or AcuConsole from the HW installation is not supported for Windows network server-client installations.

Perl needs to be installed on the system in order to run AcuSolve.

Help

New Features

Content and Book Structure

The HyperWorks product Help book has been reorganized to 10 categories based on the application functionality.

Online Help If Help is not installed locally along with the HyperWorks




applications, users can invoke the online help via Altair Web site from within the application.

Title Bar Add an expandable text icon allows you to show or hide all expandable text on the current page.

Version The version of the HyperWorks online help is added to the bottom of the Table of Content section.

Enhancements

Search Capability More robust search capability.

Known Limitation

Search If Help is installed locally with the HyperWorks application and is viewed via Firefox browser, the content books cannot be expanded after performing a topic search. When this happens, simply reload the page to resolve the problem.

Utilities/Tools

New Features

Lmxutil Replaced licensing utility tool lmutil with the almutil and lmx-config.

Enhancements

Help Menu The Update dialog is renamed to Updates and System Information. It has been enhanced to include HyperWorks updates information, the version of major HyperWorks applications, and detailed machine hardware and graphics information.

The Contact us option has been added to quickly access the Altair Support contact page.

Addition of Online Learning Tab allows users to access the HyperWorks online learning sections on the Altair web site.

Resolved Issues

HW Inventory HW Inventory now works on the Window Vista64 operating system.

Chapter 1: Preparing to Install HyperWorks




This chapter summarizes the items and procedures needed to install and successfully run HyperWorks applications on platforms supported by HyperWorks 11.0. It includes a list of required items, access to the HyperWorks package, hardware and operating system considerations, and system requirements.

The general procedures are:

Install and activate an Altair 11.0 License Manager if one does not already exist. Install HyperWorks on the designated machine(s). Set up an environment variable that points the HyperWorks application to an activated and

running Altair license server.

Set up HyperWorks online help if needed. 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.

What you need:

Access to the Altair Web site (www.altairhyperworks.com) HyperWorks software DVDs media, Altair License Manager DVD, delivered from Altair, or

HyperWorks image packages downloaded from the Altair web site

A DVD compatible drive if installing from DVD media Access to an activated and running HyperWorks 11.0 license server A compatible machine that contains the minimum hardware/software requirements to run

HyperWorks applications (Chapter 1 section 2)

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.

_______________________________________________________________________________

1.1 Installation Media

The HyperWorks 11.0 software package you received from Altair includes the HyperWorks 11.0 application DVDs, the Altair License Manager package DVD, and a documentation CD. The documentation CD contains the Altair HyperWorks 11.0 Application Installation Guide, the Altair




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. ________________________________________________________________________________

1.2 Hardware and Operating System

The following table lists the platforms, operating systems, and processors supported by Altair HyperWorks 11.0.

Platforms Altair HyperWorks 11.0

OS Version Architecture GUI Products Solvers1

Windows2

XP/Vista/7 x86 YES YES3

x86_64 YES YES

Server 2003/2008 x86 NO YES3

x86_64 NO YES

Linux4

RHEL 5.4

SLED 11

x86 YES YES3

x86_64 YES YES

IA-64 NO YES

SGI ProPack 4

(SLES 9)5 IA-64 NO YES

Unix IBM AIX 5.3 Power 4/5 NO6 YES7

Solaris 10 x86_64 NO YES8

**Mac OSX9

10.6 x86_64 YES YES3

**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.




1 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 3rd party MPIs and are Intel Cluster Ready compatible and certified.

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

2

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.

3

Only SMP parallelization is supported for HyperWorks 11.0 solvers on Windows (x86), Linux (x86) and Mac OS X (x86_64) architectures.

4 HyperWorks 11.0 Linux requirements (minimum versions): Kernel version 2.6.9-42

a) RedHat Enterprise Linux 5 Update 2 (2.6.18-53.el5) b) SUSE Linux Enterprise Desktop 11 (2.6.27.19-5)

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 LIBF2C (libf2c-3.4.3-22.1 and compat-libf2c-3.4.3-22.1) Fortran G77/G95 runtimes MotionSolve (HWSolvers) requirement: libgfortran-4.1.0-18.EL4 (32-bit/64-bit) or equivalent LIBEXPAT XML library 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): GNU BASH, version 3.00.15(1)-release POSIX shared memory (for 3D applications)/ELF TLS (thread local storage) libraries OpenGL packages/libraires (libGL 6.8.2-1, libGLU 6.8.2-1, etc.) X-org 6.8.2 packages (or XFree86 equivalent)and OpenMotif libX11, libXm.so.3, libXp.so.6, etc Vendor (NVIDIA or AMD/ATI) distributed OpenGL hardware accelerated driver packages Kernel source/header files (used to compile 3D NVIDIA/AMD ATI OpenGL vendor driver modules) Tools: rpm/fontconfig/freetype/zlib/gzip/tar/gtar Gnome 2.6/KDE 3.3 window managers (or higher) Fonts (scalable): Helvetica, Times, New Century schoolbook, b&h luxi sans/serif, typeface, bitstream vera

sans/serif, iso8859-1 (75dpi/100dpi) and Utopia SDL 1.2.7-8 libraries to run Process Manager

NOTE: HyperWorks Enterprise Explore Dialog and Data Manager are only supported on Windows platforms. HyperCrash does not support Linux 32-bit.

HyperWorks 11.0 may install and run on other non-supported Linux distributions but Altair does not test, certify, verify or warrant the reliability of the products on these platforms.

a) Altair products are tested on the KDE and Gnome window manager. b) Xen kernels are currently not supported kernels for Altair HyperWorks 11.0 applications.

5 SGI ProPack 4 is available only for SGI Altix machines.

6 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.

7 MotionSolve is not supported on IBM AIX platforms.




8 HyperXtrude Solver is not supported on Solaris platforms.

9 Minimum versions for OS X (kernel) and X11 support: 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:

HyperCrash, HyperStudy, MotionView, HyperMath/ScriptView, Process Manager and Data Manager. Unsupported third party CAD formats 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 RedHat Enterprise Linux

SLED SUSE Linux Enterprise Desktop

SLES SUSE Linux Enterprise Server

MPI Message Passing Interface

SMP Symmetric Multi-processing. Processors connect to a single shared main memory.

SPMD Single Program Multiple Data. Each processor has its own main memory.

HMPP Hybrid-Massive Parallel Processing. Hybrid

parallelism, in which a SPMD program consists of nodes with several SMP threads.

_____________________________________________________________________________________________________

1.3 System Requirements

Minimum system requirements for HyperWorks applications

The following table lists the minimum system requirements that are necessary to run any HyperWorks 11.0 32-bit/64-bit application on the supported operating systems and hardware platforms.

Unix/Linux Windows

Operating Systems IBM AIX 5.3 GUI batch mode HyperWorks Solvers

Linux RHEL 5.2/SLED 11 Sun Solaris 10 (x86_64)

Solvers only

For 32-bit and 64-bit systems: XP/Vista/7 Server 2003/2008 (Solvers

only)

Memory 512 MB (higher recommended) 512 MB (higher recommended)

Complete Install Disk Space IBM AIX ~ 4.2 GB Windows 32-bit ~ 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.**

Linux 32-bit Linux 64-bit Solaris 10 (solvers)

~ 5.8 GB ~ 6.4 GB ~ 621 MB

Windows 64-bit ~ 6.2 GB

Graphics Hardware OpenGL 3D graphics accelerator compatible with OpenGL 1.1 or higher

True color (24-bit) support Install/update to most recent OpenGL

patches/drivers 1280x1024 screen resolution

Windows compatible OpenGL graphics adapter compatible with OpenGL 1.1 or higher

256 MB or higher dedicated video memory

High (16-bit) or True (24-bit) color support

Install/update to most recent OpenGL patches/drivers

1280x1024 screen resolution *Browsers/Online help (plug-in)

Firefox 1.5 (or higher) Java Plug-in required

Firefox 1.5 (or higher) Internet Explorer 7.0 (or higher) **Does not support Protected Mode under Internet Explorer

) 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

Additional Specifications for Specific Applications

Additional requirements and limitations:

All Applications

HyperWorks 32-bit applications may not work properly within a 64-bit Linux operating system. It is recommended that you install the 64-bit applications if you wish to run on a Linux 64-bit machine.

Data Manager/Assembler/Process Manager

Altair Data Manager, Assembler, and Process Manager have a dependency on the 32 bit Simple DirectMedia Layer (SDL) Library package when launching on Linux platforms. The path to these libraries should be included in the Linux clients LD_LIBRARY_PATH.

The latest list of PC graphics cards that are compatible with HyperWorks is available on the Altair web site at: http://www.altairhyperworks.com

USB Hardware Keys (Dongles)

Altair supports a subset of the available Hostid values from X-Formation as well as hardware dongles (USB keys) on some platforms. In order to use a dongle you must have a free/open USB port on the machine that will be your license server.




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 Linux x86 (IA64 and X64 not available)

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 XP and Windows XP64 Follow these instructions to configure your non-US keyboard on Windows:

1. From the Start menu, select Control Panel. 2. Select Regional and Language Options. 3. Select Languages tab. 4. Click Details and select the predefined location from the drop-down list. 5. Click OK. 6. Click OK to close the Regional and Language Options dialog.

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:




1. From the Start menu, select Control Panel. 2. Select Region and Language. 3. Select Keyboard and Languages 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.

Chapter 2: Installing HyperWorks


) You may need administrator permissions to install this software. Check with your systems administrator for your installation requirements.

If you have a non-US keyboard, you will need to make modifications after initiating the installation. See Section 1.3 System Requirements.

You need to download three files from the Altair web site for a complete HyperWorks 11.0 installation.

Two procedures are necessary to enable HyperWorks. First, using the installation configuration you selected in Chapter 1 as a guide, install the HyperWorks software on your machine(s). Second, you must be able to point to an activated license server that allows HyperWorks application to draw license units. Details of installing and activating the Altair License Manager are described in the Altair License Management System 11.0 Installation and Operation Guide

There are three files required for a complete HyperWorks installation on each platform: standard HyperWorks applications, Help files, and Altair AcuSolve CFD Solutions. Altair AcuSolve CFD Solutions provides you the capability to run CFD analysis. To perform a full HyperWorks installation, make sure you have downloaded all three files from the Altair web site before you start the installation.

HyperWorks 11.0 can be installed via a Graphical User Interface (GUI) mode, silent mode, or console mode. The following sections describe how to install the software via these methods.

The HyperWorks 11.0 Help is a browser-based HTML system. It can be installed with the applications or installed alone behaving as an online help server. Find the location of the Internet browser if online help is to be installed along with the HyperWorks application.

2.1 Installing HyperWorks: Local Install 2.1.a Installation files

The HyperWorks 11.0 software package can be downloaded from the Altair web site or from DVD. Three files are needed for each platform: HyperWorks standard package, Help file package, and the AcuSolve CFD Solution package. Below is the list of the file names needed for each platform:

HyperWorks Installer Filename 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 IBM AIX 5.3 (batch applications and solvers only)

0.9

Containing all HyperWorks applications

Help Files Filename 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 IBM AIX 5.3 1.6

Containing Help, tutorial model files, and the demo/ files

AcuSolve Filename Platform Size (GB)

AcuSolve-V1.8a-WIN32.msi Windows (32-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.1b Installing via Graphical User Interface (GUI) mode

This section describes how to install HyperWorks application, with exception of AcuSolve applications, via a GUI mode. Follow the following steps to extract and install the software:

1. Login to the machine on which the software is to be installed.




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.

) HyperView Player, solidThinking/Inspired and AcuSolve/CFD integration is not available in the server type installs

See Section 2.2 for how to set up the client machine.

8. The Choose Install Folder panel is displayed. Choose the install path and click Next. 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. Installing to a root drive is not permitted, example C:\

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 64-bit).




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.

) On a Windows platform, the default browser setting (HW_MSG_BROWSER) is the same as the Windows default browser, and on Linux/Unix a browser prompt will request for the path and file of a web browser to use.

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.

Optional AcuSolve Integration Installation (See details in Chapter 3)




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. Uncompress the *.tgz file. It will uncompress to a folder, example AcuSolve-V1.8a_LINUX64

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.

Registering the HyperView Player plugin The HyperView Player plugin for Microsoft Office documents and Internet Explorer is installed and registered by default with the HyperView Player installation. In case of multiple HyperView/HyperView Player installations, the user may need to manually register the latest HyperView Player plugin following the steps below.

1. Navigate to Start > All Programs > Altair HyperWorks 11.0 > Tools and click Register HVPControl.

2. Invoke the currently installed HyperView Player found at /hw/bin/win[32/64]/hvp.exe to automatically register it.

2.1.c Installing via console mode

Console mode installations mimic the default Graphical User Interface steps provided by the HyperWorks installer but use only the standard input and output. The advantage to console mode installation is that Linux/Unix users no longer need X-windows (X11) to run the installer.

Console mode allows for text to be output to the console terminal line-by-line. It does not allow for any formatting, clearing of the screen, or positioning of the cursor. To trigger a console mode installer from the command line, append the following command parameter to the installer: -i console For an example console mode install call, hw11.0_linux64.bin i console The Linux console mode is only supported on the HyperWorks Linux/Unix installers. Just follow the on screen instructions to complete the installation.




See Appendix G for details of installing HyperWorks via console mode on Linux/Unix.

2.1.d Install via silent mode

Silent mode enables the installer to run without any user interaction. A near-silent mode is possible on Windows and Mac OS X. InstallAnywhere and HyperWorks end-user-defined variables may be set through command line parameters or a properties response file.

Response files are created and used in silent mode since there is no end user interaction.

The installer runs either on the defaults provided by the installer package or by providing a response file from which the installer retrieves the values for various InstallAnywhere and HyperWorks variables used to control the install.

The installer automatically checks the residing directory for a file called installer.properties. You can generate a response file from the installer by running through the installer with the following command line syntax: -r [FullPath]\installer.properties. The file will get created once the installer is complete. To trigger a silent installer from the command line, type the following:

[installername] i silent You may also call a properties response file from the command line by typing:

[installername] i silent f [fullpath]\installer.properties An example of running a silent install using a properties response file located in C:\ResponseFiles called hw11_silent.properties on Windows 64-bit: hw11_win64.exe i silent f c:\ResponseFiles\hw11_silent.properties 2.1.e Response files

Response files are used with the silent mode installers to give the default values of an install. The files contain text in a simple key=value format. An example of a properties response file is shown below:

#Choose Installation Type #------------------------ LOCAL_INSTALLATION=1 SERVER_INSTALLATION=0 #Choose Install Folder #--------------------- INSTALLER_UI=silent USER_INSTALL_DIR=C:\\Program Files\\Altair\\11.0 #Change Shortcut Folder (Local) #------------------------------ SET_START_MENU_FOLDER=Altair HyperWorks 11.0 INSTALL_DESKTOP_SHORTCUTS=1




DONOT_INSTALL_DESKTOP_SHORTCUTS=0 #Choose Install Set #------------------ CHOSEN_FEATURE_LIST=HWFhelp,SLVR,MFS,HST,HWD,HC,HW,HWX,DesktopApps,sT,ES,helpHW,tutsHW,demosHW CHOSEN_INSTALL_FEATURE_LIST=HWFhelp,SLVR,MFS,HST,HWD,HC,HW,HWX,DesktopApps,sT,ES,helpHW,tutsHW,demosHW CHOSEN_INSTALL_SET=Complete

The values in the response files are all referenced from user input taken from a HyperWorks install and used as default values toward future installs.

For example, the INSTALLER_UI value in the above example is set to silent. This negates the need to use -I silent on the command line as a silent installer switch.

) The installer will use double backslashes \\ on Windows platforms for the directory names and forward slash / on Linux/Unix platforms.

2.2 Installing HyperWorks: Server/Client Installation

On Windows machines, the HyperWorks installation type can be either server/client installation, or local installation. This section described how to set up the client machine if a server type installation is chosen.

) HyperView Player, SolidThinking/Inspired and AcuSolve/CFD integration is not available in the server type installs.

) Requirements for a NETSETUP client install include:

a. Existence of an Altair HyperWorks network server install b. The UNC paths of the location of the HyperWorks network server installs (or use

Networks on Windows 7/Vista or My Network Places on Windows XP to get to the NETSETUP client installer directory). The installer does not allow for the use of drive letter or mapped paths.

2.2.a HyperWork client NETSETUP installation in GUI mode

This section describes the client NETSETUP of a HyperWorks network server install on Windows only. The NETSETUP supports the GUI and silent mode installations modes. The example below is shown for a GUI NETSETUP client Windows 7 64-bit install.




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. Go to the NETSETUP folder 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.

2.2.b HyperWorks client NETSETUP installation in silent mode (Optional)

Follow these steps to create a properties file for the client NETSETUP installer. This step is only required to be done once in order to establish the defaults for the installer.

1. Go to the HyperWorks network server install NETSETUP directory location and run the NETSETUPproperties.bat file. a. Go to Networks b. Click on the machine and install location of the HyperWorks server install c. Go to the NETSETUP folder 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.




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.

2.3 Connecting to the Altair License Management System

About the Altair License Management System

The Altair License Management System (ALM) provides a common units-based licensing model for all Altair software related to CAE, on-demand computing, and business intelligence. This new system has been designed to enable HyperWorks Partner Products (selected third party products) to be licensed via HyperWorks Units as well.

The Altair License Management System is comprised of two components: the License Server and the Usage Reporting System (URT). The license system is based on X-Formations LM-X license server. The URT is a java application that reports anonymous transactional logs to Altair. As part of the license agreement that enables partner software to be used, product usage must be reported to Altair.

The ALM is based on X-Formations LM-X license management system version 3.32. For additional information and details, please download the LM-X End User Guide from the Altair web site at http://www.altairhyperworks.com, and choose Support > Software Downloads.

Connecting to Altair License Manager (ALS)

In order for applications to use the ALS, the environment variable, ALTAIR_LICENSE_PATH, must point to the appropriate location. Multiple license paths are allowed and should be separated by a semicolon (;) on Windows and a colon (:) on Unix/Linux. The proper format for a network license location is port@hostname. If you are using a local license file, simply set the value to the full pathname of the file.

A few examples of license paths

On Windows: [email protected] ALTAIR_LICENSE_PATH=6200@srv1;6200@srv2;6200@srv3 ALTAIR_LICENSE_PATH=c:\Program Files\Altair\Licensing11.0\altair_lic.dat

On Linux/Unix:




[email protected] 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 /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.

2.4 Starting HyperWorks Applications

This section covers how to:

Invoke a HyperWorks application Start a HyperWorks application through batch mode Establish shortcuts for starting applications Obtain a list of arguments for an application

2.4.a Invoke a HyperWorks application on Linux/Unix

All HyperWorks applications start by running the appropriate script from the /altair/scripts directory. The scripts directory contains the launch procedure for each HyperWorks application and tools such as hvtrans and printer manager. In addition, it contains the /invoke sub-directory where various sub-procedures used by the launch procedures are stored.

The general start command to enter at the UNIX prompt is:

/altair/scripts/ where is the script name associated with the particular application and the optional [file name] applies to the applications that require an input file when they start. For example, to start HyperMesh you would enter the following at the prompt:

/altair/scripts/hm The following scripts are used to launch HyperWorks applications:

Command Options Descriptions

datamanager Launch Altair Data Manager

es_cfd Launch Engineering Solutions/CFD




es_crash Launch Engineering Solutions/Crash

es_droptest Launch Engineering Solutions/Drop Test

es_nvh Launch Engineering Solutions/NVH

hc Launch HyperCrash

hfsolver Launch Manufacturing Solutions/RADIOSS 1 Step

hg Launch HyperGraph

hm Launch HyperMesh

hmbatch -c-tcl Launch HyperMesh using batch mode

hmdesktop Launch HyperMesh client from HyperWorks Desktop

hst Launch HyperStudy

hst -studyfile= Automatically read the file after launching HyperStudy

hstbatch Launch HyperStudy using batch mode

hv Launch HyperView

hvp Launch HyperView Player

hx Launch HyperXtrude

hw_batchmesh Launch the Batch Mesher user interface where you can interactively set up the required entries

blanknest Launch BlankNesting

hmath Launch HyperMath

hmathbatch Launch HyperMath in batch mode

mdl_batch -c Launch MotionSolve using batch mode

motionsolve Launch MotionSolve

mview Launch MotionView

mfs_forging Launch Manufacturing Solution/Forging application

mfs_hyperweld Launch Manufacturing Solution/HyperWeld application

mfs_hf Launch Manufacturing Solution/HyperForm application

mfs_hx Launch Manufacturing Solution/HyperXtrude application




mfs_hypermold Launch Manufacturing Solution/HyperMold application

optistruct Launch OptiStruct

ossmooth Launch OSSmooth

pmstudio Launch Process Studio

radioss Launch RADIOSS.

resmap Launch HyperWorks Results Mapper

sview Launch ScriptView

templex Template.tpl Launch Templex

2.4.b Obtain a list of arguments for an application on Linux/Unix

To obtain a list of arguments and their descriptions, add -help to the start command. For example, to obtain a list of arguments for HyperMesh, enter the following at the command prompt:

/altair/scripts/hm help The application returns a list of the available arguments and what they do. 2.4.c Invoke a HyperWorks application on Windows

The installation process creates a HyperWorks group available from the Start menu in Programs. The folder containing the applications receives a default name by the Altair HyperWorks installation wizard. Most applications can be started using the following instructions. The example below uses the default settings.

1. Click Start and select Programs. 2. From the Programs menu click Altair HyperWorks 11.0. 3. Select from the pick list the name of the program you want to run.

2.4.d Change the default working directory on Windows

The default working directory specified by a HyperWorks application is: C:\Documents and Settings\\My Documents (for Vista, C:\Users\UserID\Documents\).

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.




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 \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.

2.5 Setting Up HyperWorks Help

The HyperWorks help system is a browser-based HTML help system. It can be installed with applications or installed alone on a server. This section describes how to set up and access HyperWorks help system.

2.5.a Set up HyperWorks Help

The HyperWorks help system can be installed with applications or installed alone on a server. In order for the help to work properly from applications, you must set up a valid Internet browser and a valid path to the HyperWorks help installation if help is not installed with the application. Help can be installed via different ways:

On a local machine along with the HyperWorks software Pre-installed on a shared network location Use Altair Website help.

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 /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 /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.




) 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).

2.5.b Start help from the application Help menu

The steps to start help from application Help menu are similar for most applications.

1. Set up the browser and help environment before starting the application as described above. 2. Start the application. 3. Click the Help drop-down list and choose the help for the selected application. Once the online help has been launched, you can use the Index, Contents, or Search to locate the help for a specific topic. The context sensitive help works as well. 2.5.c Start help from the altair/scripts directory

Each HyperWorks Help book can be invoked via command prompt by pointing to the altair/scripts/help script. Enter a command and option at the command line on Unix and Linux to launch the help for a specific application.

Command Option Usage

altair/scripts/help help Display the command and options to launch each application help book

hw Launch HyperWorks Introduction book

hwd Launch HyperWorks Desktop book

hwsolvers Launch RADIOSS, MotionSolve, and OptiStruct book

hwe Launch HyperWorks Enterprise book

hwtools Launch HyperWorks Tools book

hwtut Launch HyperWorks Tutorials book

engsol Launch Engineering Solutions book

mfs Launch Manufacturing Solutions book

mathsol Launch HyperMath Solutions book

mbdsol Launch Motion Solutions book

hst Launch HyperStudy book




hc Launch HyperCrash book

hvp Launch HyperView Player book

sv Launch ScriptView book

2.5.d Help installed on server type (Windows only)

If you have chosen Server setup type described in Section 2.1, each client is installed through NETSETUP as described in Section 2.2. HyperWorks applications will be available from the Start menu. If both the HyperWorks application and help are installed on the software server, help can be accessed on this client as long as a valid browser is installed on the client machine.

Chapter 3: Installing AcuSolve




Introduction

This chapter introduces the installation of new HyperWorks products, AcuSolve and AcuConsole, and the procedure to integrate these products into HyperWorks environment.

AcuSolve is a leading general-purpose finite element based Computational Fluid Dynamics (CFD) flow solver with superior robustness, speed, and accuracy. AcuSolve can be used by designers and research engineers with all levels of expertise, either as a standalone product or seamlessly integrated into a powerful design and analysis application. Quality solutions can be obtained quickly without iterating on solution procedures or worrying about mesh quality or topology. The fluid structure interaction (FSI) capabilities available in AcuSolve enable the user to perform multi-physics analysis of complex scenarios in an efficient manner.

The interfaces in HyperMesh and HyperView ensure a smooth integration of AcuSolve into the HyperWorks framework.

AcuConsole is a powerful, yet easy to use GUI-Based Computational Fluid Dynamics (CFD) pre-processor for AcuSolve. It can work with very complex geometries, build simulations from CAD or Mesh and import 3D CAD models from Pro/ENGINEER, Parasolid, ACIS, and Discrete. AcuConsole can also import an existing mesh in various formats. Through an intuitive menu structure, AcuConsole helps the user fully set up a problem, generate an input file, and launch its solver. CAE automation is available through the Python scripting language, allowing users to customize menus and functions for specific applications.

General steps for integrating AcuSolve/AcuConsole with HyperWorks.

Installation of HyperWorks

a. HyperWorks needs to be installed and placeholders for the AcuSolve CFD Solutions are part of the installation.

Installation of AcuSolve

1. The AcuSolve CFD Solutions will need to be installed.

2. A utility called acuSetHW will be executed automatically after the AcuSolve installation to populate the placeholders in a HyperWorks installation, if HyperWorks is installed.

3. If HyperWorks is not installed, then acuSetHW can be run at a later time to complete the link between both products. See Step 3 for details.

AcuSetHW

1. This utility can be launched manually to update the HyperWorks placeholders to link together AcuSolve CFD Solutions with HyperWorks.

2. It is located in the /bin directory of the AcuSolve V 1.8a or later versions. 3. Executing the acuSetHW utility may require administrative permissions.




3.1 Install AcuSolve/AcuConsole

3.1.a Acu-product install files

AcuSolve Filename Platform Image Size (GB)



AcuSolve-V1.8a-LINUX.gz Linux (32-bit) 0.5

AcuSolve-V1.8a-LINUX64.gz Linux (64-bit) 0.7

These files are available on Altair web site only.

Disk space required for installing AcuSolve on the following platforms:

Platform 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

3.1.b System requirements

On Linux, AcuSolve requires a minimum Linux kernel version 2.6.9-67 and glibc version 2.3.4. Run rpm q glibc to check the glibc version. To run AcuSolve, you need Perl 5.0 or higher. To check the version of Perl on your system, issue the command:

Perl v You can get Perl from ActiveState from following link: http://www.activestate.com/activeperl/downloads




3.1.c Install AcuSolve

On Linux

To install the distribution on a Linux platform, perform the following steps:

1. Download the package and save the file to a temporary directory, for example, /usr/tmp. Go to the directory: cd /usr/tmp

2. Uncompress and untar the package: For example:

Tar zxvf AcuSolve-V.1.8a-LINUX64.tgz Or gzcat AcuSolve-V.1.8a-LINUX64.tgz | tar xvf -

3. Change the directory to the distribution: Cd AcuSolve-V1.8a-LINUX64

4. Install the software by invoking the INSTALL script and answering all the questions: ./INSTALL

5. After installation has completed, you need to connect to a valid License Manager. See Section 3.2 for connecting to a valid license.

6. Once successfully installed, use the following command to delete the temporary files if desired : cd /usr/tmp rm rf AcuSolve-V1.8a-LINUX64 AcuSolve-V1.8a-LINUX64.tgz

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.

3.2 Connecting to Altair Licensing Server




Connecting to Altair License Manager (ALS)

In order for applications to use the ALS, the environment variable, ALTAIR_LICENSE_PATH, must point to the appropriate location. Multiple license paths are allowed and should be separated by a semicolon (;) on Windows and a colon (:) on Unix/Linux. The proper format for a network license location is port@hostname. If you are using a local license file, simply set the value to the full pathname of the file.

A few examples of license paths

On Windows:

[email protected]

ALTAIR_LICENSE_PATH=6200@srv1;6200@srv2;6200@srv3

ALTAIR_LICENSE_PATH=c:\Program Files\Altair\Licensing11.0\altair_lic.dat

On Linux/Unix

[email protected]

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.3 Integration of AcuSolve CFD Solutions into the HyperWorks Environment

During the installation of HyperWorks, a set of placeholders are created in the HyperWorks environment pointing to the AcuSolve CFD solutions. For Windows this is AcuSolve Cmd Prompt, AcuSolve Job Launcher and CFD AcuConsole) in the Start Menu.

For Linux, the links acuconsole, acujob, and acusim are placed into the ALTAIR_HOME/scripts directory.

After the HyperWorks installation, the placeholders are not yet pointing to the correct AcuSolve CFD Solutions tools. This means that a message prompt will be displayed when, for example, clicking on CFD (AcuConsole) Start Menu item:

These place holders in the HyperWorks installation can be updated and activated by executing the utility, acuSetHW,located in the AcuSolve installation directory.The steps are described in the following sections:

) acuSetHWcan only be used successfully if both HyperWorks and AcuSolve are already installed on the system. 3.3.a Executing acuSetHW on Windows

1. There are three placeholders, AcuSolve Cmd Prompt, AcuSolve Job Launcher and CFD (AcuConsole), in the Start Menu that need to be updated.




2. Run acuSetHW from the /bin/Win32(64)/V1.8a/ directory. The Install AcuSolve in HW display prompt will be displayed, as shown below:

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.

3.3.b Executing acuSetHW on Linux

1. There are three placeholder links, acuconsole, acujob and Acusim, in the $ALTAIR_HOME/scripts directory created during HyperWorks installation.




2. Run acuSetHW from the /bin/Linux32(64)/V1.8a/ directory. The Install AcuSolve in HW display prompt will be displayed, as shown below:

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

Chapter 4: Installing RADIOSS HMPP



Chapter 4: Installing RADIOSS HMPP

Introduction of RADIOSS HMPP

The performance criteria in computation is an essential point in the architectural conception of RADIOSS. In the case of analysis of systems with a high number of degrees of freedom, the use of a shared memory parallel machines or large distributed memory clusters are common.

To efficiently adapt and optimize the performance on every type of machines, RADIOSS combines the benefit of two models of parallel programming inside the same executable:

SMP: Shared Memory Parallelism SPMD: Single Program Multiple Data

This enhanced parallel version is called RADIOSS Hybrid MPP (HMPP).

RADIOSS HMPP increases scalability and performance by having two parallelization levels:

High level: SPMD parallelization based on domain decomposition and MPI Low level: SMP Multi-threaded processes under OpenMP

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