FINEOpen Installation

INSTALLATION NOTE
FINE™/Open with OpenLabs™ 7.2
www.numeca.com
CONTENTS
CHAPTER 1. SYSTEM REQUIREMENTS
1.1 Windows 4
1.1.1 Supported platforms and operating systems 4
1.1.2 Multiprocessors calculations 5
1.1.3 Hardware requirements 5
1.1.4 Memory and disk space requirements 5
1.1.5 Graphics requirements 7
1.1.6 Compilation requirements for OpenLabs™ 7
1.2 Linux 8
1.2.1 Supported platforms and operating systems 8
1.2.2 Multiprocessors calculations 9
1.2.3 Hardware requirements 9
1.2.4 Memory and disk space requirements 10
1.2.5 Graphics requirements 11
1.2.6 Compilation requirements for OpenLabs™ 12
CHAPTER 2. INSTALLATION
2.1 Windows 14
2.1.1 Installation 14
2.1.2 License management 17
2.1.3 User Configuration 23
A. Optional user configuration 23
B. Software launch 26
2.1.4 Uninstallation 27
2.1.5 Troubleshooting 31
2.2 Linux 34
2.2.1 Installation 35
2.2.2 License management 38
2.2.3 User Configuration 44
2.2.4 Uninstallation 47
2.2.5 Troubleshooting 50
2 FINE™/Open with OpenLabs™ 7.2 Installation note

CHAPTER 1.
SYSTEM REQUIREMENTS
For proper installation and use of FINE™/Open with OpenLabs™ please consult the following
sections detailing the system requirements for your operating system.
In this section
1.1 Windows 4
1.2 Linux 8

1.1 WINDOWS
1.1.1 Supported platforms and operating systems
NUMECA software is supported in 64 bits on x86_64 processors only (64 bits processors that are
compatible with Intel 8086 set of instructions).
Formally tested on Also known to run ona

Windows 7 Professional -
Windows 8.1 Professional -
Windows 10 Professional -
Windows HPC 2012
- VISTA Business
- VISTA Ultimate
- Windows Server 2008 b
- Windows Server 2012 b
a. Known from partners and/ or customers. No official support offered on these combinations.
b. Not for HEXPRESS™/Hybrid.
Please also notice that the following limitations apply:
l Computations under Windows (except Windows Server) are limited to one PVM daemon
running at a time. As a consequence, access to multiple users on a given machine is not
allowed,
l Parasolid uses SSE2 instruction for high performance. If your platform is not supporting the
SSE2 instruction, the FINE™ GUI cannot be started.
Your platform of preference is not in the list?
Contact NUMECA local sales or support office. NUMECA software does however explicitly not
run on the following configurations:
l Power PC based systems,
l WINDOWS 2000 server workstations,
l WINDOWS 95, 98 or ME workstations.

1.1.2 Multiprocessors calculations
Multiprocessors calculations are allowed on shared and homogeneous distributed platforms. Non-
homogeneous configurations are not allowed.
The following limitations additionally apply:
l Multiprocessors calculations are allowed on distributed platforms in local user configurations
provided that the same account is used for all machines,
l Domain administrators are not allowed to run multiprocessors calculations.
l MPICH2 library needs Microsoft .net Framework package before installing NUMECA
software otherwise execution of mpiexec.exe will lead to a Windows error message.
1.1.3 Hardware requirements
Next to the standard hardware (monitor, keyboard and mouse), some specific recommendations
apply in the use of NUMECA software:
l a mouse with scroll wheel is strongly recommended.
l the monitor should support 24-bit color graphics and have a 1280 x 1024 pixel resolution for
adequate visualization.
l an Ethernet card should be installed and properly configured.
l NUMECA Software does not support CXFS (Clustered XFS) and IBRIX disk file systems.
1.1.4 Memory and disk space requirements
The Random Access Memory (RAM) required to run NUMECA software depends upon several
factors, in particular including the number of grid points inserted in the grid, the physical models
selected (turbulence, adaptation,...), the introduction of non-matching boundary conditions and the
selected calculation mode (mixed or double precision).
Similarly, a minimum disk space is required on the hard disk to allow the storage of the project
files. The size of these files largely depends upon the number of grid points generated.
More product specific details:
HEXPRESS™
The use of minimum 1 GB RAM is strongly recommended. As a general guideline, about 0.5 to

0.7 GB RAM are required to run a one million nodes project. The suggested swap space should
be equivalent to at least 3 times the RAM installed.
As a general guideline, a minimum of 300 MB is required to store the project files (provided that
the geometry is not defined by Parasolid™ or CATIA v5 files) for a one million nodes project.
HEXPRESS™/Hybrid
The Random Access Memory (RAM) required to run HEXPRESS™/Hybrid depends upon
several factors. In particular, the complexity of geometries and the settings of the CONF file. As a
general guideline, the Random Access Memory (RAM) required to run HEXPRESS™/Hybrid
are:
l for mesh without viscous layers - between 500 MB and 700 MB RAM per million of cells
l for mesh with viscous layers - between 700 MB and 900 MB RAM per million of cells
The use of minimum 4 GB RAM is mandatory, but the installation of 8 GB is recommended. The
suggested swap space should be equivalent to at least three times the RAM installed.
About 1 GB is required to store a two-millions nodes mesh in SPH format.
FINE™/Open with OpenLabs™
The use of minimum 1 GB RAM is mandatory, but the installation of 2 GB is recommended. As

a general guideline, about 1.5 GB RAM is generally required to run a one million nodes project in
double precision mode. The suggested swap space should be equivalent to at least 3 times the
RAM installed.
Mesh partitioning for parallel computations requires about 1 GB memory per million cells. When
using serial partitioner, the user must ensure that the memory on the head node is sufficient,
because the partitioning is performed only on the head node in case of serial partitioning.
As a general guideline, a minimum 1.4 GB is required to store the mesh and solution files (one
file, no full non-matching connections, solution stored after one iteration) when running a one
million nodes project.
CFView™
The use of minimum 1 GB RAM is strongly recommended. As a general guideline, about 250
MB RAM are required to visualize a one million nodes project. The suggested swap space should
No specific disk space is required on the hard disk for CFView™ except if images or data files
are saved or if the meridional average is created in CFView™ (turbomachinery application).

NTFS file system is recommended for installation and working directories under Windows.
1.1.5 Graphics requirements
NVidia graphics cards are fully supported, installed together with the latest drivers.
NUMECA software 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 MSW driver is used under Windows instead. Note however that the proposed
drivers are usually less efficient in terms of graphical speed than the default driver.
To change the used driver
1. Log in as administrator.
2. Launch regedit from the Start/Run menu.
3. Go to the HKEY_LOCAL_MACHINE/SOFTWARE/NUMECA International register.
4. Go into the folder of the package for which to modify the driver, e.g.: Fine# where # is the
version number.
5. Modify the DRIVER entry to either OPENGL or MSW.
The selection will take effect at the next session.
1.1.6 Compilation requirements for OpenLabs™
Customization of the CFD models using OpenLabs™ requires the possibility for compilation.
On Windows 64 bit, Microsoft Visual C++ Build Tools 2015 must be installed: make sure to
select the component Windows 10 SDK 10.0.10240 during the installation.

1.2 LINUX
1.2.1 Supported platforms and operating systems
NUMECA software is supported in 64 bits on x86_64 processors only (64 bits processors that are
compatible with Intel 8086 set of instructions).
Formally tested on Also known to run ona

Fedora Core 22.x, 25.x -
(K)Ubuntu 14.04bcd, 16.04bcd -
CentOS 7.0.1406 -
- SuSe 10.1, 10.2, 11.0
- Enterprise 3.x, 4.x, 5.x
- Fedora Core 5.x, 7.x, 8.x, 12.x, 17.x, 18.x, 20.x
- (K)Ubuntub 7.x, 8.x, 9.x, 10.x, 11.xc, 12.xc, 13.xc
a. Known from partners and/ or customers. No official support offered on these combinations.
b. Debian based operating systems like Ubuntu, even if LSB compliant, are not recommended as a license
server as it is known to diverge occasionally from the LSB standard.
c. For HEXPRESS™/Hybrid pay attention to the changed NVIDIA driver location. It is necessary to specify its
location defining the environment variable LD_LIBRARY_PATH to /usr/lib/nvidia-current/.
d. The OpenLabs™ module cannot be compiled with C++ compiler g++ 4.7.3.
FlexLM requires LSB (Linux Standard Base) compliance. The list of Linux distributions and
applications certified for compliance with the LSB standard is available on
http://www.linuxfoundation.org/lsb-cert/productdir.php?by_lsb.
When launching NUMECA software, if an error message appears when loading shared libraries,
contact NUMECA local sales or support office.
Your platform of preference is not in the list?
Contact NUMECA local sales or support office. NUMECA Software does however explicitly
not run on the following configurations:

l x86_64 processors running Linux SuSe 10.3,
l IBM PowerPC running Linux.
Optimal use of an Infiniband connection
The default Open MPI version provided in the package does not support Infiniband usage. An
Open MPI library specific to the machine(s) is required.
Use an External OpenMPI Library on Linux
1.2.2 Multiprocessors calculations
Multiprocessors calculations are allowed on shared and homogeneous distributed platforms. Non-
homogeneous configurations are not allowed.
1.2.3 Hardware requirements
Next to the standard hardware (monitor, keyboard and mouse), some specific recommendations
apply in the use of NUMECA software:
l a mouse with scroll wheel is strongly recommended.
l the monitor should support 24-bit color graphics and have a 1280 x 1024 pixel resolution for
adequate visualization.
l an Ethernet card should be installed and properly configured.
Specific to HEXPRESS™/Hybrid
l HEXPRESS™/Hybrid makes direct use of OpenGL libraries. These libraries must thus be up-
to-date, properly installed and configured before HEXPRESS™/Hybrid can be started.
l Tests have only been performed on NVIDIA graphical cards.
HEXPRESS™/View is not supported with the integrated graphics card that comes with Intel i7
processors machines. In such cases users need to modify the default settings. For example, if the
NVIDIA graphics card is available on the machine:

1. Go to the NVIDIA control panel/Manage 3D settings,
2. and select High- performance NVIDIA processor from the drop- down menu under Preferred
graphics processor.
1.2.4 Memory and disk space requirements
The Random Access Memory (RAM) required to run NUMECA software depends upon several
factors, in particular including the number of grid points inserted in the grid, the physical models
selected (turbulence, adaptation,...), the introduction of non-matching boundary conditions and the
selected calculation mode (mixed or double precision).
Similarly, a minimum disk space is required on the hard disk to allow the storage of the project
files. The size of these files largely depends upon the number of grid points generated.
HEXPRESS™
The use of minimum 1 GB RAM is strongly recommended. As a general guideline, about 0.5 to
0.7 GB RAM are required to run a one million nodes project. The suggested swap space should
As a general guideline, a minimum of 300 MB is required to store the project files (provided that
the geometry is not defined by Parasolid™ or CATIA v5 files) for a one million nodes project.
HEXPRESS™/Hybrid
The Random Access Memory (RAM) required to run HEXPRESS™/Hybrid depends upon
several factors. In particular, the complexity of geometries and the settings of the CONF file. As a
general guideline, the Random Access Memory (RAM) required to run HEXPRESS™/Hybrid
are:
l for mesh without viscous layers - between 500 MB and 700 MB RAM per million of cells
l for mesh with viscous layers - between 700 MB and 900 MB RAM per million of cells
The use of minimum 4 GB RAM is mandatory, but the installation of 8 GB is recommended. The
suggested swap space should be equivalent to at least three times the RAM installed.
About 1 GB is required to store a two-millions nodes mesh in SPH format.
FINE™/Open with OpenLabs™
The use of minimum 1 GB RAM is mandatory, but the installation of 2 GB is recommended. As

a general guideline, about 1.5 GB RAM is generally required to run a one million nodes project in
double precision mode. The suggested swap space should be equivalent to at least 3 times the
RAM installed.
Mesh partitioning for parallel computations requires about 1 GB memory per million cells. When
using serial partitioner, the user must ensure that the memory on the head node is sufficient,
because the partitioning is performed only on the head node in case of serial partitioning.
As a general guideline, a minimum 1.4 GB is required to store the mesh and solution files (one
file, no full non-matching connections, solution stored after one iteration) when running a one
million nodes project.
CFView™
The use of minimum 1 GB RAM is strongly recommended. As a general guideline, about 250
MB RAM are required to visualize a one million nodes project. The suggested swap space should
No specific disk space is required on the hard disk for CFView™ except if images or data files
are saved or if the meridional average is created in CFView™ (turbomachinery application).
1.2.5 Graphics requirements
NUMECA software makes use of the advantages of the available Graphics Card. By default, the
driver OPENGL is used.
In case a problem appears with the default driver OPENGL, the user should change to the X11 driver
under Linux. Note however that the X11 driver is usually less efficient in terms of graphical speed
than the default driver.
The drivers OPENGL and OPENGL2 may not work when using VNC or remote access by
"ssh". In case of problems, the X11 driver should be used.
To change the driver permanently for every next launch of the software:

1. Open the file ~\.numeca\.drivers
2. Type: host_name display_name possible_drivers chosen_driver e.g. gauss.numeca.be gauss
OPENGL:X11 X11
Alternatively, the driver can be manually specified in a shell for that shell session only through the
following commands:
l in csh or tcsh shell:
setenv NI_DRIVER X11
l in bash or korn shell:
NI_DRIVER=X11 export NI_DRIVER
1.2.6 Compilation requirements for OpenLabs™
Customization of the CFD models using OpenLabs™ requires the possibility for compilation:
On Linux 64 bit, the GNU C and C++ compiler (g++) must be installed. The gcc version should
be between 4.8.# and 5.3.# (type the command gcc -v in a shell to get your gcc version). The
officially tested version is g++ 4.8.5.

CHAPTER 2.
INSTALLATION
Prior to installation it is important to consult first the "System requirements" (p. 3).
2.1 Windows 14
2.2 Linux 34

2.1 WINDOWS
The user is strongly advised to consult the "Windows" (p. 4) system requirements prior to the
installation. Problems may indeed appear during the installation and configuration phases in case
the listed hardware and software requirements would not be fully satisfied.
Please do notice that the documentation package attached to NUMECA software is not installed
during the installation procedure and can be downloaded from the Products page of the Customer
Area of www.numeca.be.
In case of trouble: see "Troubleshooting" (p. 31).

For more information and troubleshooting:
l consult the forum in NUMECA's Customer Area with a section dedicated to installation.
l or contact NUMECA local sales or support office (for active maintenance plans only).
To help to find a solution within the shortest delays, please provide a detailed description of the
observed behavior and performed analysis.
At the end of the "Troubleshooting" (p. 31) the information to provide is listed.
2.1.1 Installation
Install FINE™/Open with OpenLabs™ under Windows
1. Log in as administrator or as a user with administrator privileges on the machine. If the user
does not have administrator privileges, the NUMECA software installation will not be
performed successfully.
2. Check and make sure that the necessary disk space is available prior to starting the installation
process.
For the disk space requirements, see also: "Windows" (p. 4) system requirements.
3. Get the installation package from the Products page of the Customer Area (www.numeca.be).
4. Unzip the installation package.
5. Exit all the other active applications and launch the setup.exe executable.
6. During the installation, the user will be asked to accept the terms of the License Agreement.
7. Enter the installation directory (referred to as NUMECA_INSTALLATION_DIRECTORY)

in function of one of the following scenarios:
l If NUMECA software was not installed before on the machine, choose a directory of your
preference. Providing a directory name that does not exist will create it automatically.
l If NUMECA software was already installed before, choose the same NUMECA_
INSTALLATION_DIRECTORY to use the multiple versions and/ or products in one
multi-version environment.
It is important to notice that a common NUMECA_INSTALLATION_DIRECTORY

should be shared by all NUMECA installations (e.g. C:\numeca_software\), otherwise
the multi-version installation will not be set up adequately. This is important e.g. for the
good functioning of PVM when launching several products or versions one after the
other.
8. At the end of the installation process, instructions to obtain information required for license
generation will be prompted. To this end, the following steps must be performed:
a. Click on Yes.
b. The license information is stored in the file license.info located in NUMECA_
INSTALLATION_DIRECTORY automatically. Once it is saved, send this text file to
NUMECA local sales or support office.
Alternatives to get the license information
The information can also be obtained using the NUMECA Administration Tool (Launching at
the end of the installation process (step 8) or from Start/Programs/NUMECA
software/<product_name>/Administration Tool menu) or recovered as Ethernet Address
by clicking on the System Settings tab after launching lmtools.exe located in the directory
NUMECA_INSTALLATION_DIRECTORY\<product_name>\flexlm.
9. After the package is installed, the NUMECA Administration Tool is launched automatically.
This is a tool for license management and provides a graphical user interface for the
management of the license server and client machines. The tool offers a guide through the
process of setting up and configuring a license server.
Alternatives to access the Administration Tool
After installation, the Administration Tool can also be started from

Start/Programs/NUMECA software/<product_name>/Administration Tool menu. Click
on Finish to leave the tool and to finalize the installation.

Tasks that can be performed in the NUMECA Administration Tool
l License Management: to configure the machine as license server and/ or client.

l User Configuration: to set user MPI configuration.
l Diagnostics: to assess and fix problems with license management, graphics, Windows
registry and parallel configuration.
l Network Configuration: to clean and reinitialize PVM, to setup RSH connections to other
machines/ users.
10. When receiving the license file from NUMECA, perform the license installation and user
configuration:
l "License management" (p. 17)
l "User Configuration" (p. 23)
During an installation and license specification, the administrator must launch the software once to
properly initialize flexlm.
In case of installation problems, right-click on setup.exe , select the option Run as... and then either
run as the true Windows Administrator account, or if and only if the user account with Administrator
privileges, run as user, but remove the option to run the program with restricted access. On
WINDOWS 7 it may also be necessary to disable the User Account Control feature (UAC) at least
during the installation process and the configuration steps.
In order to run distributed memory parallel computations, NUMECA software must be installed in the
same directory on different machines.
Install HEXPRESS™ v7.2 standalone
The installation of FINE™/Open with OpenLabs™ v7.2 includes HEXPRESS™ v7.2.

The latest release of HEXPRESS™ standalone v7.2 can be downloaded from the Products page
of the Customer Area (www.numeca.be ) and used in combination with FINE™/Open with
OpenLabs™ v7.2. This standalone version contains significant improvements:
New Features in v7 of HEXPRESS™
New Features in v7 of HEXPRESS™/Hybrid

2.1.2 License management
Introduction
Before using NUMECA software, a valid floating license is required.
What is a 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 which 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 other computers (clients) with Linux or Windows, connected
through a network to the license server. The license server can be a Linux or a Windows
machine.
l NUMECA updates the security ID of license files with each major release. License files
with old security ID cannot be used with the latest NUMECA software. Please send your
old license file to NUMECA local sales or support office for an upgrade of the license file.
l Redundant license server can be delivered allowing to manage a floating license by several
servers. For more information, contact NUMECA local sales or support office.
l Machines used as license server must have a fixed first IP address. For example, when
using VPN on Windows, VPN will become the first network interface. In this case, the
license server will not work properly.
l By default it is not possible to use a virtual machine as a license server. To install a license
server on a virtual machine, contact your account manager.
l Running Windows 64-bits, an additional Windows security patch is required to enable
CATIA v5 import with Datakit. For more details, link to the Microsoft official website.
NUMECA software must be installed on the license server. At the end of the installation, the
license information (the HostName and HostID of this computer) must be sent to NUMECA local
sales or support office in order to get a license file.
Before using NUMECA software, the license daemon should be configured on the license server.
See also: "Installation" (p. 14)
To set up the license server it is necessary to prepare the license file and launch the server either
though the NUMECA Administration Tool or in LMTools.

Access to the NUMECA Administration Tool
At the end of the installation of NUMECA software the Administration Tool is launched
automatically.
It can also be started anytime from the Start/Programs/NUMECA software/<product_name>
menu: right-click on the Administration Wizard item and select Run as administrator.
It is required to run the Administration Tool as administrator for its proper functioning.
Prepare the license file
To install the license service:

1. Rename the license file as license.dat
2. Copy the license.dat file in the directory that all users are able to access.
3. Check that the license file has the read-execute access privileges:
l select the license file license.dat using Windows Explorer.
l while keeping the mouse on the selected file right-click and select from the appearing
menu: Properties. This will open a properties window.
l on the General page the Read-only box of the Attributes should not be selected. Unselect
this box if necessary.
l click on Apply and click on Close to close the window.
The "license.dat" file must be readable by every user.
When using a TCP port for the license server, the port number (check the free port with the
command: C:\\netsat -an) has to be added in the license file on the server/ vendor line:
1. SERVER hostname hostid and VENDOR numeca should be replaced by SERVER hostname
hostid portnumber1 and VENDOR numeca portnumber2;
2. reread the license file,
3. start NUMECA software and specify the license server writing portnumber@hostname . All
specified ports should be opened and free.

It is no more required to copy the license files on every client workstation if the variables NUMECA_
LICENSE_FILE defined as @license_server or port_number@license_server are added in the registry
database for each client. This allows to update the license file only on the license server.
License set-up in NUMECA Administration Tool v12
Start floating license service
To start the license service:

1. Select License Management.
2. On the line Activate from license file browse to the license file.
3. Click on Apply.
The manual start operations must be repeated each time the server machine is rebooted. Alternatively
it would be possible to define an automatic start of the license service from lmtools or using the
NUMECA Administration Tool.
Automatic start at machine boot
After the manual start of the license service, it is possible to have it automatically start at machine
boot:
1. In License management click on the Advanced button.
2. Go to the License server tab.
3. Press the Set autostart server button.
A Windows service called NUMECA License server is used.
Verify license service status
To verify that the license server is correctly running do the following:

1. From the NUMECA Administration Tool home page, click on License Management .
2. Click on the Advanced button at the bottom of the Activate Product tab.
3. Select the License server status tab.
4. Select the license server on the left-hand side drop down menu.

5. Information regarding the available features, the number of available licenses and the number
of used licenses is shown under the License server info section.
Update of license file
When a license file is expired, contact NUMECA local sales or support office to obtain an
updated license file.
Replace the active license file license.dat with the update license provided by NUMECA
(renamed as license.dat).
It is strongly suggested to make a backup of the old license file, for safety, by renaming it to
"license.old".
1. Go to the NUMECA Administration Tool home page, click on License Management .

3. Select the License server tab.
4. Click on the Re-read license button.
5. The words "SUCCEEDED" or "Failed" are shown depending on the update success or
failure, respectively.
If the version of the Flexlm tool is upgraded or the version of the license file security ID is
upgraded, an update of the license file is not sufficient. The user must shutdown the running
license server and start a new license server with the latest Flexlm tool and the latest license file.
Alternative: license set-up in lmtools
Start license service
1. In Windows Explorer, browse to the directory NUMECA_ INSTALLATION_

DIRECTORY/<product_name>/flexlm and double click on lmtools.exe.
2. On the Service/License File page select Configuration using Services.
3. Select the Config Services tab.
4. Enter for Service Name any name indicating that it is related to a NUMECA license (e.g.,
numeca_license).

5. To enter the Path to the lmgrd.exe file click on Browse right next to the text box and browse
to NUMECA_ INSTALLATION_ DIRECTORY/<product_ name>/flexlm and select
lmgrd.exe.
6. To enter the Path to the license file, click on Browse right next to the text box and browse to
the license file license.dat to select it (files of type from license files (".lic") to license files
(".dat")).
7. Enter HOME_DIRECTORY/.numeca/debug.log to access the path of debug log file. This
file is automatically created when starting the license service.
8. Click on Save Service.
9. Select Use Services and Start Server at Power Up. In this way the license service will be
automatically starting when booting under Windows.
10. To start the server now manually select the tab Start/Stop/Reread.
11. Select the NUMECA license service under Flexlm license Services installed on this
computer.
12. Click on Start Server.
If the license service was correctly started, numeca.exe and lmgrd.exe should be visible in the list
of processes or services in Windows Task Manager. If these executables are not running verify the
debug.log file.
See also: "Troubleshooting" (p. 31)
13. If NUMECA software is used on the license server, the user should first perform a user
configuration as described in the section "User Configuration" (p. 23).
14. Launch the software a first time.
15. Click on Specify the License Server.
16. Enter the name of the license server or its IP address.
17. Click on Finish.
Rename this license file to license.dat and follow the instructions below.

1. Replace the active license file license.dat with the update license provided by NUMECA
"license.old".
2. Go to the directory NUMECA_INSTALLATION_DIRECTORY/<product_name>/flexlm.

3. Start the LMTools by double clicking on lmtools.exe
4. Select the tab Start/Stop/Reread.
5. Select the NUMECA license service in the list and click on ReRead License File.
If the version of the Flexlm tool is upgraded or the version of the license file security ID is upgraded,
an update of the license file is not enough. The user must shutdown the running license server and
start a new license server with the latest Flexlm tool and the latest license file.

1. Open the Windows Task Manager.
2. Select the Processes or Services.
3. Check that the processes numeca.exe and lmgrd.exe are running.
or:
1. In Windows Explorer browse to the directory NUMECA_ INSTALLATION_
DIRECTORY/<product_name>/flexlm and double click on lmtools.exe.
2. Select Configuration using Services.
3. Select the tab Server Status.
4. Click on Perform Status Enquiry and wait to see the server status and the available features.
Floating license on Windows client
When a floating license is installed on a 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 Windows client, the user must:

1. Install NUMECA software.
2. Perform a user configuration on this machine before first use as described in the section "User
Configuration" (p. 23).
3. Click on Specify the License Server when first starting the software.
4. Enter the name of the license server or its IP address.
5. Click on Finish.
Optional: ask software to wait for license
To request that NUMECA products wait for an active license, define it in the "Home directory"
(p. 26) in .numeca/preferences.dat using the keyword LICENSE_WAIT. This functionality is
available for all products.
Example
PRODUCT FINE/Marine
LICENSE_WAIT
END_PRODUCT
Student version with activation ID
In general a license certificate (text file) is provided to give access to NUMECA software.
Alternatively the NUMECA Administration tool allows to use an activation ID to start the license
server. For example, the free student version is based on an activation ID and the instructions how
to use it are provided together with the activation ID. Use of an activation ID requires the use of
Trusted storage and installation of an anchor service. Hence this terminology can be found in the
NUMECA Administration Tool but can be safely ignored in case of a license certificate in text
file format.
Example of an Activation ID: C2a9-561f-7895-435b-acb5-3520-c166-4bcc
2.1.3 User Configuration
A. Optional user configuration
Without the optional steps in this section it is still possible to launch a simulation on one processor
on the local machine with a default location of the home directory.

Configure account to perform parallel computations
Provided that the parallel capabilities have been adequately installed and valid licenses can be
accessed, the user will be able to perform parallel computations. Launching a parallel
computation, the system will by default request the user login and password. Before the first
launch, the user can register his/ her name and password once and for all, by doing the following
steps:
1. Open a DOS shell,
2. Type the command NUMECA_ INSTALLATION_
SOFTWARE/fineopen72/bin64/mpiexec.exe -register<Enter>.
3. Enter the user login and password and confirm.
If the user does not register his/ her name and password before launching the parallel computation,
the FINE™ GUI will prompt the user to enter credentials (Windows login account) if needed.
Currently, it is not possible to launch the computation without the registering/ providing the user's
credentials. Thus, if no password has been defined during the registration, it will be necessary to set
the password on the machine in any case.
Domain administrators are not allowed to run parallel computations under Windows.
PVM does not support domain accounts.
Parallel computations under Windows (except Windows Server) are limited to one PVM daemon
running at a time on the machine. Consequently, access to multiple users on a given machine is not
allowed.
MPICH2 library needs Microsoft .net Framework package before installing NUMECA software.

When running parallel computations, the path to the project must be identical on both the local and
remote machines. For example, for distributed memory parallel computations, a folder must be
mounted on each machine and share the same drive name, in order to store the project directory that
will be run in parallel on multiple hosts.
Configure account to allow remote computations
It is possible to launch tasks on remote machines by using the Task Manager capabilities. To be
able to perform remote launches, NUMECA software must be installed and explicit permission
must be specified on the remote machine. To this end, the following operation must be checked
and/ or performed on the remote machine:
1. Open the Windows Control Panel window (Start/Settings/Control Panel).
2. Click on the Services icon under System and Security/Administrative tools.
3. Select from the list of services NUMECA RSH Daemon.
4. Click on Stop and leave the Services window open.
5. Edit the file rhosts.txt in the directory C:\WINDOWS on both the host and client machines.
This can be done through the FINE™/Admin tool. Launch it from All Programs-
>NUMECA software-><product_name>->Administration Wizard and select Configure
the TaskManager in this machine.
Alternatively edit the rhosts.txt file
Edit the text file and add the following line for each host user you want to give access
permission:
hostname username:
These lines typically give right to the user username, working on the machine hostname, to
connect to the machine containing the rhosts.txt file.
6. Select the NUMECA RSH Daemon from the list of services in the Services window.
7. Click on Start. Starting this service may take approximately 5 minutes.
Use of the Task Manager under Windows with a Linux host may lead the remote copy to option to
fail. See also: "Cannot connect to other hosts" (p. 33) in the Troubleshooting section for more detail
on this problem.

In addition to that, the firewall should also allow remote computations. To do so, follow the steps
below:
1. Add a Port inbound and outbound rule for a TCP protocol with the number 514. The
connection should be allowed for all type of profiles.
2. Allow the following programs to bypass the firewall inbound and outbound rules: smpd,
mpiexec, hexstream#x86_64 and hexstream#_impix86_64 (# stands for sp, hp and dp) located
in <NUMECA_INSTALLATION_DIRECTORY>\fineopen72\bin64; lib\win32\pvmd3.exe,
bin\rsh.exe, bin\rsh_ vista.exe and bin\win32\hoster.exe located in <NUMECA_
INSTALLATION_DIRECTORY>\pvm.
Home directory
On Windows, NUMECA software saves some data (preferences, user fluid database, ...) in the
folder %HOME%\.numeca\, or in the %HOMEDRIVE%%HOMEPATH%\.numeca\ folder in
case %HOME% is not defined. If the user wants to customize the path of the .numeca folder, the
user can redefine the system environment variable HOME.
Note:
l The variable HOME must be defined as a system environment variable.
l Defining HOME to a network disk may significantly slow down the NUMECA software
GUI.
During the runtime, NUMECA software writes temporary data in the directory
%HOME%\.numeca\tmp. This tmp directory can be redefined by defining the environment
variable TMP_DIR.
B. Software launch
After configuring, the product can be started from the Start\Programs\NUMECA

software\<product_name>\ menu.
It is not allowed to start NUMECA software under Windows as administrator in a user domain
environment. This limitation does not apply to user login.
In case the license has not been configured adequately at this stage of the installation process, it is still
possible to launch the product by selecting a license file (server) when prompted after first launch.

The UAC (User Account Control) should be disable for running the solver in parallel otherwise it
prevents mpiexec to record the encrypted login and password in the registry database and the Task
Manager remains open forever without any evolution.
NUMECA software can be launched directly from the user desktop by copying shortcuts from
~\AllUsers\StartMenu\Programs\NUMECA software\<product_name>\ to ~\AllUsers\Desktop.
It is not suggested for one user to simultaneously open (and therefore launch tasks in) more than one
FINE™ environment.
2.1.4 Uninstallation
Before removing a product, the license service and PVM should be stopped as detailed in the
following section. As a next step the product can be removed.
Uninstall license service
In case the license service is defined based on a version of NUMECA software to uninstall, the
license service should be stopped and removed first. Of course further use of remaining
NUMECA products on the machine will require redefining the license service based on the most
recent product.
In NUMECA Administration Tool
1. Go to the NUMECA Administration Tool home page,

2. click on License Management,
3. click on the Advanced button at the bottom of the Activate Product tab,
4. select the License server tab,
5. click on the Stop license server button to stop the specified license server.
6. The words "SUCCEEDED" or "Failed" are shown depending on the success or failure of the
uninstalling process, respectively.
7. Click on the Remove from autostart button to complete the uninstalling process.

Or in LMTools
1. Browse in Windows Explorer to the directory NUMECA_ INSTALLATION_

DIRECTORY/<product_name>/flexlm.
2. Double click on lmtools.exe.
3. Select Configuration Using Services.
4. Click on the Start/Stop/ReRead tab.
5. Select the NUMECA license service from the list of services.
6. Click on Stop to stop the license service.
7. Click on the tab Configure Services.
8. Select the NUMECA license service through the Service Name pull down menu.
9. Click on Remove Service to remove the service.
Close PVM
FINE™ environment uses PVM. Before uninstalling FINE™, the PVM process must be closed.
This can be done as follows:
1. Start the Task Manager (Modules/Task Manager) from the FINE™ GUI and select the
Hosts definition page in the menu on the left.
2. Click on the button Shutdown. A warning message will appear stating that all hosts will be
removed from the Virtual Machine and that FINE™ GUI will be closed. Click on yes to
continue.
Uninstall the Product
Before uninstalling verify the following:

l that there are no running tasks on the machine,
l that the license service was stopped as described in the previous section ("Uninstall license
service" (p. 27)).
Depending upon the configuration, there are several possibilities:
l If the product is the only product and the only version on the computer: uninstall in mono-
version environment.
l If other products and/ or other versions are installed on the same machine, it is possible to:
l to remove only some of these products/ versions: partly uninstall in multi- version
environment",
l to remove all products: fully uninstall in multi-version environment".

Uninstall in mono-version environment
Proceed as follows to remove FINE™/Open v72 in a mono- version environment under

Windows:
1. Optional:
a. go to NUMECA_INSTALLATION_DIRECTORY/fineopen72/bin64 in a dos shell and
b. type smpd -remove so as to remove the services for MPICH2.
Please do notice that this step is optional and only applies if MPICH2 services have not yet
been removed. Otherwise, an error message indicating that the service has not been installed
will appear. Please also notice that the services can be installed back if necessary with the
command smpd -install.
c. Go to NUMECA_ INSTALLATION_ DIRECTORY/impi5/ in a dos shell and type

hydra_service -remove so as to remove the services for IntelMPI.
Please do notice that this step is optional and only applies if IntelMPI services have not yet
command hydra_service.exe -install.
2. Go to NUMECA_INSTALLATION_DIRECTORY/pvm/bin in a dos shell and type nirshd -

remove so as to remove the services for RSH daemons.
Please notice that the services can be installed back if necessary with the command nirshd -
install.
3. Proceed with a reboot of the PC.

4. Open the Windows Control Panel (Start/Settings/Control Panel) and double click on the
icon Programs and Features.
5. Select Fineopen72 from the list and click on Add/Remove.
Partly uninstall in multi-version environment
Proceed as follows to remove FINE™/Open with OpenLabs™ v72 or for example

FINE™/Open v6.1 (but not both) in a multi-version environment under Windows:
2. Select Fine72 or Fineopen61 from the list and click on Uninstall.
Fully uninstall in multi-version environment
Proceed as follows to remove FINE™/Open with OpenLabs™ v72 and, for example,
FINE™/Open with OpenLabs™ v61 in a multi-version environment under Windows:
1. Optional:
a. go to NUMECA_INSTALLATION_DIRECTORY/fineopen72/bin64 in a dos shell and
b. type smpd -remove so as to remove the services for MPICH2.
Please do notice that this step is optional and only applies if MPICH2 services have not yet
command smpd -install.
c. Go to NUMECA_ INSTALLATION_ DIRECTORY/impi5/ in a dos shell and type

hydra_service -remove so as to remove the services for IntelMPI.
Please do notice that this step is optional and only applies if IntelMPI services have not yet
command hydra_service.exe -install.
2. Go to NUMECA_INSTALLATION_DIRECTORY/pvm/bin in a dos shell and type nirshd -

remove so as to remove the services for RSH daemons.
Please notice that the services can be installed back if necessary with the command nirshd -
install.
3. Proceed with a reboot of the PC.


5. Select Fineopen61 from the list and click on Uninstall.
6. Select Fineopen72 from the list and click on Uninstall.
2.1.5 Troubleshooting
Introduction
In most cases, a straightforward and careful execution of the instructions detailed in the
installation note enables to start NUMECA software smoothly. In case it is not working as
expected this section provides information on how to handle most common situations.
Product not starting
In case FINE™/Open with OpenLabs™ does not start, check the following items:
l Is NUMECA software installed with administrator privileges? If not, perform the installation
again with administrator privileges.
l Check whether 'Hide file extensions for known types' (activated by default for .dat extensions)
is disabled to enter the name of the license file with its extension license.dat.
l Is the license file valid and active to start the product ?
l Check if the license server is up. If so, the numeca.exe process should run in the Windows
Task Manager. If not, please do the instructions for license installation.
l 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.
l Check if the license key file is well readable by every user.
l Did the user configure his/ her working environment? If not, perform the configuration
according to the section "User Configuration" (p. 23); then log out and log in.
l Has the machine been rebooted after a change in the environment variables? If not, reboot it.
l Check if the TCP/IP protocol is installed on the machine. The protocol is mandatory to ensure
the correct function of the floating licenses.
l Are the NUMECA software components visible from the machine? If not, install them.
l Clean PMV files:

1. Close all tasks opened, including the FINE™GUI.
2. Open the Windows Task Manager and select the thumbnail Processes.
3. Check that no process pvmd3.exe is running. If so, select the process and click End
Process to stop it.
4. Delete any files called pvm*.username in the directory defined by the environment variable
PVM_TMP (usually C:\tmp).
Graphical problems and system crashes
NUMECA software 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 MSW driver is used under Windows instead. Note however that the proposed
drivers are usually less efficient in terms of graphical speed than the default driver.
1. Log in as administrator.
2. Launch regedit from the Start/Run menu.
3. Go to the HKEY_LOCAL_MACHINE/SOFTWARE/NUMECA International register.
4. Go into the folder of the package for which to modify the driver, e.g.: Fine# where # is the
version number.
5. Modify the DRIVER entry to either OPENGL or MSW.
Screen flashes
In some circumstances, the graphical area can flash during interactive operations, depending upon
the driver selected. Setting the environment variable NI_ DOUBLEBUFFERING to ON in
HKEY_ LOCAL_ MACHINE/SOFTWARE/NUMECA International/<product_ name> register
may solve the problem. To launch the registry editor, access regedit in the Start/Run text box.
Flow solver not starting in parallel mode
The parallel account must be configured at first use (see "User Configuration" (p. 23).

To launch parallel computations on Windows, the solver uses the MPICH2 libraries and the smpd
process manager. The smpd service is automatically installed and started during the installation of
FINE™. If the user has already the smpd service installation before installing FINE™, there may
be a conflict between the smpd services and thus the smpd service in FINE™ may not be started.
If the user gets the error message smpd version mismatch during the parallel computation, check
if the FINE™ smpd service is started. If not, stop other smpd services and start the one installed
by FINE™ (the service name is MPICH2 Process Manager, Argonne National Lab and the
linked executable is Installation_path\fine<version>\bin64\smpd.exe).
Cannot connect to other hosts
At the first execution of task manager
Can the machine be "seen" from the remote hosts (and vice-versa)? Use the ping command to
check this item.
Is the machine name included in the computer list within the rhosts.txt file of the user? Please
notice that capital letters must be used; extra-characters like "è, ä, ë, ..." may lead to potential
problems and should better be avoided.
Task manager launched once with success
In case the user can no longer connect to other hosts while this operation has at least be successful
once, the following should be checked:
1. a. Start the Task Manager (Modules/Task Manager) from the FINE™ GUI and select the
b. Click on the button Shutdown. A warning message will appear stating that all hosts will be
continue.
2. Close all currently open tasks (including the FINE™ GUI) and remove pvmd.* and pvml.*,
located in the directory defined by the environment variable PVM_TMP (by default C:\tmp), if
applicable. Additionally kill the PVM daemon pvmd3.exe, if applicable. The status of PVM
daemon can be observed by accessing the Windows Task Manager.
Remote copy does not work
The remote copy option can be accessed in Task Manager Tasks Definition area.

This option does not work if the user configuration file .cshrc (Linux platform) gives output to a
shell. To test whether it applies, open a DOS shell on the Windows machine and type the
command rsh machine_name echo YES <Enter> (where machine_name refers to the name of
the Linux machine). If the value returned is YES, the configuration is correct and the remote copy
option is expected to work properly. If additional lines are returned, problems are expected. If so,
further troubleshooting is needed as described in the following section.
Further troubleshooting

The following information can be helpful:
l the license key file license.dat.
l the hostname and hostid. This information can be obtained by launching the NUMECA
Administration tool (started from Start/Programs/NUMECA software/<product_
name>/Administration Wizard menu) or by executing into the subdirectory NUMECA_
INSTALLATION_ DIRECTORY\<product_ name>\flexlm the lmtools.exe (for Hostname
and HostID for NUMECA as Computer/Hostname and Ethernet Address under the
System Settings tab).
l the product name and version for which installation is causing problems.
l a description of the configuration (in terms of name, Windows version, local or domain user).
l the debug.log file generated when starting the license service.
l the .out files in C:\tmp.
l the pvml.username in C:\tmp (or directory defined by the environment variable PVM_TMP).
2.2 LINUX
The user is strongly advised to consult the "Linux" (p. 8) system requirements prior to start any
installation. Troubles may indeed appear during the installation and configuration phases in case
the listed hardware and software requirements would not be fully satisfied.

Please do notice that the documentation package attached to NUMECA software is not installed
during the installation procedure and can be downloaded from the Products page of the Customer
Area of www.numeca.be.
In case of trouble: see "Troubleshooting" (p. 50).

At the end of the "Troubleshooting" (p. 50) the information to provide is listed.
2.2.1 Installation
Install FINE™/Open with OpenLabs™ under Linux
1. Log in the workstation corresponding to the selected OS. It is strongly recommended not to
install the software as "root" or using the command "sudo" because the user may have no
permission to execute the software afterward. It is strongly recommended to check the
permission of the disk and directory the user will select for the software installation.
2. Check and make sure that the necessary disk space is available prior to starting the installation
process.
For the disk space requirements, see also: the "Linux" (p. 8) system requirements.
3. Get the installation package from the Products page of the Customer Area (www.numeca.be).
4. Check that the file can be accessed with full permission and extract it by typing the command
line: tar -xvf <package_name>.tar.
Do NOT extract the tar file in the target directory NUMECA_ INSTALLATION_
DIRECTORY in which the product will be installed.
5. Go to the directory containing the files extracted from the tar archive and type the command
./install_numeca <ENTER>.

The trusted storage based licensing requires a LSB compliant platform. After license agreement, a
check is performed to verify whether the host machine is LSB compliant. It is required if the
license server is installed on the host machine.
6. During the installation, the user will be asked to accept the terms of the License Agreement.
7. Enter the installation directory (referred to as NUMECA_INSTALLATION_DIRECTORY)
in function of one of the following scenarios:
l If NUMECA software was not installed before on the machine, choose a directory of your
preference. Providing a directory name that does not exist will create it automatically.
l If NUMECA software was already installed before, choose the same NUMECA_
INSTALLATION_DIRECTORY to use the multiple versions and/ or products in one
multi-version environment.
It is important to notice that a common NUMECA_INSTALLATION_DIRECTORY

should be shared by all NUMECA installations, otherwise the multi-version installation
will not be set up adequately. This is important e.g. for the good functioning of
PVM when launching several products or versions one after the other.
In order to run distributed memory parallel computations with OpenMPI, NUMECA

products must be installed in the same directory on different machines.
If the product has not been installed in the same 'NUMECA_INSTALLATION_DIRECTORY'

as the old product. The script 'add_ version.sh' in /NUMECA_ INSTALLATION_
DIRECTORY/COMMON/ will allow the user to link previous versions by specifying their full
path name (e.g.: /usr/numeca_software/fineautogrid122).
8. Finally, the so-called 'HostName' and 'HostID' information required to generate a license file
will be shown. This information should be sent to NUMECA local sales or support office.
Alternative to find the HostName and HostID from the Administration Tool
From the home page, the 'HostName' and 'HostID' can be found at the License Management
-> License server status tab (available in Advanced mode).

Alternative to find the HostName and HostID from a shell
Type the commands:

NUMECA_INSTALLATION_DIRECTORY/<product_
name>/LINUX/install/flex64/lmutil lmhostid -hostname <Enter>
and
NUMECA_INSTALLATION_DIRECTORY/<product_
name>/LINUX/install/flex64/lmutil lmhostid <Enter>.
9. After the package is installed, the NUMECA Administration Tool is launched automatically.
This is a tool for license management and provides a graphical user interface for the
management of the license server and client machines. The tool offers a guide through the
process of setting up and configuring a license server.
Alternative to access the Administration Tool
After installation, the Administration Tool can also be started through the command admin#,
where # is the software version (e.g. admin72). Click on Finish to leave the tool and to finalize
the installation.
Tasks that can be performed in the NUMECA Administration Tool
l License Management: to configure the machine as license server and/ or client.

l User Configuration: to set the PATH in the .bashrc/.cshrc/.profile files.
l Network Configuration: to clean and reinitialize PVM, to setup SSH connections to other
machines/ users.
l Diagnostics: to assess and fix problems with license management and graphics.
10. When receiving the license file from NUMECA, perform the license management and user
configuration:
l "License management" (p. 38)
l "User Configuration" (p. 44)
Launch the software as described in the user guide of your product while taking into account
the points of attention as listed in the "Software launch" (p. 47) section of the Linux user
configuration.

2.2.2 License management
Introduction
Before using NUMECA software, a valid floating license is required.
What is a 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 which 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 other computers (clients) with Linux or Windows, connected
through a network to the license server. The license server can be a Linux or a Windows
machine.
Important points of attention for license servers:

l NUMECA updates the security ID of license files with each major release. License files
with old security ID cannot be used with the latest NUMECA software. Please send your
old license file to NUMECA local sales or support office for an upgrade of the license file.
l Redundant license server can be delivered allowing to manage a floating license by several
servers. For more information, contact NUMECA local sales or support office.
l Machines used as license server must have a fixed first IP address. For example, when
using VPN on Windows, VPN will become the first network interface. In this case, the
license server will not work properly.
l By default it is not possible to use a virtual machine as a license server. To install a license
server on a virtual machine, contact your account manager.
l FlexLM requires LSB (Linux Standard Base) compliant OS.
NUMECA software must be installed on the license server. At the end of the installation, the
license information (the HostName and HostID of this computer) must be sent to NUMECA local
sales or support office in order to get a license file.
Before using NUMECA software, the license daemon should be configured on the license server.
To set up the license server it is necessary to prepare the license file and launch the server either
though the NUMECA Administration Tool or in a shell.

Access to the NUMECA Administration Tool
At the end of the installation of NUMECA software the Administration Tool is launched
automatically.
It can also be started anytime on Linux using the command: admin#, where # is the software
version.
It is recommended to run the Administration Tool as root to fully benefit from all possibilities of the
Administration Tool.
Example
adminopen72
Prepare the license file
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 that all users are able to access.
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 each user.
When using a TCP port for the license server, the port number has to be added in the license file on
the server/vendor line:
1. SERVER hostname hostid and VENDOR numeca should be replaced by SERVER
hostname hostid portnumber1 and VENDOR numeca portnumber2;
2. reread the license file,
3. start NUMECA software and specify the license server writing portnumber@hostname . All
specified ports should be opened and free.
License set-up in NUMECA Administration Tool
Start floating license service

To start the license service:
1. Select License Management.
2. On the line Activate from license file browse to the license file.
3. Click on Apply.
After the manual start of the license service, it is possible to have it automatically start at machine
boot:
1. In License management click on the Advanced button.
2. Go to the License server tab.
3. Press the Set autostart server button.
When starting the license service through the NUMECA Administration Tool, it uses the cron
daemon of the user who installs the software to define the automatic start of the license at machine
boot. Cron is a daemon used to schedule various kind of tasks on Linux. This tool uses crontab
text files that specify commands/ tasks to run at certain time intervals. In the case of NUMECA
Administration Tool, the cron daemon automatically starts the license service using the license file
(s) or existing server specified in the previous license server set-up. In absence of a previous set-
up, the daemon uses the dummy address NUMECA_ INSTALLATION_
DIRECTORY/flexlm/any.lic as the license server file location for the autostart.

1. From the NUMECA Administration Tool home page, click on License Management .
3. Select the License server status tab.
4. Select the license server on the left-hand side drop down menu.
5. Information regarding the available features, the number of available licenses and the number
of used licenses is shown under the License server info section.
Floating license on Linux client
When a floating license service is installed on a license server, this license service 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.

1. Go to the NUMECA Administration Tool home page,
2. click on License Management,
3. select the Activate Product tab,
4. select the Activate from existing server option.
Users willing to launch NUMECA software on a client should perform a user configuration on
this machine before first use as described in the section "User Configuration" (p. 44).
Replace the active license file license.dat with the update license provided by NUMECA
"license.old".
1. Go to the NUMECA Administration Tool home page, click on License Management .

4. Click on the Re-read license button.
5. The words "SUCCEEDED" or "Failed" are shown depending on the update success or
failure, respectively.
If the version of the Flexlm tool is upgraded or the version of the license file security ID is
upgraded, an update of the license file is not sufficient. The user must shutdown the running
license server and start a new license server with the latest Flexlm tool and the latest license file.
Alternative license server set-up from a shell
Start of the license service
To start the license daemon manually, do the following operations:

1. Go to the directory NUMECA_ INSTALLATION_ DIRECTORY/<product_
name>/LINUX/install/flex64/
2. Execute the command: ./lmgrd - c NUMECA_ INSTALLATION_
DIRECTORY/COMMON/license.dat -l $HOME/.numeca/debug_numeca.log
In these lines, 'NUMECA_INSTALLATION_DIRECTORY' should be replaced by the absolute
directory path where you have installed NUMECA software.
The manual start operations must be repeated each time the server machine is rebooted.
The license daemon can be automatically started during the workstation boot process. For
example to do so on LINUX Red Hat Enterprise 5.1:
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/<product_
name>/LINUX/install/flex64/lmgrd -c License_path/license.dat
In this line, 'NUMECA_INSTALLATION_DIRECTORY' should be replaced by the absolute
directory path where you have installed NUMECA software, 'License_path' should be replaced
by the absolute directory path where the license file is located.
The license server can also be started from /etc/rc#.d/. For more information contact your system
administrator or NUMECA local sales or support office.
Verify License Service Status

1. Go to the directory:
NUMECA_INSTALLATION_DIRECTORY/<product_name>/LINUX/install/flex64/
2. Execute the command: ./lmutil lmstat -c License_path/license.dat

If the license server is up this will be shown in the shell with the words: "license server UP
(MASTER) v11.13". 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 v11.13
If the license server or vendor daemon is not up see: "User Configuration" (p. 44).
3. To display the active users of a given feature, use the following command: ./lmutil lmstat -a -c
License_path/license.dat
Floating license on Linux client
When a floating license is installed on a 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 a Linux client, the path of the NUMECA_ LICENSE_ FILE should be defined in the
~/.flexlmrc file:
setenv NUMECA_LICENSE_FILE /full-path/license.dat or @servername
NUMECA_LICENSE_FILE=/full-path/license.dat or @servername
export NUMECA_LICENSE_FILE
Users willing to launch NUMECA software on a client should perform a user configuration on
this machine before first use as described in section "User Configuration" (p. 44).
When a floating license file is expired, contact NUMECA local sales or support office to obtain
an updated license file and follow the instructions below.
1. Rename the license file to license.dat.
2. Replace the active license file with the updated provided license on license server.
"license.old".
3. Go to the directory
NUMECA_INSTALLATION_DIRECTORY/<product_name>/LINUX/install/flex64/
4. Execute the command:

./lmutil lmreread -c LICENSE_FULL_PATH/license.dat
If the version of the Flexlm tool is upgraded or the version of the license file format is upgraded, an
update of the license file is not sufficient. The user must shutdown the running license server and start
a new license server with the latest Flexlm tool and the latest license file.
Optional: ask software to wait for license
To request that NUMECA products wait for an active license, define it in

/home/user/.numeca/preferences.dat using the keyword LICENSE_WAIT. This functionality is
available for all products.
Example
PRODUCT FINE/Open
LICENSE_WAIT
END_PRODUCT
Student version with activation ID
In general a license certificate (text file) is provided to give access to NUMECA software.
Alternatively the NUMECA Administration tool allows to use an activation ID to start the license
server. For example, the free student version is based on an activation ID and the instructions how
to use it are provided together with the activation ID. Use of an activation ID requires the use of
Trusted storage and installation of an anchor service. Hence this terminology can be found in the
NUMECA Administration Tool but can be safely ignored in case of a license certificate in text
file format.
Example of an Activation ID: C2a9-561f-7895-435b-acb5-3520-c166-4bcc
2.2.3 User Configuration
Introduction
At the end of the installation, each user willing to use NUMECA software must initially configure
his/ her working environment by running an initialization script.

Configure the user environment
1. Log in as user.
2. Go to the directory NUMECA_INSTALLATION_DIRECTORY/COMMON, and execute
the command ./configure. This operation will add a couple of lines in the user's .cshrc, .tcshrc
or .profile file (located in user's home directory) and add the NUMECA software in user's
default path.
3. Log out and log in again to apply the information in the .cshrc , .tcshrc or .profile file.
On Linux, NUMECA software saves some data (preferences, user fluid database, templates...) in the
folder $HOME\.numeca\. The variable $HOME is imposed by NUMECA software and cannot be
modified.
During the runtime, NUMECA software writes temporary data in the directory $HOME/.numeca/tmp.
This tmp directory can be redefined by defining the environment variable NI_TMP_DIR.
Optional: configure account to allow remote computations
When configuring the FINE™ environment for remote computations, it is strongly advised to
suspend all currently running tasks and shutdown the PVM daemon before starting the
configuration.:
continue.
RSH
FINE™ enables to launch computations on remote machines by using the Task Manager
capabilities. To be able to perform remote launches using rsh command, NUMECA software
must be installed on the remote machine and explicit permission must be specified in the dedicated
.rhosts file, located in the user's home directory. To this end, the following operation must be
checked and/ or performed:
1. Edit the .rhosts file and check information describing the list of computer and user authorized
to use the Task Manager. Example of .rhosts file:
computer1 user1 computer2 user1 computer3 user1
2. Check the permission of the .rhosts file (600 is required).

3. Check that the rsh command is active on all machines listed in the .rhosts file. This can be
done by typing the command rsh machine_name and checking that no password is requested.
If the system keeps requesting a password, please verify that the previous steps have been
correctly followed or contact your system administrator. Please note that the rsh command is
not available on HP and should better be replaced by the remsh command.
4. Check that the rlogin command allows user to login on all machines listed in the .rhosts file,
without requiring any password information. Providing these few tests are successful, the Task
Manager is ready to use.
Use of NUMECA software with other applications that would require an access to PVM can lead to
conflicts. Contact NUMECA local sales or support office for more information.
SSH
FINE™ enables to launch computations on remote machines by using the Task Manager
capabilities. To be able to perform remote launches using ssh command, NUMECA software
must be installed on the remote machine and the environment variable "NI_RSHCMD" should be
set to "ssh":
setenv NI_RSHCMD ssh
export NI_RSHCMD=ssh
and explicit permission must be specified in the dedicated ~/.ssh/authorized_keys file. To this
end, the following operations must be checked and/ or performed:
l In a shell, the command ssh-keygen -t dsa will generate in the directory ~/.ssh two files, one
private key and one public key.
l Check the permission of the private key (600 is required).
l The public key can be put on the other machine in the ~/.ssh/authorized_keys file.
The permissions on the file must be very strict:
l chmod 750 ~/
l chmod -R 700 ~/.ssh

Use of NUMECA software with other applications that would require an access to PVM can lead to
conflicts. Contact NUMECA local sales or support office for more information.
Software launch
When launching the FINE™ environment, the user should note:

l It is not allowed for one user to simultaneously open (and therefore launch tasks in) more than
one FINE™ environment with different versions.
l In a multi-version environment, it is strongly suggested to shutdown the Task Manager when
switching from version to version, in order to avoid possible conflicts due to the PVM
daemon. This warning only applies if the versions have been installed in distinct NUMECA_
INSTALLATION_DIRECTORY locations.
To launch the components:
<productname><version#> -print <Enter>
Examples
For FINE™/Open with OpenLabs™: fineopen72-print <Enter>

For CFView™: cfviewopen72 -print
For HEXPRESS™: hexpress72-print <Enter>
For HEXPRESS™/Hybrid: hexpresshybrid72-print <Enter>
It is important to outline that no output is displayed by default in the shell where the software is
launched. Instead the output is redirected to log files, located in the directory ~/.numeca/tmp/ and
named as startup_logfile_fine , startup_logfile_hexpress, startup_logfile_cfview.
However, outputs can still be forced for display in the shell. Add the - print command to the
command line. This will give additional information during software launch, especially during the
initial configuration of the software.
2.2.4 Uninstallation
Introduction
This section details the steps required to properly remove an installation of NUMECA software.
Depending upon the configuration, there are several possibilities:

l If the product is the only product and the only version on the computer: uninstall in mono-
version environment.
l If other products and/ or other versions are installed on the same machine, it is possible to:
l to remove only some of these products/ versions: partly uninstall in multi- version
environment",
l to remove all products: fully uninstall in multi-version environment".
Furthermore, the license service may be stopped if NUMECA software is not used on any
machine connected to the license server.
Uninstall License Service
Points of attention:
l Instructions related to the NUMECA license service must be removed if the machine has
been configured to start automatically the license service at start up. These instructions can
be accessed in the /etc/inittab file.
l It is not possible to stop the license server without an internet connection.
l The license server cannot be started or stopped without a network connection.
In NUMECA Administration Tool
1. From the NUMECA Administration Tool home page, click on License Management,
4. Click on the Stop license server button to stop the specified license server.
5. The words "SUCCEEDED" or "Failed" are shown depending on the success or failure of the
uninstalling process, respectively.
6. Click on the Remove from autostart button to complete the uninstalling process.
In a shell
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/<product_
name>/OSname/install/flex#/
2. Execute the command: ./lmutil lmdown -c LICENSE_FULL_PATH/license.dat
Close PVM
FINE™ environment uses PVM. Before uninstalling FINE™, the PVM process must be closed.
This can be done as follows:
continue.
Uninstall in mono-version environment
Proceed as follows to remove a product in a mono-version environment under Linux:

1. Verify that there are no running tasks on the machine.
2. Stop the license service before uninstalling NUMECA software. More details in the subsection
"Uninstall License Service" (p. 48).
3. Remove the lines from "#begin NUMECA configuration" to "#end NUMECA configuration"
from the user's .cshrc, .tcshrc or .profile file.
4. Remove the directory NUMECA_INSTALLATION_DIRECTORY and its content.
Partly uninstall in multi-version environment
Proceed as follows to remove one product version in a multi-version environment under Linux:
"Uninstall License Service" (p. 48) .
3. Remove the directory NUMECA_INSTALLATION_DIRECTORY/<product_name>/ and
all of its content.
Before removing the directory NUMECA_INSTALLATION_DIRECTORY/<product_name>/, check

and make sure that the license file is not inside the directory.

Fully uninstall in multi-version environment
Proceed as follows to remove all NUMECA products in a multi-version environment under

Linux:
"Uninstall License Service" (p. 48).
3. Remove the lines from "#begin NUMECA configuration" to "#end NUMECA configuration"
from the user's .cshrc, .tcshrc or .profile file.
4. Remove the directory NUMECA_INSTALLATION_DIRECTORY and its content.
2.2.5 Troubleshooting
Introduction
In most cases, a straightforward and careful execution of the instructions detailed in the previous
chapters enables the user to start NUMECA software smoothly. In case of problems, this section
aims at providing guidelines on how to detect and solve possible troubleshooting.
FINE™/Open with OpenLabs™ not starting
In case FINE™/Open with OpenLabs™ fails to start, use the -print argument in the command
line, for example cfviewopen72 -print to start the product.
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:
l Is the license file valid and active to start the product ?
l 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.
l 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.
l Check if the license key file is well readable by every user.
l Did the user configure the working environment? Before using NUMECA software, each user

must configure the working environment using the command ./configure within the
NUMECA_INSTALLATION_DIRECTORY/COMMON/ directory; then log out and log in.
l Is the graphics driver appropriate for the display ? Try to activate the X11 driver.
2. Type: host_ name display_ name possible_ drivers chosen_ driver e.g. gauss.numeca.be
gauss OPENGL:X11 X11
Alternatively, the driver can be manually specified in a shell for that shell session only through
the following commands:
l Check if the TCP/IP protocol is installed on the machine. The protocol is mandatory to ensure
the correct function of the floating licenses.
l Are the NUMECA software components visible from the machine? If not, install them.
l Is the OS adequate? If not, copy the correct tar file and start the installation again.
l Are the Linux permissions sufficient for the user to access NUMECA software installed? Ask
your system administrator.
l Successive installation of FINE™ can possibly lead to trouble if tasks have been improperly
stopped. To purge this issue:
Close all tasks opened (including FINE™ GUI) and kill the PVM daemon related to the user
(if applicable). This operation can be performed through the kill command applied to the
corresponding process number. Process numbers can be outlined using the command ps -ef |
grep pvm. This operation must be performed on each machine the user can possibly access.
Graphical problems and system crashes
NUMECA software 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.
2. Type: host_name display_name possible_drivers chosen_driver e.g. gauss.numeca.be gauss
OPENGL:X11 X11
Alternatively, the driver can be manually specified in a shell for that shell session only through the
following commands:
GUI 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 Linux. The variable can be manually specified through the
following commands:
l for csh or tcsh shells: setenv NI_DOUBLEBUFFERING ON
l for bash or korn shells: NI_ DOUBLEBUFFERING=ON export NI_
DOUBLEBUFFERING
Display drivers not detected
NUMECA products with GUI check the available working drivers and updates automatically in
the .drivers file located in the .numeca directory of the user 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.

Cannot connect to other hosts
At first execution of Task Manager
In case the user cannot connect to other hosts at the first execution of the Task Manager, the
following should be checked:
l Is the machine included in the computer list within the .rhosts file (when running remote
commands with rsh)? This file details the computers authorized to use the Task Manager. The
file is located in the user home directory.
Example of .rhosts file
computer1 user1 computer2 user1 computer3 user1
l Has the .rhosts adequate permission (when running remote commands with rsh)? (600 is
required)
l Is NUMECA software adequately installed on the selected remote hosts? If not, perform the
installation.
l Is the rsh command active on all machines listed in the .rhosts file? This check can be done by
typing the command line rsh machine_name echo \$PVM_ROOT <Enter>. All selected
machines must be accessed without requiring any password information and the $PVM_
ROOT variable should be displayed adequately. Please note that the rsh command is not
available on HP and should better be replaced by the remsh command.
l Is the user .cshrc, .tcshrc or .profile file fully executed when opening a new batch shell (non
interactive mode)? Ask your system administrator to check this issue.
Task Manager launched once with success
In case the user can no longer connect to other hosts while this operation has at least been
successful once, the following should be checked:
continue.
3. Close all tasks opened (including FINE™ GUI) and kill the PVM daemon related to the user
(if applicable). This operation can be performed through the kill command applied to the
corresponding process number. Process numbers can be outlined using the command ps -ef |
grep pvm. This operation must be performed on each machine the user can possibly access.

Further troubleshooting

The following information can be helpful:
l the license key file license.dat.
l the hostname and hostid. This information can be obtained by launching the NUMECA
Administration tool (starting through the command admin) or by executing the commands
lmutil lmhostid - hostname <Enter> and lmutil lmhostid <Enter> in the NUMECA_
INSTALLATION_DIRECTORY/<product_name>/LINUX/install/flex64/ directory.
l the product name and version for which installation is causing problems.
l a description of the configuration (in terms of name, platform and OS for each machine on
which NUMECA software is installed).
l the .log file generated during the installation and located in the /tmp directory on the machine
from where the script ./install_numeca has been launched .
l the "startup_logfile_*" files located in ~\.numeca\tmp.

© NUMECA International, all rights reserved
EN201805221004

FINEOpen Installation

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

FINEOpen Installation

Hochgeladen von

Copyright:

Verfügbare Formate

INSTALLATION NOTE

FINE™/Open with OpenLabs™ 7.2

2 FINE™/Open with OpenLabs™ 7.2 Installation note

3 FINE™/Open with OpenLabs™ 7.2 Installation note

1.1.1 Supported platforms and operating systems

Formally tested on Also known to run ona

Your platform of preference is not in the list?

4 FINE™/Open with OpenLabs™ 7.2 Installation note

1.1.3 Hardware requirements

1.1.4 Memory and disk space requirements

5 FINE™/Open with OpenLabs™ 7.2 Installation note

FINE™/Open with OpenLabs™

The use of minimum 1 GB RAM is mandatory, but the installation of 2 GB is recommended. As

6 FINE™/Open with OpenLabs™ 7.2 Installation note

1.1.5 Graphics requirements

To change the used driver

1.1.6 Compilation requirements for OpenLabs™

7 FINE™/Open with OpenLabs™ 7.2 Installation note

1.2.1 Supported platforms and operating systems

Formally tested on Also known to run ona

Your platform of preference is not in the list?

8 FINE™/Open with OpenLabs™ 7.2 Installation note

Optimal use of an Infiniband connection

1.2.2 Multiprocessors calculations

1.2.3 Hardware requirements

9 FINE™/Open with OpenLabs™ 7.2 Installation note

1.2.4 Memory and disk space requirements

FINE™/Open with OpenLabs™

The use of minimum 1 GB RAM is mandatory, but the installation of 2 GB is recommended. As

10 FINE™/Open with OpenLabs™ 7.2 Installation note

1.2.5 Graphics requirements

To change the used driver

11 FINE™/Open with OpenLabs™ 7.2 Installation note

1.2.6 Compilation requirements for OpenLabs™

12 FINE™/Open with OpenLabs™ 7.2 Installation note

13 FINE™/Open with OpenLabs™ 7.2 Installation note

In case of trouble: see "Troubleshooting" (p. 31).

Install FINE™/Open with OpenLabs™ under Windows

14 FINE™/Open with OpenLabs™ 7.2 Installation note

It is important to notice that a common NUMECA_INSTALLATION_DIRECTORY

Alternatives to get the license information

Alternatives to access the Administration Tool

After installation, the Administration Tool can also be started from

15 FINE™/Open with OpenLabs™ 7.2 Installation note

l License Management: to configure the machine as license server and/ or client.

Install HEXPRESS™ v7.2 standalone

The installation of FINE™/Open with OpenLabs™ v7.2 includes HEXPRESS™ v7.2.

16 FINE™/Open with OpenLabs™ 7.2 Installation note

Before using NUMECA software, a valid floating license is required.

What is a floating license?

With a floating license each software component is managed by an independent maximum

17 FINE™/Open with OpenLabs™ 7.2 Installation note

Prepare the license file

To install the license service:

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

18 FINE™/Open with OpenLabs™ 7.2 Installation note

License set-up in NUMECA Administration Tool v12

Start floating license service

To start the license service:

Automatic start at machine boot

Verify license service status

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

19 FINE™/Open with OpenLabs™ 7.2 Installation note

Update of license file