HyperWorks 10.0システム要件一覧7 RADIOSS/OptiStruct (Bulk Data Format input). The HP-MPI is required for OptiStruct SPMD on Linux operating systems. This includes x86, x86_64

アルテアエンジニアリング株式会社

〒170-6043 東京都豊島区東池袋 3-1-1 サンシャイン 60 43F Phone 03-5396-1341 Fax 03-5396-1851 www.altairjp.co.jp

ⒸCopyright 2009 Altair Engineering, Inc. All rights reserved. 1

HyperWorks 10.0 システム要件一覧

*以下の目次をクリックすると、該当するページにジャンプします。

HyperWorks Application Platform and Operating System Support ..................................................................................................... 2 System Requirements .................................................................................................................................... 5 Recommended Graphics Boards.................................................................................................................. 7 Linux Graphic Card Driver Issues ................................................................................................................ 9 Non-US keyboards ....................................................................................................................................... 13 RADIOSS Executable List 10.0 - 9.0.2 - 51l ................................................................................................ 14

License Manager

Altair Licensing 10.0 Supported Platforms ................................................................................................ 22


Platform and Operating System Support The following table lists the platforms, operating systems, and processors supported by Altair® HyperWorks® 10.0.

Note The HyperWorks 10.0 GUI application suite no longer supports IBM AIX and SUN Solaris architecture and operating system platforms.


1 HyperXtrude GUI is included on the supported platforms for the HyperWorks GUI Applications list.

2 Altair HyperMesh Batch, BatchMesher, HyperStudy Batch, Templex and the HyperGraph translator tool will also be available only in the batch command line execution mode under the IBM AIX 5.3 architecture.

3 HyperWorks 10.0 Linux applications use GLIBC version 2.3.4 (or higher) as a minimum requirement. In order to run Altair Data Manager and/or Process Manager the SDL direct media layer 32-bit compatibility library packages must be installed. Appropriate OpenGL hardware accelerated driver packages must be installed.

HyperWorks 10.0 may install and run on other non-supported Linux distributions but Altair does not test, verify or warrant the reliability of the products on these platforms. Altair products are tested on the Gnome window manager. Recommended Linux packages/libraries (includes both 64-bit/32-bit compatibility packages):

GLIBC (2.3.4 or higher) ksh/pdksh/ksh93 libgcc runtime (3.4.3 or higher) / libstdc++ and libg2c (Fortran) libraries POSIX shared memory (for 3D applications)/ELF TLS (thread local storage) libraries libGL/libGLU/libGLcore/libglx XFree86-libs/XFree86-Mesa-libGL(4.2 or higher)/Xorg-libs/libX11/libXext/libXau/libXdmcp kernel source/header files (used to compile 3D NVIDIA/AMD driver modules) rpm tool/fontconfig/freetype/zlib/gzip/tar/gtar Gnome 2.22.1/KDE 3.5.9 window managers (or higher) SDL libraries

Note: Altair packages custom Tcl/Tk libraries/packages. Linux distributions:


RHEL=RedHat Enterprise Linux, SLES=SuSe Linux Enterprise Server, SLED= SuSe Linux Enterprise

Desktop

4 Altair Data Manager and Process Manager are supported under Windows XP and Vista. ADM/PM is a native 32bit

application and can be launched on both 32bit and 64bit supported Windows environments. HyperMath and ScriptView

will be supported on Windows 32bit and 64bit environments.

5 Altair Solver products support AMD Opteron/Athlon64, Intel EM64T and Itanium2, IBM AIX Power 4/5. RADIOSS will

also support PA 8000/9000 processors.

6 HyperXtrude solver only supported on the selected platforms.

7 RADIOSS/OptiStruct (Bulk Data Format input). The HP-MPI is required for OptiStruct SPMD on Linux operating

systems. This includes x86, x86_64 and ia-64 Linux architectures. All associated HP-MPI interconnects supported.

8 RADIOSS (Block Format input). The GLIBC version 2.3.4 is a minimum requirement to run RADIOSS SPMD on their

respective Linux distributions. RADIOSS supports Gigabit/Myrinet/Infiniband, HP Hyperfabric, AIX cluster, SGI MPI and

any supported MS-MPI interconnects.

9 The RADIOSS (Bulk Data format) Multi-Body Dynamics solution sequence is not supported on HP-UX 11.23 ia-64

architecture.

10 MotionSolve does not support IBM AIX architecture.

11 HyperXtrude solver is only supported on IBM AIX 64-bit architecture.


System Requirements

Minimum system requirements for HyperWorks applications

The following table lists the minimum system requirements that are necessary to run any HyperWorks 32-bit/64-bit

applications on supported operating systems and hardware platforms.

UNIX Windows

Operating Systems HP-UX (PARISC)- HP-UX 11.11 32-bit only

Linux x86 – SuSe 9.2/RHEL 4/5.2

Linux x86_64 (AMD64/EM64T) – SLED 10

SP1/RHEL 4/5.2

IBM AIX**– IBM AIX 5.3

**(restricted applications – check supported

platform list)

Windows XP (32-bit/64-bit)

Windows Vista (32-bit/64-bit)

Memory 256 MB (dedicated memory) 256 MB (dedicated memory)

Installation Disk

Space

HP-UX (PARISC) 32-bit

Linux x86

Linux x86_64

IBM AIX

5.5 GB

~5 GB

~5 GB

4.5 GB

~4 GB

Graphics Hardware A high-end OpenGL 3D graphic accelerator

supporting true color visual (24 bit) is

recommended for best graphics performance

for running the HyperWorks OpenGL

executable.

HyperView, MotionView, HyperMesh, and

HyperForm require OpenGL V 1.1 or greater.

Installing and updating to the most recent

patches or drivers for your OpenGL video

adapter is recommended for better

performance.

Screen resolution required: 1280x1024 or

higher.

A Windows compatible graphics adapter

capable of running OpenGL and supporting at

least high color (16 bit) or true color (24 bit).

We recommend a high-end OpenGL graphics

accelerator supporting true color (24 bit) for

best performance and graphics quality with at

least 256MB dedicated onboard memory.

HyperView, MotionView, HyperMesh, and

Manufacturing Solutions require OpenGL V

1.1 or greater.

Screen resolution required: 1280x1024 or

higher.

Browser

(need for Plugin)

Netscape Navigator 4.7x (HP-UX)

FireFox 2.0 (Linux)

Microsoft Internet Explorer 6.0 and above

Online Help FireFox 2.0 FireFox 2.0


(may have issues on newer

versions of the browsers

shown)

Internet Explorer 6.0

Additional Specifications for Specific Applications

Additional requirements and limitations:

All Applications

Altair HyperWorks 32-bit applications cannot be launched from within a 64-bit Linux operating system

environment. To run Altair HyperWorks on a Linux 64-bit operating system, you must install the 64-bit version of

HyperWorks.

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

client’s 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.

FLEXlm Hardware Key (Dongle) Support (Windows 32-bit only) Local installations of HyperWorks on Windows operating systems may either use an Ethernet (MAC) address or a

hardware key (dongle). If you choose to use a dongle, the following table identifies the type of dongle supported with

FLEXln under the Windows (32-bit only). Altair ships USB FLEXID=9 dongles.

Note While Rainbow Sentinel dongles are no longer available, they are still supported.


Recommended Graphics Boards

The following table lists the recommended CAE/CAD graphic boards for use with the Altair HyperWorks suite of

applications. Please note that all driver support for these cards should be addressed to the appropriate manufacturer of the

graphic board.

AMD/ATI Visualization Series (FireGL/FirePro)


nVIDIA Quadro FX Series

Notebook/Laptop cards


Linux Graphic Card Driver Issues

Some known limitations/issues with the hardware accelerated Linux drivers for the current AMD ATI FirePro/FireGL and NVIDIA Quadro FX cards are listed below. Please reference the original release notes directly from the AMD/ATI (www.amd.com) and NVIDIA (www.nvidia.com) websites for detailed information and other known issues/limitations.

NVIDIA Quadro FX Linux Issues/Limitations (180.29 drivers)

Many 2.4 and 2.6 x86_64 kernels have an accounting problem in their implementation of the change_page_attr kernel interface. Early 2.6 kernels include a check that triggers a BUG() when this situation is encountered (which kills the current OpenGL application or the X server). The accounting issue has been resolved in the 2.6.11 kernel or later.

NVIDIA drivers check for this BUG()in kernel versions between 2.6.0 and 2.6.11 where it disables the usage of change_page_attr kernel interface. This avoids the accounting issue but leaves the system open to cache aliasing problems.

Note: This change_page_attr accounting issue and BUG() can be triggered by other kernel subsystems that rely on this interface. If you are using a 2.6 x86_64 kernel, it is recommended that you upgrade to a 2.6.11 or later kernel.

1. X server fails to start / errors in X log

a) X log conatins:

(EE) NVIDIA(0): The NVIDIA kernel module does not appear to

(EE) NVIDIA(0): be receiving interrupts generated by the NVIDIA graphics

(EE) NVIDIA(0): device PCI:x:x:x. Please see the COMMON PROBLEMS

(EE) NVIDIA(0): section in the README for additional information.

This usually means there is a problem with PCI IRQ, I/O APIC or other conflicts in the system and any one (or combination of the below) parameters may help resolve the problem.

Parameter Behavior

pci=noacpi don't use ACPI for PCI IRQ routing

pci=biosirq use PCI BIOS calls to retrieve the IRQ routing table

noapic don't use I/O APICs present in the system

acpi=off disable ACPI

b) X log contains:

(EE) NVIDIA(0): The interrupt for NVIDIA graphics device PCI:x:x:x

(EE) NVIDIA(0): appears to be edge-triggered. Please see the COMMON

(EE) NVIDIA(0): PROBLEMS section in the README for additional information.

This often is seen with older Linux 2.4 kernels, which do not fully support ACPI or 2.6 kernels when ACPI is disabled or fails to initialize. Current workarounds are to:

a. Update to a newer system BIOS.


b. Update to a 2.6 kernel with ACPI enabled.

c. Pass the ‘noapic’ option to the kernel to force PIC routing

.

2. Problems starting OpenGL applications

This may happen if you have stale symlinks and/or other libraries in the way. A few things to try are:

a. Simply rerun ‘ldconfig’.

b. Check to make sure the output from ‘xdpyinfo | GLX’ includes both GLX and NV-GLX (if not, check the /etc/X11/xorg.conf under Module to make sure Load “glx” is being loaded).

3. Upgrading to a newer kernel and the NVIDIA module will not load or there is no hardware

acceleration after upgrade.

The kernel interface layer of the NVIDIA driver needs to be specifically compiled for the configuration and version of the kernel in use. If you upgrade the kernel you will have to reinstall the NVIDIA driver.

ADVANCED USERS ONLY: You can install the NVIDIA kernel module for a non running kernel (for example, in the situation where you just built and installed a new kernel, but have not rebooted yet) with a command line such as this:

# sh NVIDIA-Linux-x86_64-180.44-pkg1.run --kernel-name='KERNEL_NAME'

Where 'KERNEL_NAME' is what uname -r would report if the target kernel were running.

4. OpenGL applications crash

This could be from many different factors. Below are some things to try to remedy or improve the on the problem of stability.

a. Set the environment variable _GL_SINGLE_THREADED=1.

b. Set the environment variable _GL_NO_DSO_FINALIZER=1.

c. Check to make sure that NVIDIA’s ELF TLS library is being properly linked with libpthread before loading libGL or manually link the application to libpthread.

5. SELinux NVIDIA driver requirement (HyperWorks products are tested with SELinux enabled)

The SELinux requirement can be addressed via two mechanisms after the NVIDIA Linux graphics driver has been installed: -If you do not wish to use SELinux enforcement, you can disable it by running the `setenforce 0` command before starting X, or by adding selinux=0 to the end of the kernel line in /etc/grub.conf and rebooting. -If you wish to use SELinux enforcement, you will need to change the security context of the NVIDIA X driver module and of the server-side NVIDIA GLX extension module. To achieve this, please run the commands listed for your platform below: Linux/x86 (32-bit): # chcon -t texrel_shlib_t /usr/lib/xorg/modules/drivers/nvidia_drv.so # chcon -t texrel_shlib_t /usr/lib/xorg/modules/extensions/libglx.so.1.0.**** # chcon -t texrel_shlib_t /usr/lib/tls/libnvidia-tls.so.1 # chcon -t texrel_shlib_t /usr/lib/libGLcore.so.1.0.****

Linux/x86-64 (64-bit): # chcon -t texrel_shlib_t /usr/lib64/xorg/modules/drivers/nvidia_drv.so # chcon -t texrel_shlib_t /usr/lib64/xorg/modules/extensions/libglx.so.1.0.**** # chcon -t texrel_shlib_t /usr/lib64/libGLcore.so.1.0.**** # chcon -t texrel_shlib_t /usr/lib64/tls/libnvidia-tls.so.1


6. General NVIDIA driver stability issues

I/O APIC (SMP kernel)

If you are experiencing stability problems with a Linux SMP computer and seeing I/O APIC warning messages from the Linux kernel, system reliability may be greatly improved by setting the ‘noapic’ kernel parameter.

Local APIC (UP)

On some systems, setting the "Local APIC Support on Uniprocessors" kernel configuration option can have adverse effects on system stability and performance. If you are experiencing lockups with a Linux UP computer and have this option set, try disabling local APIC support.

MMCONFIG conflicts

Run ‘dmesg | grep MMCONFIG’ and look at the output, if it outputs “PCI: Using MMCONFIG” try disabling it via the kernel parameter ‘pci=nommconf’ and reboot machine and test.

Video group permissions on the /dev/nvidia* card

Run either ‘usermod –A video username’ or ‘gpasswd –a username video’ command to add user to group ‘video’. If application does not launch and/or kicks the user out of the current X session this may be the cause.

AMD/ATI FirePro and FireGL Linux Issues/Limitations (ATI Catalyst 8.563 driver)

AMD ATI FirePro/FireGL Linux drivers are designed to work on Red Hat Enterprise Linux and Novell/SuSe products even though the package can be installed and ran on many other Linux distributions.

Requirements:

1. The display driver requires POSIX shared memory to be enabled on the system.

2. Kernel Source package is no longer required if Kernel Header package is installed.

3. 32-Bit packages must be installed for 64-Bit Linux drivers to install or work. a. XFree86-Mesa-libGL b. libstdc++ c. libgcc d. XFree86-libs e. fontconfig f. freetype g. zlib h. gcc

1. OpenGL issues with HyperMesh refreshing.

If there seems to be an OpenGL window refreshing issue in HyperMesh with the ATI proprietary drivers you may need to change the OpenGL overlay option to “on”. You can enable it by running the command ‘aticonfig –ovt=opengl’

2. OpenGL framebuffer Corruption

Whenever any OpenGL application is rendered, the rendered output appears "scrambled" and unreadable. The problem looks to be caused when Anti-Aliasing is forced. A solution to this problem is to


a. Open the ATI/AMD Catalyst Control Center

b. Expand the item labeled '3D' in the options tree on the left-hand side of the window

c. Select "Anti-Aliasing" and check the box which reads: "Override application setting"

d. Apply the settings and close the control center.

3. System freezes at startup after installing the driver

If this occurs try the following:

a. Turn off the Red Hat Graphical boot from grub config:

b. Edit the grub config file located at /boot/grub/grub.conf

c. Remove the 'rhgb' from the kernel line in order to disable the Red Hat Graphical boot.

4. Novell’s Sax2 support

Currently ATI proprietary Linux drivers do not work well with Sax2. It is recommended not to use Sax2 in correlation with the ATI proprietary drivers.

5. Red Hat Enterprise Linux 5.0 and higher (RHEL 5.0) SELinux issues

SELinux may cause problems during the installation of the ATI proprietary drivers and it is recommended that you stop the SELinux during the installation of the ATI proprietary drivers, wither via the ‘setenforce 0’ or via the kernel parameter selinux=0.

Once the installation is complete you may re-enable SELinux. If SELinux is enabled and set to enforcing you may need to change the context of the fglrx_dri.so file for it to load properly:

‘chcon –t textrel_shlib_t /usr/lib/dri/fglrx_dri.so’

Note: Substitute lib with lib64 where appropriate.


Non-US keyboards

HyperWorks ships with the keyboard configuration set for a US keyboard. Other countries (e.g. Germany) use extended keyboards to generate native characters not present in the US ASCII character set. Use the following instructions for your o/s to install a local keyboard configuration.

UNIX

On UNIX to configure your installation for Non-US keyboards, please perform the following after installing HyperWorks:

1. Locate the directory in which HyperWorks has been installed.

1. This directory will be referred to as <install location>.

2. Change directories to <install location>/scripts/invoke.

3. Copy the contents of .hwlocal_sample.sample into the file .hwlocal_settings.

4. Open .hwlocal_settings in a text editor and locate the keyboard configuration you wish to set.

5. At the end of the configuration description, change the '0' to a '1' for each configuration to be enabled.

6. Save and close the file to enable these settings.

Note To disable the non-US keyboard support, change the trailing '1' to a '0'. .

Windows XP and Windows XP64

1. On Windows, follow these instructions to configure your non-US keyboard.

2. From the Start menu, select Settings, then Control Panel.

3. Select Keyboard.

4. Select Input Locales tab.

5. Click Properties or Change and select the predefined locale from the drop-down list.

6. Click OK.

7. Click OK to close the Keyboard dialog.

Note If your keyboard requirements are not in the standard list, you can add it in using the Add… option on the Properties dialog. If you prefer, you can access Input Locales from the Regional Settings dialog.

Windows Vista

Follow these instructions to configure your non-US keyboard on Windows.

1. From the Start menu, select Settings, then Control Panel.

2. Select Regional and Language Options.

3. Select Keyboards and Languages tab.

4. Click Change Keyboard and select the predefined locale from the drop-down list.

5. Click OK.

6. Click OK to close the Regional and Language Options dialog.


RADIOSS Executable List 10.0 - 9.0.2 - 51l

rev : 10.0

Date of document release : 1.12.2008

written by : Wienholtz Olivier

still to be verified by : Eric Lequiniou

On any question, send an Email to Olivier Wienholtz

aix64

Version Target Machine Specifications Radflex Compiler Information Notes

pwr4

SMP, 64 Bits

IBM Power 4

AIX

- Supported OS :

AIX 5.2 radflex10_ibm

F90 : xlfcmp 8.1.0.1

C : C 6.0.0.0 -/-

pwr4_spmd

SPMD, 64 Bits

IBM Power 4

AIX

Cluster

- Supported OS :

AIX 5.2

- MPI distribution :

PPE.POE 3.2.0.0

radflex10_ibm F90 : xlfcmp 8.1.0.1

C : C 6.0.0.0 -/-

hpux64


hp11w

SMP, 64 Bits

HP PA8000

HPUX 11

- Supported OS :

HPUX-11.00,

Patch level :

HP compiler F90 v2.9.2,

Shared libF90 B.11.11.91

radflex10_hp F90 : HP F90 v2.9.2

C : aCC A.03.63 -/-

hp11_spmd

SPMD, 64 Bits

HP PA8000

HPUX 11

Gigabit Ethernet,

HP Hyperfabrick

Cluster

- Supported OS :

HPUX-11.00,

Patch level :


Fortran90 B.11.11.91


HP MPI 01.06.00.00

radflex10_hp F90 : HP F90 v2.9.2

C : aCC A.03.63 -/-

hpuxia64


hp11i

SMP, 64 Bits

ITANIUM 2

HPUX 11

- Supported OS :

HPUX-11.22 IA64,

Patch level :


Sharedf libF90 B.11.23.16

radflex10_hp

F90 : HP F90 v2.9.2

C : aCC : HP ANSI C++

B3910B A.05.55

-/-

hp11i_spmd ITANIUM 2 - Supported OS : radflex10_hp F90 : HP F90 v2.9.2 -/-

mailto:[email protected]�


SPMD, 64 Bits HPUX 11

Gigabit Ethernet,

Myrinet,

Infiniband

Cluster

HPUX-11.22 IA64,

Patch level :


Shared libF90 B.11.23.16


HP MPI 02.00.00.00

C : aCC : HP ANSI C++

B3910B A.05.55

linux32


p4linux9

SMP, 32 Bits

INTEL PENTIUM 4

Linux

- Supported OS :

Linux with glibc version 2.3 :

Suse 9, Suse 10,

Redhat Enterprise Linux 3,


Fedora, Redhat 9.0

radflex10_linux F90 : pgf90 5.1-6

C : pgcc 5.1-6 -/-

p4linux9_sp

SMP, 32 Bits

INTEL PENTIUM 4

Linux

Extended Single Precision

Version

- Supported OS :


Suse 9, Suse 10,



Fedora, Redhat 9.0

radflex10_linux F90 : pgf90 5.1-6

C : pgcc 5.1-6

10.0 and

9.0.2 only

linux64


linux964

SMP, 64 Bits

AMD Opteron

Linux

- Supported OS :


Suse 9,



Fedora

- Compatibility :

INTEL EM64T

radflex10_

linux

F90 : pgf90 6.0.5

C : pgcc 6.0.5 -/-

linux964_sp

SMP, 64 Bits

AMD Opteron

Linux


Version

- Supported OS :


Suse 9, Suse 10,

radflex10_

linux

F90 : pgf90 6.0.5

C : pgcc 6.0.5

10.0 and

9.0.2 only




Fedora

- Compatibility :

INTEL EM64T

hplinux964_spmd

SPMD, 64 Bits

HP Cluster

AMD Opteron

Linux

Gigabit Ethernet

Myrinet,

Infiniband

- Supported OS :


Suse 9, Suse 10


Redhat Enterprise Linux 4


HP MPI 02.02.05.01

radflex10_

linux

F90 : pgf90 6.0.5

C : pgcc 6.0.5

Use

linux964_s

pmd

starter

hplinux964_spmd_

sp

SPMD, 64 Bits

HP Cluster

AMD Opteron

Linux

Gigabit Ethernet

Myrinet,

Infiniband


Version

- Supported OS :


Suse 9, Suse 10




HP MPI 02.02.05.01

radflex10_

linux

F90 : pgf90 6.0.5

C : pgcc 6.0.5

10.0 and

9.0.2 only

Use

linux964_s

pmd_sp

starter

oplinux964_spmd

SPMD, 64 Bits

AMD Opteron

Linux

Gigabit Ethernet

Myrinet,

Infiniband

Cluster

- Supported OS :


Suse 9,



Fedora


OpenMPI 1.2

- Compatibility :

INTEL EM64T

radflex10_

linux

F90 : pgf90 6.0.5

C : pgcc 6.0.5

Use

linux964_s

pmd

starter

oplinux964_spmd_

sp

SPMD, 64 Bits

AMD Opteron

Linux

Gigabit Ethernet

Myrinet,

Infiniband

Cluster


Version

- Supported OS :


Suse 9,



radflex10_

linux

F90 : pgf90 6.0.5

C : pgcc 6.0.5

10.0 and

9.0.2 only

Use

linux964_s

pmd_sp

starter


Fedora


OpenMPI 1.2

- Compatibility :

INTEL EM64T

p4linux964_spmd

SPMD, 64 Bits

INTEL XEON

EM64T

Linux

Gigabit

Ethernet,

Myrinet,

Infiniband

Cluster

- Supported OS :


Suse 9,



Fedora


INTEL MPI 3.0

radflex10_

linux

F90 : Intel(R) Fortran

Compiler for Intel(R)

EM64T-based

applications, Version 9.1

Build 20070109 Package

ID: l_fc_c_9.1.041

C : Intel(R) C Compiler for

Intel(R) EM64T-based


Build 20070109

Package ID:

l_cc_c_9.1.046

-/-

p4linux964_spmd_

sp

SPMD, 64 Bits

INTEL XEON

EM64T

Linux

Gigabit

Ethernet,

Myrinet,

Infiniband

Cluster


Version

- Supported OS :


Suse 9,



Fedora


INTEL MPI 3.0

radflex10_

linux



EM64T-based



ID: l_fc_c_9.1.041




Build 20070109

Package ID:

l_cc_c_9.1.046

10.0 and

9.0.2 only

hpp4linux964_

spmd

SPMD, 64 Bits

HP Cluster

INTEL XEON

EM64T

Linux

Gigabit

Ethernet,

Myrinet,

Infiniband

- Supported OS :


Suse 9,10,



Fedora


radflex10_

linux



EM64T-based



ID: l_fc_c_9.1.041


Use

p4linux964

_spmd

starter


Cluster HP MPI 02.02.05.01 Intel(R) EM64T-based


Build 20070109

Package ID:

l_cc_c_9.1.046

hpp4linux964_

spmd_sp

SPMD, 64 Bits

HP Cluster

INTEL XEON

EM64T

Linux

Gigabit

Ethernet,

Myrinet,

Infiniband

Cluster


Version

- Supported OS :


Suse 9,10,



Fedora


HP MPI 02.02.05.01

radflex10_

linux



EM64T-based



ID: l_fc_c_9.1.041




Build 20070109

Package ID:

l_cc_c_9.1.046

10.0 and

9.0.2 only

Use

p4linux964

_spmd_sp

starter

linuxia64


il9

SMP, 64 Bits

INTEL ITANIUM 2

Linux

- Supported OS :


Suse 9, Suse 10,



radflex10_linux

F90 : Intel Fortran

Version 9.0,

Build 20050430

C : Intel C, Version 9.0,

Build 20050430

-/-

il9hp_spmd

SPMD, 64 Bits

HP Cluster

ITANIUM 2

Linux

Gigabit Ethernet,

Myrinet,

Infiniband

Cluster

- Supported OS :


Suse 9,




HP MPI 02.01.00.00

radflex10_linux

F90 : Intel Fortran

Version 9.0,

Build 20050430


Build 20050430

Use

il9_spmd

starter

il9hp_spmd_sp

SPMD, 64 Bits

HP Cluster

ITANIUM 2

Linux

Gigabit Ethernet,

Myrinet,

Infiniband


Version

- Supported OS :


Suse 9,


radflex10_linux

F90 : Intel Fortran

Version 9.0,

Build 20050430


Build 20050430

10.0 and

9.0.2 only

Use

il9_spmd_s

p


Cluster Redhat Enterprise Linux 4


HP MPI 02.01.00.00

starter

il9sgi_spmd

SPMD, 64 Bits

SGI ALTIX

INTEL ITANIUM 2

Linux

Machines

- Supported OS :


Suse 9,




SGI Propack 4.x,

sgi-mpt-1.11.1-sgi400r1

radflex10_linux

F90 : Intel Fortran

Version 9.0,

Build 20050430


Build 20050430

Use

il9_spmd

starter

il9sgi_spmd_sp

SPMD, 64 Bits

SGI ALTIX

INTEL ITANIUM 2

Linux

Machines


Version

- Supported OS :


Suse 9,




SGI Propack 4.x,

sgi-mpt-1.11.1-sgi400r1

radflex10_linux

F90 : Intel Fortran

Version 9.0,

Build 20050430


Build 20050430

10.0 and

9.0.2 only

Use

il9_spmd_s

p

starter

solaris10-x64


sol10x64

SMP, 64 Bits

AMD Opteron

INTEL EM64T

Solaris 10

Machines

- Supported OS :

Solaris 5.10

radflex10_x86s

ol10

F90 : Sun Fortran 95 8.3

SunOS_i386

Patch 127002-01

2007/07/18

C : Sun C 5.9

SunOS_i386

Patch 124868-01

2007/07/12

Version

10.0 and

9.0.2 only

sol10x64_spmd

SPMD, 64 Bits

AMD Opteron

INTEL EM64T

Solaris 10

Clusters

- Supported OS :

Solaris 5.10


sun-hpc-ct-7.1 (Open MPI

1.2.5r16572-ct7.1b003r3852)

radflex10_x86s

ol10

F90 : Sun Fortran 95 8.3

SunOS_i386

Patch 127002-01

2007/07/18

C : Sun C 5.9

SunOS_i386

Patch 124868-01

Version

10.0 and

9.0.2 only


2007/07/12

win32

Version Target

Machine Specifications Radflex Compiler Information Notes

p4win32

SMP, 32 Bits WINDOWS

- Supported OS :

Windows XP,

Windows Server 2003,

Windows Vista

radflex10_wnt

F90 : Intel(R) Visual Fortran

Compiler for applications

running on IA-32, Version 10.0

Build 20070426 Package ID:

W_FC_P_10.0.025

C : Intel(R) C++ Compiler for

applications running on IA-32,

Version 10.0 Build 20070426

Package ID: W_CC_P_10.0.025

10.0 and

9.0.2 only

p4win32_sp



Version

- Supported OS :

Windows XP,

Windows Server 2003,

Windows Vista

radflex10_wnt



running on IA-32, Version 10.0

Build 20070426 Package ID:

W_FC_P_10.0.025


applications running on IA-32,

Version 10.0 Build 20070426


10.0 and

9.0.2 only

win64

Version Target

Machine Specifications Radflex Compiler Information Notes

p4win64

SMP, 64 Bits

WINDOWS

- Supported OS :

WINDOWS Server 2003 64 Bit,

WINDOWS XP 64

- Compatibility :

AMD Opteron

INTEL EM64T

radflex10_wnt



running on Intel(R) 64, Version

10.0 Build 20070426 Package

ID: W_FC_P_10.0.025


applications running on Intel(R)

64, Version 10.0 Build 20070426


Copyright

-/-


p4win64_sp



Version

- Supported OS :

WINDOWS Server 2003 64 Bit,

WINDOWS XP 64

- Compatibility :

AMD Opteron

INTEL EM64T

radflex10_wnt





ID: W_FC_P_10.0.025



64, Version 10.0 Build 20070426


Copyright

10.0 and

9.0.2 only

p4win64_sp

md

SPMD, 64

Bits

WINDOWS

- Supported OS :

WINDOWS Server 2003, 64 Bits

Compute Cluster Edition

- Compatibility :

AMD Opteron

INTEL EM64T


MS MPI

radflex10_wnt





ID: W_FC_P_10.0.025



64, Version 10.0 Build 20070426


Copyright

-/-

p4win64_sp

md_sp

SPMD, 64

Bits

WINDOWS


Version

- Supported OS :

WINDOWS Server 2003, 64 Bits

Compute Cluster Edition

- Compatibility :

AMD Opteron

INTEL EM64T


MS MPI

radflex10_wnt





ID: W_FC_P_10.0.025



64, Version 10.0 Build 20070426


Copyright

10.0 and

9.0.2 only


Altair Licensing 10.0 Supported Platforms The Altair License Management System 10.0 software is available for downloading by registered customers from the Altair Web site through the Altair Client Center (http://www.altairhyperworks.com/clientcenter).

The images on the Altair web site are one tar file per platform. Download the images for the platforms from which you expect the license manager and usage report system to be launched. If you plan to run the license manager and the usage report system on different server, download the proper packages for both servers.

Consult the following list to download the right package for your system.

Package Name Platform Details

altair_flexlm-10.0.amd64_s8 .tar Li n u x-AMD64 SUSE Enterprise Server8 or later, RHEL3.0 or later 64 bits

altair_flexlm-10.0.hp700_u11.tar H P UX PARISC HPUX 11.11 32 bits

altair_flexlm-10.0.i86_r9 .tar Li nux-x86 RH 9.0 or higher 32 bits (glibc >= 2.3)

altair_flexlm-10.0.it32_hp11.tar H P U X-Itanium 11.23 32 bits

altair_flexlm-10.0.it64_re3.tar Li n ux-Itanium RHEL 3.0 IA 64 bits

altair_flexlm-10.0.ppc64_se9 .tar Li n ux-PPC64 SUSE Enterprise Server 9 or later PowerPC 64 bits

altair_flexlm-10.0.ppc_u4.tar A IX 5.1or higher Power PC 32 bits

altair_flexlm-10.0.sgi32_u6.tar S G I IRIX 6.5 32 bits

altair_flexlm-10.00.sun4_u7.tar S U N S olaris Sparc 2.7 to 2.10 32 bits

altair_flexlm-10.0.sun64_u5.tar S U N Solaris Sparc 2.7 to 2.10 64 bits

altair_flexlm-10.0.x64_sun10.tar S U N Solaris 10 AMD 64 bits

licensing10.0_win32.exe Windows XP

licensing10.0_win64.exe Windows XP 64

Documents

HyperWorks 10.0システム要件一覧7 RADIOSS/OptiStruct (Bulk Data Format input). The HP-MPI is required for OptiStruct SPMD on Linux operating systems. This includes x86, x86_64