Installation Note

for LINUX and UNIX platforms

Hexpress v2.5
Unstructured Grid Generator

- December 2007 -

NUMERICAL MECHANICS APPLICATIONS

Installation Note
for LINUX and UNIX platforms
Hexpress v2.5
Documentation v2.5-a

NUMECA International
5, Avenue Franklin Roosevelt
1050 Brussels
Belgium
Tel: +32 2 647.83.11
Fax: +32 2 647.93.98
Web: http://www.numeca.com

NUMERICAL MECHANICS APPLICATIONS

Contents

CHAPTER 1: Introduction

1-1

CHAPTER 2: System Requirements

2-1

2-1 Overview

2-1

2-2 Supported Platforms & Operating Systems

2-1

2-3 Hardware Requirements

2-2

2-4 Memory & Disk Space Requirements

2-3

2-5 Graphics Requirements

2-3

CHAPTER 3: Installation

3-1

3-1 Introduction

3-1

3-2 Install Hexpress 2.5-4: no Hexpress Installed

3-1

3-3 Install Hexpress 2.5-4: Multi-Version Environment

3-2

CHAPTER 4: License Management

4-1

4-1 Introduction

4-1

4-2 Installation of Node-locked License

4-1

4-3 Installation of Floating License

Floating License on UNIX/LINUX License Server
Floating License on UNIX or LINUX Client

4-2
4-2
4-3

4-4 Update of License File

Update of Node-locked License
Update of Floating License

4-3
4-4
4-4

4-5 Dedicated License for CATPart Files Import

How to Get Dedicated License ?
How to Install Dedicated License ?
How to Update License ?

4-4
4-4
4-4
4-5

CHAPTER 5: User Configuration

5-1 Overview

5-1
5-1

5-2 User Configuration

5-1

5-3 Software Launch

5-1

CHAPTER 6: Uninstallation

6-1

6-1 Overview

6-1

6-2 Uninstall Hexpress 2.5 (Mono-Version Environment)

6-1

6-3 Uninstall Hexpress Partly (Multi-Version Environment)

6-2

6-4 Uninstall Hexpress Fully (Multi-Version Environment)

6-2

6-5 Uninstall License Service

6-2

INSTALLATION NOTE

iii

Contents

CHAPTER 7: Troubleshooting

iv

7-1

7-1 Introduction

7-1

7-2 Hexpress Not Starting

7-1

7-3 Graphical Problems & System Crashes

7-2

7-4 Hexpress Screen Flashes

7-3

7-5 Hexpress Drivers Not Detected

7-3

INSTALLATION NOTE

CHAPTER 1:

Introduction

This note details the installation procedure of the unstructured grid generator Hexpress v2.5 developed
by NUMECA.
The package is delivered with full options, except for the direct importation of CATPart files (generated by CATIA v5) which requires a dedicated external license from TTF NUMECA partner. More
details about this dedicated license can be found in section 4-5.
This installation note consists of six parts respectively dedicated to:

general information for all platforms, including system requirements,

the installation procedure itself,
the license installation,
the user configuration and launch procedure,
the uninstallation procedure,
possible troubleshooting.

The user is strongly advised to consult the system requirements described in the first
part of this note prior to start any installation of the Hexpress v2.5 package. Troubles
may indeed appear during the installation and configuration phases in case the listed
hardware and software requirements would not be fully satisfied.
The installation procedure and the license installation should be carefully followed to ensure a fast and
smooth installation. In case problems occur during the installation or configuration phases, the troubleshooting section should give a step by step analysis to detect and help solving the cause of the problem.
Please do notice that the documentation attached to Hexpress v2.5 is NOT installed during the installation procedure.
Please contact NUMECA support team at +32-2-647.83.11 or send an e-mail to support@numeca.be for
more information or in case of persistent problems. To allow NUMECA support to help you out within the
shortest delays, please provide a detailed description of the observed behaviour and performed analysis
using the troubleshooting section of this installation note.

INSTALLATION NOTE

1-1

Introduction

1-2

INSTALLATION NOTE

CHAPTER 2:

2-1

System Requirements

Overview

In this chapter, system requirements for a proper installation and use of Hexpress v2.5 are listed. In order
to guarantee a smooth and successful installation, the specifications of your system must match with the list
of supported platforms and operating systems as described here below. The following system requirements
and limitations are listed in the next sections:

supported platforms and operating systems,

hardware requirements,
memory and disk space requirements,
graphics requirements.

2-2

Supported Platforms & Operating Systems

A detailed list of supported platforms and operating systems is proposed in the tables here below:
On LINUX:
Processor

Formally tested on

Also known to run ona

32 bits / 64 bits

x86b

Red Hat 9.0

32 bits

x86b

Enterprise 2.x, 3.x

32 bits

x86b

SuSe 9.x

32 bits

x86b

Mandrake 9

32 bits

a. known from partners and/or customers. No official support offered on these combinations.
b. 32 bits processors that are compatible with Intel 8086 set of instructions. Includes Pentium 4, Xeon, Pentium D, AMD Sempron, Athlon and Celeron.

INSTALLATION NOTE

2-1

System Requirements

Hardware Requirements

Processor

Formally tested on

Also known to run ona

32 bits / 64 bits

x86_64b

Enterprise 4.x

64 bits

x86_64b

SuSe 9.x

64 bits

x86_64b

SuSe 10.1, 10.2

64 bits

x86_64b

Enterprise 3.x

64 bits

IA-64c

Enterprise 2.x, 3.x

64 bits

a. known from partners and/or customers. No official support offered on these combinations.
b. 64 bits processors that are compatible with Intel 8086 set of instructions. Includes Opteron, Athlon 64, Athlon 64 X2, Athlon 64 FX, Sempron, Turion, Xeon EM64T, Core2 Duo and Core2 Quad.
c. 64 bits architecture proposed by Intel, that is not compatible with Intel 8086 set of instructions. Includes Itanium2.

Please contact NUMECA support team at support@numeca.be if your platform of preference is not listed
in one of the tables above. Hexpress 2.5-4 does however explicitly not run on the following configurations:

x86_64 processors running LINUX SuSe 10.3,

HP Itanium 2 running HP-UX 11,
IBM PowerPC running LINUX.

2-3

Hardware Requirements

Next to the standard hardware (monitor, keyboard and mouse), some specific recommendations apply in
the use of NUMECA software:

a DVD-ROM drive is required for installation purposes.

a 3-buttons mouse is strongly recommended to use all capabilities in Hexpress.
the monitor should support 24-bit colour graphics and have a 1280x1024 pixel resolution for sufficiently clear visualization of the interface and the graphics.

an ethernet card is mandatory on LINUX when a node-locked license is used.

2-4

Memory & Disk Space Requirements

The Read Only Memory (RAM) required to run Hexpress depends upon several factors, in particular
including the number of grid points inserted in the grid, the introduction of full non matching connections
(FNMB) and the number of viscous layers inserted in the final mesh.
The use of minimum 1 Gb RAM is mandatory, but the installation of 2 Gb is recommended. As a general
guideline, about 800 Mb RAM are generally required to run a one million nodes project
The suggested swap space should be equivalent to at least 3 times the RAM installed.

2-2

INSTALLATION NOTE

Graphics Requirements

System Requirements

Similarly, a minimum disk space is required on the hard disk to allow the storage of the mesh files (including cache files). As a general guideline, about 900 Mb is required to store the mesh and cache directory for
a one million nodes project.

2-5

Graphics Requirements

The supported graphics cards are (according to HOOPS manual):

NVIDIA GeForce(2)(256).
NVIDIA GeForce(4)(256).
NVIDIA TNT 2.
3DLabs Wildcat III.

Hexpress makes use of the advantages of the available Graphics Card. Some trouble may however come
up with the default driver OPENGL since it may not be supported by the user host computer and machine
display.
In order to set the system compatible with a more portable driver, typically X11 driver is used under UNIX
(or LINUX) instead. Note however that the proposed drivers are usually less efficient in terms of graphical
speed than the default driver.
To change the driver used by Hexpress:
1.

Open the file ~\.numeca\.drivers

2.

Type "host_name display_name possible_drivers chosen_driver"

i.e. gauss.numeca.be gauss OPENGL:X11 X11

Furthermore, the driver can be manually specified through the following commands:
in csh, tcsh or bash shell:
setenv NI_DRIVER X11
in korn shell:
NI_DRIVER=X11
export NI_DRIVER
The selection will take effect at the next session.

INSTALLATION NOTE

2-3

System Requirements

Graphics Requirements

2-4

INSTALLATION NOTE

CHAPTER 3:

3-1

Installation

Introduction

To install Hexpress 2.5-4, it is important to check first whether previous versions of Hexpress were
installed on the machine:

Providing no NUMECA package is installed on the machine, Hexpress 2.5-4 installation may be performed as described in section 3-2.

Hexpress 2.5-4 can possibly be installed besides Hexpress 2.3. If so, all versions can be accessed
through a unique multi-version environment. Please refer to section 3-3 for more details on the installation
of Hexpress in a multi-version environment.

The installation procedure detects automatically the operating system on which the user is
logged in. To install Hexpress 2.5-4 on other operating systems, the user must select the
corresponding tar file and log onto a workstation with such OS, otherwise the procedure
will be automatically stopped. Please refer to section 3-2 for more details.

3-2

Install Hexpress 2.5-4: no Hexpress Installed

Providing no Hexpress package is installed on the machine, Hexpress 2.5-4 installation may be performed
on a UNIX or LINUX platform as follows:
1.

Log onto the workstation corresponding to the selected OS. Although the installation procedure does not
request absolutely the "root" permission, it is strongly recommended to check the permission of the disk and
directory the user will select for the software installation.

2.

The installation of Hexpress 2.5-4 package under LINUX requires about 350 Mb. Please check that the
necessary disk space is available prior to start the installation process.

3.

The tar files included on the DVD-ROM (or accessible from www.numeca.be) are named
install_hexpress_25_4_OSname.tar (OSname is corresponding to the OS selected); they are located in the
corresponding "/platform/OS" sub-directories.

INSTALLATION NOTE

3-1

Installation

4.

Install Hexpress 2.5-4: Multi-Version Environment

Copy the tar file install_hexpress_25_4_Osname.tar into a temporary directory. Check that the file can be
accessed with full permission and extract it by typing the command line: tar -xvf
install_hexpress_25_4_OSname.tar.
Do
NOT
extract
the
tar
file
in
the
target
directory
NUMECA_INSTALLATION_DIRECTORY in which hexpress25_4 will be installed.

5.

Go to the temporary directory containing the files extracted from the tar archive and type the command ./
install_hexa <ENTER>.

6.

The user will be asked to give the name of the installation directory, named
'NUMECA_INSTALLATION_DIRECTORY' hereafter. A directory name that does not already exist must be
used; otherwise the procedure will be automatically stopped.

7.

At the end of the installation process, the user will be asked whether a previous version should or not be
linked. Since no previous NUMECA package is installed on the machine (mono-version environment), the
answer is no.

8.

Finally, the so-called 'HostName' and 'HostID' information required to generate a license key will be shown.
This information should be sent at license@numeca.be. The HostName and HostID can also be obtained by
typing the commands NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/machine_type/install/lmutil lmhostid
-hostname <ENTER> and NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/machine_type/install/lmutil
lmhostid <ENTER>, with machine_type corresponding to the OS selected.

9.

In case NUMECA software should be installed on another OS, the previous seven steps must be repeated with
the new corresponding archive file corresponding to the other OS. In step 6 the same
NUMECA_INSTALLATION_DIRECTORY should be entered during the installation.

10.

When receiving the license file from NUMECA, perform the license installation as described in the next chapter.

11.

Perform the user configuration as described in Chapter 5.

12.

Launch the software as described in Chapter 5.

3-3

Install Hexpress 2.5-4: Multi-Version Environment

Hexpress 2.5-4 environment can possibly be installed besides Hexpress 2.3.

Providing Hexpress 2.3 package is adequately installed on the machine, Hexpress 2.5-4 can be straightforwardly installed in a multi-version environment on UNIX or LINUX as follows:
1.

Log onto the workstation corresponding to the selected OS. Although the installation procedure does not
request absolutely the "root" permission, it is strongly recommended to check the permission of the disk and
directory the user will select for the software installation.

2.

The installation of Hexpress 2.5-4 package under LINUX requires around 350 Mb. Please check that the
necessary disk space is available prior to start the installation process.

3.

The tar files included on the DVD-ROM (or accessible from www.numeca.be) are named
install_hxepress_25_4_OSname.tar (OSname is corresponding to the OS selected); they are located in the
corresponding platform/OS sub-directories.

4.

Copy the tar file install_hexpress_25_4_Osname.tar into a temporary directory. Check that the file can be
accessed with full permission and extract it by typing the command line tar -xvf
install_hexpress_25_4_OSname.tar.
Do
NOT
extract
the
tar
file
in
the
target
directory
NUMECA_INSTALLATION_DIRECTORY in which hexpress25_4 will be installed.

3-2

INSTALLATION NOTE

Install Hexpress 2.5-4: Multi-Version Environment

Installation

5.

Go to the temporary directory containing the files extracted from the tar archive and type the
command ./install_hexa <ENTER>

6.

The user will be asked to give the name of the installation directory
NUMECA_INSTALLATION_DIRECTORY in which Hexpress 2.3 has been previously
installed, otherwise the multi-version installation will not be set-up adequately.

7.

At the end of the installation process, the user will be asked whether previous versions should or
not be linked. A positive answer (yes) is required to enable concurrent launch Hexpress 2.3
or Hexpress 2.5-4, in case (and only in case) these versions have been partially or completely installed in separate NUMECA_INSTALLATION_DIRECTORY (e.g.: /usr/
numeca23_1/ and /usr/numeca25_4). If so, links must be created towards Hexpress 2.5-4 and
full pathname of Hexpress 2.3 (e.g.: /usr/numeca23_1/hexpress23_1) should be specified
upon request.

8.

Finally, the so-called 'HostName' and 'HostID' information required to generate a license key
will be shown. This information can be ignored.
License file delivered with Hexpress 2.3 cannot be used for Hexpress 2.5,
since security levels have been upgraded. Please send the Hexpress 2.3 license
file at license@numeca.be for an upgrade of the license file.

9.

In case NUMECA software should be installed on another OS, the previous six steps must be
repeated with the new corresponding archive file corresponding to the other OS. At this stage,
there is no need to create new links since they will already exist (if installed in the same installation direction specified at step 6). When receiving the license file, perform the license installation as described in the next chapter.

10.

Perform the user configuration as described in Chapter 5.

11.

Launch the software as described in Chapter 5.

INSTALLATION NOTE

3-3

Installation

3-4

Install Hexpress 2.5-4: Multi-Version Environment

INSTALLATION NOTE

CHAPTER 4:

4-1

License Management

Introduction

Before using NUMECA software, a valid FlexLM license key is required. There are two different types of
license:

FlexLM node-locked license key. A node-locked license is dedicated to a given computer and allows
access to NUMECA software on this computer only. In section 4-2 it is described how to obtain and
install such a license key.

FlexLM floating license key. With a floating license each software component is managed by an independent maximum number of concurrent accesses (number of processes). Floating licenses are managed
by a license server which checks if process access is free. The license can be accessed on the same computer but also on other computers (clients) which are connected through a network to the license server.
To obtain and install a floating license on a license server see section 4-3.1. To configure the clients for
the use of the floating license see section 4-3.2.
Standard license keys for Hexpress 2.5-4 are based on the version 9.2 of the FlexLM tools. Type the command .\lmutil lmver numeca into /NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/OSname/
install to know the FlexLM tools version used on the operating system of the license server.
License keys delivered with Hexpress 2.3 cannot be used with Hexpress 2.5, since
security levels have been upgraded. Please send the Hexpress 2.3 license file at
license@numeca.be for an upgrade of the license file.

4-2

Installation of Node-locked License

Node-locked licenses are dedicated to a given computer. They allow access to the software components
only from the dedicated computer. At the end of installation on the dedicated computer, the license information (HostName and HostID of this machine) must be sent at license@numeca.be. Once the license key is
generated, it must:
1.

Be renamed as license.dat

2.

Be copied into NUMECA_INSTALLATION_DIRECTORY/COMMON

3.

Have read-execute access privileges (execute chmod 755 license.dat).

INSTALLATION NOTE

4-1

License Management

Installation of Floating License

The license.dat file must be readable by every user.

4-3

Installation of Floating License

With a floating license, each software component is managed by an independent maximum number of concurrent accesses (number of processes). Floating licenses are managed by a license server. The license
server runs a license daemon that checks if process access is free. If so, when launching a software component, license access is given to the user process or access is denied otherwise.
The license can be accessed on the same computer but also on any other computer (client), with UNIX,
LINUX or Windows, connected to the license server. The license server can be a UNIX, LINUX or Windows machine. To install a floating license:

on a UNIX or LINUX license server: see section 4-3.1.

on a UNIX or LINUX client: see section 4-3.2.
If a NUMECA license service is already active consult section 4-4 to replace the license file.

4-3.1

Floating License on UNIX/LINUX License Server

NUMECA software must be installed on the license server (see Chapter 3 for software installation). At the
end of the installation, the license information (the HostName and HostID of this computer) must be sent
at license@numeca.be.

4-3.1.1 Configuration of License Service

To install the license service take the following steps:
1.

Rename the license file as license.dat

2.

Copy the license.dat file in the directory NUMECA_INSTALLATION_DIRECTORY/COMMON

3.

Check that the license file has the read-execute access privileges (execute chmod 755 license.dat)
The license.dat file must be readable by every user.

4-3.1.2 Starting License Service

Before using NUMECA software, the license daemon should be started on the license server. This can be
done manually or automatically.

a) Manual Start of License Service

To start the license daemon manually, do the following operations:
1.

Go to the directory NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/OSname/install/

2.

Execute the command:

./lmgrd -c NUMECA_INSTALLATION_DIRECTORY/COMMON/license.dat

In these lines, NUMECA_INSTALLATION_DIRECTORY should be replaced by the absolute directory

path where you have installed NUMECA software, while OSname should be replaced by LINUX.
The manual start operations must be repeated each time the server machine is
rebooted.

4-2

INSTALLATION NOTE

Update of License File

License Management

b) Automatic Start of License Service

The license daemon can be automatically started during the workstation boot process. To do so:
1.

Login as "root"

2.

Go to the /etc directory

3.

Edit the inittab file

4.

Add the following line at the end:

lmgr:35:wait:/
NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/OSname/install/lmgrd -c
NUMECA_INSTALLATION_DIRECTORY/COMMON/license.dat

In this line, NUMECA_INSTALLATION_DIRECTORY should be replaced by the absolute directory

path where you have installed NUMECA software, while OSname should be replaced by LINUX.

4-3.1.3 Verification of License Service Status

To verify that the license server is correctly running do the following:
1.

Go to the directory NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/OSname/install/

2.

Execute the command:

./lmutil lmstat -c NUMECA_INSTALLATION_DIRECTORY/COMMON/license.dat

If the license server is up this will be shown in the shell with the words: "license server UP (MASTER)
v9.2". The vendor daemon numeca needs to be up as well as indicated with the words: "Vendor daemon
status (on license_server_machine_name): numeca: UP v9.2. If the license server or vendor daemon is not
up see Chapter 5.
To display the active users of a given feature, use the following command:
./lmutil lmstat -a -c NUMECA_INSTALLATION_DIRECTORY/COMMON/license.dat

4-3.2

Floating License on UNIX or LINUX Client

When a floating license is installed on a UNIX, LINUX or Windows license server, this license may be
used by other computers with a network connection to the license server. In this section, it is assumed that
the license server is running. On each UNIX or LINUX client, the user should install NUMECA software
and copy the license key file license.dat of the license server in the directory
NUMECA_INSTALLATION_DIRECTORY/COMMON.
Users willing to launch NUMECA software on a client should perform a user configuration on this
machine before first use as described in Chapter 5.

4-4

Update of License File

When a license file is expired, contact NUMECA at license@numeca.be to obtain a updated license file.
Rename this license file as license.dat and follow the instructions in the sections below depending on the
license type.

INSTALLATION NOTE

4-3

License Management

4-4.1

Dedicated License for CATPart Files Import

Update of Node-locked License

Rename
the
updated
license
as
license.dat
and
copy
it
in
the
directory
NUMECA_INSTALLATION_DIRECTORY/COMMON, thus overwriting the old license.dat file. Ensure
that read-execute access permission are adequately set on the new license file.

4-4.2

Update of Floating License

To replace a floating license on the license server, do the following operations on the server machine:
1.

Copy the new file license.dat in the directory NUMECA_INSTALLATION_DIRECTORY/COMMON/

It is strongly suggested to make a backup of the old license file, for safety, by renaming
it to license.old.

2.

Go to the directory NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/OSname/install/

where OSname is the OS corresponding to the server machine (LINUX).

3.

Execute the command:

./lmutil lmreread -c NUMECA_INSTALLATION_DIRECTORY/COMMON/license.dat

To replace a floating license on the clients using the license server, simply replace the license.dat in the
directory NUMECA_INSTALLATION_DIRECTORY/COMMON, for each NUMECA software.

4-5

Dedicated License for CATPart Files Import

Hexpress includes a dedicated option enabling a direct importation of CATPart files, as generated by
CATIA v5.
This option is however subjected to a separate license. It is generated by TTF NUMECA partner and is
available on SGI, HP11, IBM AIX 4.3, LINUX and WINDOWS platforms (all platforms running 32-bits
architecture exclusively). Both node-locked and floating dedicated license file for importation of CATPart
files can be obtained, under the constraint that licenses generated on WINDOWS are in the form of a hardkey.

4-5.1

How to Get Dedicated License ?

The dedicated license file can be requested to NUMECA (generic address license@numeca.be). The following information must accompany the demand:

the platform of preference for installation of the dedicated license,

the type of license (node-locked, floating) with related HostID.

4-5.2

How to Install Dedicated License ?

The dedicated license file, named as "license_import.dat",

NUMECA_INSTALLATION_DIRECTORY/COMMON.

must

be

located

in

In case a floating license has been requested, it is necessary to perform the additional operations:

create a file named "ttf_server_information.dat". The file must include the two following lines and must
be stored in NUMECA_INSTALLATION_DIRECTORY/COMMON.
SERVER server_name
where server_name is the name of the server
PORT 10500

4-4

INSTALLATION NOTE

Dedicated License for CATPart Files Import

License Management

start the license server. This can be achieved through the execution of the command line
./ttfstartsrv NUMECA_INSTALLATION_DIRECTORY/COMMON/license_import.dat 10500 logfile ./LOG_FILE from the directory NUMECA_INSTALLATION_DIRECTORY/COMMON/
hexpress25_4/OSname/install/ttf

4-5.3

How to Update License ?

stop the license server. This can be achieved through the execution of the command line
./ttfstopsrv 10500 from the directory NUMECA_INSTALLATION_DIRECTORY/COMMON/
hexpress25_4/OSname/install/ttf
where 10500 is actually the port number (should be consistent with the port number
specified when launching the server.
replace the license file in NUMECA_INSTALLATION_DIRECTORY/COMMON (UNIX) or
NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/flexlm/ (Windows).

start the license server. This can be achieved through the execution of the command line
./ttfstartsrv NUMECA_INSTALLATION_DIRECTORY/COMMON/license_import.dat 10500 logfile ./LOG_FILE from the directory NUMECA_INSTALLATION_DIRECTORY/COMMON/
hexpress25_4/OSname/install/ttf

INSTALLATION NOTE

4-5

License Management

4-6

Dedicated License for CATPart Files Import

INSTALLATION NOTE

CHAPTER 5:

5-1

User Configuration

Overview

At the end of the installation, each user willing to use NUMECA software must initially configure his/her
working environment by running an initialisation script. In the following:

Section 5.2 describes how to configure the user environment.

Section 5.3 describes how to launch the software.

5-2

User Configuration

Each user is then allowed to configure his/her working environment as follows:

1.

Login as user.

2.

Go to the directory NUMECA_INSTALLATION_DIRECTORY/COMMON, and issue the command

./configure. This operation will add a couple of lines in the users .cshrc or .profile file (located in
users home directory) and add the NUMECA software in users default path.

3.

Log out and login again to apply the information in the .cshrc or .profile file.

5-3

Software Launch

Hexpress 2.5-4 can be started through the commands hexpress25_4 in the shell window.
In a multi-version environment, access to Hexpress 2.3-1 is allowed through the command
hexpress23_1. Do however notice that valid links towards Hexpress 2.5-4 must apply during the installation process.

INSTALLATION NOTE

5-1

User Configuration

Software Launch

It is important to outline that no output is displayed by default in Hexpress 2.5-4 shells, in order to avoid
unnecessary cluttering. The output is better redirected to a log file, located in the directory ~/.numeca/tmp/
and named as startup_logfile_hexpress.
However, outputs can still be forced for display in the shells. To this end, the -print command should
append to the command line as for example hexpress25_4 -print. This will give additional information during software launch, especially during the initial configuration of the software.
In case of troubles when starting the software, please send these files (if present) to NUMECA support
(support@numeca.be) with a short description of the problem.

5-2

INSTALLATION NOTE

CHAPTER 6:

6-1

Uninstallation

Overview

This chapter details the steps required to properly remove an installation of NUMECA software. Depending upon the configuration, several possibilities are offered:

Providing Hexpress 2.5-4 is installed in a mono-version environment (only Hexpress 2.5-4 is

installed), the uninstallation process can be performed as described in section 6-2.

Providing Hexpress 2.5-4 is installed in a multi-version environment, a partial or complete uninstallation can be performed:

to remove part of Hexpress environment, see section 6-3.

to remove the complete Hexpress environment, see section 6-4.
No further action is requested to uninstall a node-locked license. In case of floating license, the license
service may be stopped if NUMECA software is not used on any machine connected to the license server
(see section 6-5).

6-2

Uninstall Hexpress 2.5 (Mono-Version Environment)

Proceed as follows to remove Hexpress 2.5-4 in a mono-version environment under UNIX or LINUX:
1.

Verify that there are no running tasks on the machine.

In case of floating license, the license service should be stopped before uninstalling NUMECA
software. More details in section 6-5.

2.

Remove the lines from "#begin NUMECA configuration" to "#end NUMECA configuration" from the
users .cshrc or .profile file.

3.

Remove the directory NUMECA_INSTALLATION_DIRECTORY and its contents.

INSTALLATION NOTE

6-1

Uninstallation

6-3

Uninstall Hexpress Partly (Multi-Version Environment)

Uninstall Hexpress Partly (Multi-Version Environment)

Proceed as follows to remove Hexpress 2.5-4 or Hexpress 2.3 (but not both) in a multi-version environment under UNIX or LINUX:
1.

Verify that there are no running tasks on the machine.

In case of floating license, the license service should be stopped before uninstalling NUMECA
software. More details in section 6-5.

2.

Check that an active and valid license file is present for Hexpress 2.5-4 or Hexpress 2.3 (depending
upon the version the user wants to keep installed). The license file must be installed in the directory
NUMECA_INSTALLATION_DIRECTORY/COMMON/.

3.

Remove the directory NUMECA_INSTALLATION_DIRECTORY/hexpress# (where # refers to the

version to uninstall, either 23_1 or 25_4) and all of its contents.

6-4

Uninstall Hexpress Fully (Multi-Version Environment)

Proceed as follows to remove Hexpress 2.5-4 and Hexpress 2.3 in a multi-version environment under
UNIX or LINUX:
1.

Verify that there are no running tasks on the machine.

In case of floating license, the license service should be stopped before uninstalling NUMECA
software. More details in section 6-5.

2.

Remove the lines from "#begin NUMECA configuration" to "#end NUMECA configuration" from the
users .cshrc or .profile file.

3.

Remove the directory NUMECA_INSTALLATION_DIRECTORY and all of its contents.

6-5

Uninstall License Service

No action is requested to uninstall a node-locked license.

In case of floating license, the license service should be stopped before uninstalling NUMECA software. To
do so, the following operations must be performed:
1.

Go to the directory NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/OSname/install

2.

Execute the command:

./lmutil lmdown -c NUMECA_INSTALLATION_DIRECTORY/COMMON/license.dat
Instructions related to NUMECA license service must be removed providing the
machine has been configured to start automatically the license service at start up. These
instructions can be accessed in /etc/initab file.

6-2

INSTALLATION NOTE

CHAPTER 7:

7-1

Troubleshooting

Introduction

In most cases, a straightforward and careful execution of the instructions detailed in the previous chapters
enables the user to start Hexpress 2.5-4 smoothly. In case of problems, this chapter aims at providing
guidelines on how to detect and solve possible troubleshootings. If the problems still persist, please contact and provide NUMECA support team with the following information:

the license key file license.dat.

the hostname and hostid. These information can be obtained by executing the commands lmutil
lmhostid
-hostname
<Enter>
and
lmutil
lmhostid
<Enter>
in
the
NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/OSname/install
directory,
where
"OSname" refers to the operating system selected.

the Hexpress version for which installation is causing problems.

a description of the configuration (in terms of name, platform and OS for each machine on which
NUMECA software is installed).

the .log file generated during the installation and located in the /tmp directory on the machine from
where the script ./install_hexa has been launched (as described in section 3-2, step 5).

the "startup_logfile_*" files located in ~\.numeca\tmp

7-2

Hexpress Not Starting

In case Hexpress does not start, use the -print argument in the command line as: hexpress25_4 -print.
This argument will output information in the shell (including the location of the license file) which may
be helpful to understand the problem. With this information at hand, check the following items:

Is the license file valid and active to start Hexpress ?

Check if the license key, named as license.dat,

is adequately
NUMECA_INSTALLATION_DIRECTORY/COMMON directory

INSTALLATION NOTE

copied

into

the

7-1

Troubleshooting

Graphical Problems & System Crashes

In case of floating licenses, check if the license server is up. On the license server, two active daemons
should be present. This can be seen using the commands ps -ealf | grep lmgrd and ps -ealf | grep
numeca. If not, follow the instructions for license installation.

In case of floating licenses, some license check problems may occur if the host computer cannot find
the server IP-address corresponding to the hostname information included in the first line of the
license key. To solve this problem, replace the hostname by the IP-address of the license server. This
operation does not invalidate the license key.

Check if the license key file is well readable by every user.

Did the user configure his/her working environment? Before using NUMECA software, each user
must configure his/her working environment using the command ./configure within the
NUMECA_INSTALLATION_DIRECTORY/COMMON directory; then log out and log in.

Is the graphics driver appropriate for the display ? Try to activate the X11 driver as follows:
in csh, tcsh or bash shell:
setenv NI_DRIVER X11
in korn shell:
NI_DRIVER=X11
export NI_DRIVER
If this solves the problem, it means that OPENGL driver is at the source of the problem. If so, make the
change to X11 permanent by editing the file ~/.numeca/.drivers and specifying the driver in the
chosen_driver colon (last colon).

Check if the TCP/IP protocol is installed on the machine. The protocol is mandatory to ensure the correct function of the floating licenses.

Are the NUMECA software components visible from the machine? If not, install them.
Is the OS adequate? If not, copy the correct tar file and start the installation again.
Are Unix permission sufficient for the user to access NUMECA software installed? Ask for the system administrator.
Please send the file ~/.numeca/tmp/startup_logfile_hexpress to NUMECA support team if problems still
persist.

7-3

Graphical Problems & System Crashes

Hexpress makes use of the advantages of Graphics Card available. Some trouble may however come
up with the default driver OPENGL since it may not be supported by the user host computer and machine
display.
In order to set the system compatible with a more portable driver, refer to the following instructions. Note
however that the proposed drivers are usually less efficient in terms of graphical speed than the default
driver. The driver can be manually specified through the following commands:
for csh, tcsh or bash shells:
setenv NI_DRIVER X11
for korn shells:
NI_DRIVER=X11

7-2

INSTALLATION NOTE

Hexpress Screen Flashes

Troubleshooting

export NI_DRIVER
Ultimately, the user can force a specific driver by editing the file ~/.numeca/.drivers. The driver can then be
specified in the chosen_driver colon (last colon).

7-4

Hexpress Screen Flashes

In some circumstances, the graphical area can flash during interactive operations, depending upon the
driver selected. This mostly happens when using the X11 driver. Setting the environment variable
NI_DOUBLEBUFFERING to ON into the user profile (.cshrc, .profile, .tcshrc,...) may solve the problem
under UNIX or LINUX. The variable can be manually specified through the following commands:
for csh, tcsh or bash shells:
setenv NI_DOUBLEBUFFERING ON
for korn shells:
NI_DOUBLEBUFFERING=ON
export NI_DOUBLEBUFFERING

7-5

Hexpress Drivers Not Detected

Hexpress checks the available working drivers and updates automatically the .drivers file located in
users .numeca directory at first launch on a new machine/display. This operation is only completed during
the first execution, since it may take some time. As a consequence, the upgrade of drivers on an existing
machine/display cannot be automatically detected by Hexpress.

INSTALLATION NOTE

7-3

Troubleshooting

7-4

Hexpress Drivers Not Detected

INSTALLATION NOTE