Install

STAR-CD INSTALLATION GUIDE

Version 4.20.010(Updated: 24 June 2013)

CONFIDENTIAL — FOR AUTHORISED USERS ONLY

Formatted for duplex A4 printing

© 1988-2013 CD-adapco

Version 4.20 (Updated: 24 June 2013) 1

TABLE OF CONTENTS

1 SYSTEM REQUIREMENTS AND LIMITATIONS

Supported Systems ................................................................................................... 1-1

Graphics Support ...................................................................................................... 1-2

Disk Space Requirements ......................................................................................... 1-2

System-specific Issues .............................................................................................. 1-3

2 STAR-CD INSTALLATION

Introduction .............................................................................................................. 2-1

STAR-CD suite installation on Linux. ..................................................................... 2-2

STAR-CD suite installation on Windows ................................................................ 2-7

3 LICENSING

FLEXlm Version 11.9.1.0 ........................................................................................ 3-1

Vendor Daemon Name ............................................................................................. 3-1

Starting the License Daemon .................................................................................... 3-1

License File Location ............................................................................................... 3-2

Environmental Variables .......................................................................................... 3-3

4 TESTING THE INSTALLATION

Setup User Environment to Run STAR .................................................................... 4-1

Create a Working Directory ...................................................................................... 4-2

Automatically Generate the Case Using Pre-processor ............................................ 4-2

Run the STAR solver ................................................................................................ 4-3

Appendix A hardware.ini (Site specific configuration file)

Default Settings ....................................................................................................... A-1

Platform Settings ..................................................................................................... A-2

Host Settings ............................................................................................................ A-2

Group Settings ......................................................................................................... A-3

Appendix B software.ini (SOFTWARE CONFIGURATION FILE)

Default Settings ........................................................................................................B-1

Platform Settings ......................................................................................................B-2

Group Settings ..........................................................................................................B-3

Example software.ini ................................................................................................B-3

2 Version 4.20 (Updated: 24 June 2013)

Appendix C Microsoft Windows HPC Server

Installing Windows HPC Server Environment .........................................................C-1

Configure the Cluster ................................................................................................C-1

Appendix D Compilers Used to Build the Software

Porting Reference Platforms for the STAR Solver .................................................. D-1

Porting Reference Platforms for the Advanced Pre-/Post-processor ....................... D-2

Section 1 SYSTEM REQUIREMENTS AND LIMITATIONS

Supported Systems

Version 4.20 (Updated: 24 June 2013) 1-1


Supported Systems

This document applies to STAR-CD version 4.20, the current release of the STAR-CD suite of simulation software for continuum mechanics.

A separately installed FORTRAN compiler is only required if the user wishes to implement User Coding (In Appendix D, Table D.1 outlines appropriate compilers for each machine type). Users who wish to use the non-default installations are directed to the appendices for information about different ways to configure the software.

Certified platforms are combinations of hardware and software that are subjected to thorough automated and interactive testing.

Supported platforms are combination of hardware and software where some interactive testing has been performed and/or compatibility is expected:

Table 1-1 Certified Platforms

Platform Operating System

Linux x86 (64bit)Red Hat Enterprise Linux 6.2

(RHEL 6.2)

Windows x86 (64bit)Microsoft Windows 7 SP1

Microsoft Windows Server 2008 R2

Table 1-2 Supported Platforms

Platform Operating System

Linux x86 (64bit)

Red Hat Enterprise Linux 6.3

(RHEL 6.3)

SuSE Linux Enterprise Server 11 SP2

(SLES 11 SP2)

Windows x86 (64bit)Microsoft Windows 8

Microsoft Windows Server 2012

SYSTEM REQUIREMENTS AND LIMITATIONS Section 1

Graphics Support

1-2 Version 4.20 (Updated: 24 June 2013)

Some of these versions may require OS patches to function properly. CD-adapco makes no claim for suitability of other Linux distributions not mentioned.

HPC mode (parallel computation) will require implementations of MPI (Message Passing Interface) compiled for specific operating systems. IBM Platform MPI ISV Edition is now supplied with the STAR-CD distribution. It is available for Linux and Windows. Alternative third party vendor’s MPI implementations (e.g. Intel MPI and Open MPI) can be used.

Graphics Support

The GUI for pro-STAR, the advanced pre- and post-processing tool, has been rewritten and now uses the Qt GUI toolkit. The Motif based version has been discontinued. On Linux systems, the command-line-only pro-STAR X-Window system driver (prostar x) continues to remain available. On Windows systems, the X driver has been discontinued.

OpenGL runtime libraries and appropriate hardware are required to run the default OpenGL graphics driver. These runtime libraries are usually available for free on most systems, but are not necessarily part of the default operating system installation.

Disk Space Requirements

The disk space requirements varies considerably between each of the STAR-CD ports. Allow between 5GB and 6GB of free disk space for a single port full installation.


System-specific Issues



CSH/TCSH problems with MPI on clusters

Users with either csh or tcsh as their default shell need to be aware of potential MPI problems caused by poorly written .cshrc files. This file is executed whenever a new shell is created and this can cause MPI jobs to fail. Examples of problems are setting TMPDIR or stty settings without checking whether a shell is running in batch mode or under remote shell session. If STAR fails to run on a cluster and renaming your .cshrc file fixes the problem then you have a poorly written .cshrc file.

This problem can be avoided by setting TMPDIR to a local disk and protecting settings like stty with an if conditional to test for interactive sessions:

if ( $?TERM && "‘tty | \grep -v ’not a tty’" != "" ) then

Most people don’t need a .cshrc and renaming this file to .login will also work. Please note that the ksh and bash shells do not have any of these problems.

Linux

Licensing

FLEXlm licensing server now requires Linux Standard Base version 3. These utilities require symbolic links to the standard Linux 2.x loaders. If these are missing, then LSB 3 executables will produce an error like the following:

starusr@host_$ ./lmgrdksh: ./lmgrd: No such file or directorystarusr@host_$

On some Linux systems, installing the LSB 3 packages will not create the required symbolic links. These must be created manually as follows:

ln -s ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3




ES-ICE

ES-ICE is a Motif based program, so it has dependency on the libXm.so.3 Motif runtime library. While most modern Linux distributions have moved on to newer GUI toolkit libraries, it still remains as an optional library package that can be selected.

/opt/starcd4/ICE/4.19.068/linux64_2.6-x86-glibc_2.3.4-gcc_4.4.3-ifort_11.0/bin/es-ice: error while loading shared libraries: libXm.so.3: cannot open shared object file: No such file or directory

STAR Solver

On some 64bit Linux x86_64 systems, the matching GNU C++ 4.x run time may be missing:

star: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

Install the GNU C++ 4.x “/usr/lib64/libstdc++.so.6” run time library.

Many Linux distributions come with very small default stack sizes. The stack size may need to be increased when running ASI cases on a cluster. This can be done by adding lines such as the following in the /etc/security/limits.conf file:

* soft stack 16384* hard stack unlimited

The exact stack size limit may depend on the largest case size you wish to run. You do not need to restart your machine for this to take effect.

Open MPI 1.6.2 on Linux requires the libnuma.so.1 shared object for non-uniform memory access policies. This may be missing in the default installations of some Linux distributions.




Intel MPI 4.1 will not work on clusters where nodes cannot determine their correct external IP address using the ping command:

Assertion failed in file ../../socksm.c at line 2970: (it_plfd->revents & POLLERR) == 0internal ABORT - process 0

Please check that the host name is not set to 127.0.0.1 or 127.0.1.1 in the local /etc/hosts file on each node. A fresh installation of some Linux distributions configure /etc/hosts file in this way.

Windows

Intel Compiler Installation

STAR-CD for Windows requires an Intel® Visual Fortran Composer 2013 XE compiler (13.1.1.171) to run cases containing user coding. If the case is to be run on a Microsoft Windows HPC server cluster, the Intel FORTRAN compiler should only be installed on the head node.

Also Microsoft Visual Studio 2012 professional or express edition is need to build STAR-CD user coding libraries. If you don't own Microsoft Visual Studio you need to install Microsoft Visual Studio 2012 Shell (Isolated), Microsoft Visual Studio 2012 Shell (Integrated) and Visual C++ 2012 Express for windows Desktop. Please install Visual C++ 2012 Express after the Microsoft Visual Studio 2010 Shell.

Microsoft Visual Studio express product are available for download from:

http://www.microsoft.com/visualstudio/eng/downloads

A Microsoft Visual Studio 2012 installation is required for user codingdebugging support. To start a debugging session issue the command:

star -g -devtool=devenv




STAR-CD compilation tool configuration takes place during installation if therequired tools are found on your system. If the compiler tools are installed afterSTAR-CD, please rename:

<STAR-CD INSTALL LOCATION>\bin\autoenv-intel.bat.example

to:

<STAR-CD INSTALL LOCATION>\bin\autoenv-intel.bat.

Short name (8dot3name)

STAR-CD requires short name in directory path in the 8dot3name convention. In Windows Server 2008 R2 and 2012 installations the default behaviour has 8dot3name disabled. To enable 8dot3name in the c: drive:

fsutil 8dot3name set c: 0

To query the 8dot3name support of a drive:

fsutil 8dot3name query c:

If you do not wish to enable 8dot3name support, please install STAR-CD in a installation directory that does not contain a space. You will also need to run STAR-CD in case directories that do not contain a space.




Running on clusters

STAR-CD runs require the user to have power user rights or higher on the local machine starting the run. Power user rights are not required for shared memory runs on the local machine.

To configure this, login to node which will start the run with administrator privilege.

If you are not using a domain controller:

• Select Administrator Tools > Computer Management > Local Users and Groups > Users > Account Name of Users running STAR-CD

• Right click and select properties.

• Select the member of tab, click the advanced button, and then find now button.

• Select Power User or Administrator and click ok.

If you are using a domain controller:

• Select Administrator Tools > Computer Management > Local Users and Groups > Groups > Power User or Administrator.

• Right click and select properties.

• Click add, then advanced button, and then find now button.

• Select Domain Users and click ok.

If your system administrator does not wish to add all Domain users as power users on the local machine, they can add individual users or create a STAR-CD users group.

Privileges can also be added from the command line using the net local group "power user" "domain name\account name or group" /add command.




Section 2 STAR-CD INSTALLATION

Introduction



Introduction

This new version of STAR-CD is released through user services download. The following is the minimum that is required to be installed to run STAR-CD:

• pro-STAR (pre-processor and post-processor)• STAR (the continuum mechanics solver)• STARDATA (chemical reaction databases)• FLEXlm (can be omitted if FLEXlm is already available)

Additional plugins are provided. Please check the installation messages for a full list of available software and versions. Several other software components are supplied and these are presented during the installation. Several of these were previously included as pre-installed plugins, but now they can be installed in a separate manner, allowing users to try different versions of the additional software without disturbing existing installations

The following optional components are available for Linux in the same package:

• STAR-NET (for running under Grid Engine, OpenLava, Lava, LSF, OpenPBS, PBSPro, SGE and Torque resource managers)

• IBM Platform MPI ISV Edition 8.3.0.2• PC MPI 8.1.1.0 (older version of IBM Platform MPI)• Intel MPI 4.1.0 (alternative commercial MPI)• Open MPI 1.6.2 (alternative Open Source MPI)• Common (Contains the manuals and tutorials, it is recommended that these

are installed).

The following optional components are available for Windows in the same package:

• IBM Platform IBM ISV Edition 8.3.0.3• PC MPI 8.1.1.0 (older version of IBM Platform MPI)• Intel MPI 4.1.0 (alternative commercial MPI).

STAR-CD INSTALLATION Section 2

STAR-CD suite installation on Linux.



In these instructions, it is assumed that you will install STAR-CD in a directory called /opt/starcd. If you wish to use another directory, replace /opt/starcd with the actual full path directory name.

Preparing Downloaded Packages

Unpack the tar file follow the instructions in the “Installing the Software” section, by substituting the string “/opt/starcd” with the location of the distribution on your site.

Installing the Software

In this section the location /tmp/star_pkg can refer equally to the location of the tar or zip file unpacked from the unpacked downloaded package. It is assumed here (for example) that the destination is /opt/starcd.

It is not recommended to run the installer using the “root” account. This is because the installation of process of STAR-CD does not require administrative permission.

Change directory to /tmp/star_pkg and execute the setup script with the command “sh ./setup”. It is recommended not to run the installer as “root” as it is not necessary to have administrative permission to install STAR-CD.

The script can be interrupted at any time before the final stage in which the actual installation of files is initiated (usually <CTRL>-C). This script lists the various required packages and optional packages available and prompts the user to select a system for installation. It will also prompt the user for the installation directory, and create it if necessary. The installation process can be repeated for numerous product combinations. The installation script makes no assumption about the intended target platform, so all products may be installed on a central server or over a network.

Secure Shell (ssh/scp) is now the default protocol for secure authentication toremote hosts for STAR-CD. It is not recommended to use the old insecure remote shell (rsh/rcp) protocol, which is not installed by default in modern linux distributions.

A different secure connection protocol like Kerberos or one that comes with your batch scheduler can be chosen during the installation process:




Secure Shell (ssh/scp) is now the default protocol for secure authentication toremote hosts. Do you want to use an alternative protocol?yes

Please enter full path to command for launching remote shell:/usr/kerberos/bin/rsh

Please enter full path to command for remote file copy:/usr/kerberos/bin/rcp

Configured "REMOTETASK=/usr/kerberos/bin/rsh".Configured "REMOTECOPY=/usr/kerberos/bin/rcp".

After all the specified software has been installed, the Software Administrator should check that the following files are up-to-date:

/opt/starcd/doc/install.pdf/opt/starcd/doc/prostar-error-report.pdf/opt/starcd/doc/star-error-report.pdf/opt/starcd/doc/star_rnotes.pdf

These documents are occasionally updated after the creation of the archives supplied with the tar files. Please check the copies on the User Services web site (https://support.cd-adapco.com) or contact your support representative. The PDF files are accessible to users through the pro-STAR help menu.

Initialising the Software

The installation tool allows any number of platform specific software to be installed below the same “STARDIR” location. Subsequent installation processes will not affect any configuration files that are already in the $STARDIR/etc directory. Repeated installation action creates files with an extension “-new” (for example software.ini-new) that can be renamed as the Software Administrator wishes, provided that the filename extension is retained as “.ini”. The new configuration file can be activated by issuing the command “setstar” after an initialization of the default system. A menu is presented, allowing the user to select the appropriate configuration file.

Local copies of the software.ini file can be created to tailor the installation for variation of versions or non-default ports. For example, one might create a file named alternate.ini in the $STARDIR/etc directory that activates a non-default port of STAR solver, or make a copy in one’s home directory with different settings.

To activate the alternative INI files, a repeated call to ‘setstar’ offers a menu of options for different configuration files. If you choose the last option on the list, then the full path to the file must be specified.




Hardware and Software Configuration

The installation directory will contain:

bin/doc/etc/sbin/IBMMPI/ICE/INTELMPIOPENMPI/PCMPI/PROSTAR/STAR/STARDATA/STARNET/(Plus others)

The etc directory contains three important configuration files. The hardware.ini file contains site hardware and license information. The software.ini file contains installation specific information. The setstar file configures the user’s environment to be able to run STAR.

hardware.ini

An example hardware.ini file is written with the installation. A full list of all options is given in Appendix A, and these can be optimised for each site. However, during the installation, the Software Administrator answers two questions about licensing. The results are placed in the hardware.ini file. This is all that is required in order to test the software.

software.ini

Under normal circumstances, the software.ini should not need editing. However, there may be occasions where non-standard installation combinations are required, and Appendix B contains a list of options and instructions for these circumstance.

setstar

This file should not be edited. The end user simply executes the following shell dependent commands.




For Bourne, Korn or Bash shells:

. /opt/starcd/etc/setstar

For C and Tcsh shells:

source /opt/starcd/etc/setstar

STAR version information will be printed out in the terminal screen, for example, on a linux platform:

SARDIR: /opt/starcdSTARINI: DefaultCDLMD_LICENSE_FILE: 19999@starlicenseserverLM_LICENSE_FILE: 12345@otherlicenseserver

ICE: ICE/4.*/linux64_2.6-x86-glibc_2.3.4-gcc_4.4.3-ifort_11.0IBMMPI: IBMMPI/8.3.0.2/linux64_2.6-x86-glibc_2.3.4INTEL: /opt/intelINTELMPI: INTELMPI/4.1.0/linux64_2.6-x86-glibc_2.3.4OPENMPI: $STARDIR/OPENMPI/1.6.2/linux64_2.6-x86-gcc3.4.6-glibc_2.3.4PCMPI: $STARDIR/PCMPI/8.1.1.0/linux64_2.6-x86-glibc_2.3.4PROSTAR: $STARDIR/PROSTAR/4.20.*/linux64_2.6-x86-glibc_2.3.4STAR: $STARDIR/STAR/4.20.*/linux64_2.6-ifort_11.0-glibc_2.3.4-dsoSTARCDMAN: $STARDIR/4.20.*/genericSTARDATA: $STARDIR/STARDATA/2.*/genericSTARNET: $STARDIR/STARNET/3.00.023/generic

Activating Alternative Configuration

In this example, an additional INI file has been created by the local site Software Administrator. The alternate.ini that can be accessed through a subsequent call to ‘setstar’, after the initialization of the default installation. These give access to additional platforms where they are supplied. Their naming is arbitrary and down to a site policy:

user@host_$ setstar

STAR-CD INITIALIZATION MENU ---------------------------1 = Default preference (software.ini)2 = User defined preference (alternate.ini)3 = Specify other preference

Please enter your choice (1-3):3

Please refer to Appendices A and B about changes to “.ini” files. If you are not a Software Administrator, you can make copies of the “.ini” files to edit and choose item 3 to specify the full path to the alternative “.ini” file.




Additional Software: es-solutions and plugins

The functionality of STAR-CD software is often enhanced by user’s own coding, sometimes this is to achieve repetitive tasks; other times it is to investigate new and different modelling strategies. At CD-adapco, our engineers have developed extensions to STAR-CD referred to as “es-solutions” (for example: es-ice, es-after etc) and other additional software “plugins” (wave, DARS-CFD, DOLFA). In previous versions of STAR-CD they were pre-installed in the solver directories. They now reside in individual directories and, thus, can be installed anywhere on the file system. However, we recommend that you keep to the original directory structure until you have gained some familiarity and confidence with the new installation. Some of these tools are not available for every platform but this will be shown during the installation stages and the automatic log of what has been installed. To view the available plugins for a particular platform after installation you can use the command “star -showplugins”.

Running STAR solver on clusters

We strongly recommend the installation of resource manager such as Lava, LSF, PBSPro, Sun Grid Engine or Torque for managing batch jobs on your cluster. You will need to install STAR-NET which acts as an interface between the resource manager and STAR-CD.

In order to get the best scalability of STAR-CD solver on a large number of nodes, it is important is use a high speed interconnect such as Infiniband, Myrinet or Gigabit. We recommend IBM Platform MPI as it supports multiple interconnect types.

It is important to provide sufficient I/O bandwidth to a large parallel application running on many compute nodes. Therefore we recommend a parallel file system with multiple I/O nodes. In a large compute cluster with multiple parallel jobs running, it is important to provide enough disk bandwidth by using a cluster of I/O nodes. STAR-CD supports parallel I/O through the new "-pario" option.

We also recommend all user coding compilations and geometry decomposition to be done on a head node. These should be done before submitting jobs to the batch system using the "-ufile" and "-decomp" options. For large clusters you may wish to employ multiple head nodes.

Please refer to documentation in directory associated with the version of STAR-NET

$STARNET/generic/doc/starnet.pdf


STAR-CD suite installation on Windows



This installation must be performed by the administrator or a user with administrator rights. If you wish to change the default installation directory please note that STAR-CD on Windows cannot be installed in the same directory as any previous versions. Select custom install if you want to use a network license server instead of installing a local license sever. If any errors occur during installation, these are recorded in the file:

%STARDIR%\STAR-CD4.20.*_InstallLog.log

If you wish to run STAR-CD on a cluster using multiple nodes, you must install IBM Platform MPI, PC MPI or Intel MPI on the same drive with same path structure on all nodes. This can be done by selecting destination location during the MPI installation. Users will also need to store their password in the Windows registry as described in Appendix E of the User Guide.

To run STAR-CD on a cluster it is recommended to use UNC share by performing Network Installation for clusters. For Windows 7 and Windows Server 2008/2012 (but not Windows 8) it is also possible to use dynamic UNC shares by disabling User Access Control (UAC) and rebooting. On Windows Server 2012 you must switch off UAC by changing the registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA

value to 0 using the regedit command.

Installing Downloaded Packages

The zip files must be unpacked into separate temporary directories (for example C:\tmp\star_pkg). Click the “STAR-CD_4.20.*.exe” icon found in the unpacked directory to begin the installation process then follow the on screen instructions




Network Installation for clusters

STAR-CD 4.20 supports running from a file server installation and working location on a file server location. Dependencies are installed on all clients workstations.

The administrator needs to login to the file server to perform a STAR-CD installation:

1. Select ”Custom (Advanced)” option.

2. Select Additional Tasks “Share install directory” to make the installation visible.

3. Select Additional Tasks “Use network working location for cases” and choose the working location in UNC format. If you want to change or add “Use network working location for cases” after installation you need to modify or set “STARCASES” variable in “<STAR-CD_INSTALL_LOCATION\ bin\starcdpowershell.bat”.

4. The administrator has to make sure that the installation and working locations are visible on all compute nodes. In addition working directory needs "Security > Full Control > Allow" to be enabled for all users.

If the file server does not have a compiler, please rename“autoenv-intel.bat.example" and modify as described in section “Intel Compiler Installation” on page 1-5.

To configure a compute node to use a pre-installed network version of STAR-CD run installer:

1. Select “Custom (Advanced)” option.

2. Select “Configure this machine to use an existing STAR-CD network installation” option.

3. Please check that CDLMD_LICENSE_FILE environmental variable point to your FLEXlm server (which can either be on local or remote) machine.

4. “Use network working location for cases” MUST be activated from the file server.




Network installation for Windows client workstations

This option creates a file server installation without installing any dependencies onWindows client workstations. This type of installation only supports running parallel simulations using IBM Platform MPI and PC MPI in shared memory mode.

Install STAR-CD on the central server in an UNC share directory or install using the -DNETWORKINSTALL=true option on a mapped drive.

STAR-CD_4.20.*.exe -DNETWORKINSTALL=true

On each client machine that needs to run STAR-CD, launch a Windows PowerShell command window and type:

set Set-ExecutionPolicy Unrestricted

Then navigate to the shared installation directory on the central server, and run the following script from within the installation:

<STAR-CD_INSTALL_LOCATION>\STAR-CD.ps1

Windows HPC Server installation

To configure a cluster, perform a normal installation on the head node only. Run the clusrun command on the head node to install dependencies on the compute nodes:

clusrun /all "\\netshare\path\STAR-CD_4.20.*.exe -i silent -Dclusternode=1

You can also use the HPC Cluster Manager to select the compute nodes, start an Action and choose to run the command:

\\netshare\path\STAR-CD_4.20.*.exe -i silent -Dclusternode=1

Please check that CDLMD_LICENSE_FILE environmental variable on the head node points to your FLEXlm server (which can either be on local or remote) machine. Also ensure all nodes in the cluster can see the FLEXlm server. Details of FLEXlm configuration on Section 4.




Section 3 LICENSING

FLEXlm Version 11.9.1.0


Section 3 LICENSING

FLEXlm Version 11.9.1.0

This version of FLEXlm utilities is now known as FLEXnet Publisher

For your convenience, CD-adapco provides a set of FLEXnet Publisher utilities. These are installed in the <STAR-CD location>/license directory. STAR-CD does not depend on this location. If it is necessary to use the FLEXnet 11.9.1.0 license daemon for a number of programs the license directory can be moved to a more convenient location.

Vendor Daemon Name

The FLEXlm documentation refers to the vendor daemon name. For CD-adapco this is called cdlmd (cdlmd.exe on Windows), it is in the license file and the environmental variable CDLMD_LICENSE_FILE is used to locate the license file if set.

Starting the License Daemon

Linux Systems

Once installed on the target system, the FLEXlm daemon should be initialised as follows:

lmadmin -import fullpath_to/license_file

where path_to/license_file represents the current location of the license file that has been provided by CD-adapco. Please note that the -import option that is used will place a copy of this license file into FLEXlm_install_dir/licenses/cdlmd, where FLEXlm_install_dir is the directory where lmadmin resides. This imported license file is read when the license server is started. The log file is deposited into FLEXlm_install_dir/logs.

Once the lmadmin daemon has been started, management of the license server is performed using the lmadmin web server interface, which is available at http://machinename:8080. The default license administrator username is "admin" and the default password is also "admin".

LICENSING Section 3

License File Location


Windows Systems

Like the Linux systems, the FLEXlm daemon is initialised with:

lmadmin.exe -import fullpath_to\license_file

where path_to\license_file represents the current location of the license file that has been provided by CD-adapco. Please note that the -import option that is used will place a copy of this license file into FLEXlm_install_dir\licenses\cdlmd, where FLEXlm_install_dir is the directory where lmadmin resides. This imported license file is read when the license server is started. The log file is deposited into FLEXlm_install_dir\logs.

If it is desired to run the license server as a service, then the option -installService serviceName should also be provided, where serviceName would be replaced by the desired name for the license server service.

Once the lmadmin daemon has been started, management of the license server is performed using the lmadmin web server interface, which is available at http://machinename:8080. The default license administrator username is admin and the default password is also admin.

License File Location

FLEXlm uses a number of ways to locate the license file, either by pathname or by port@host syntax. FLEXlm standard behaviour is to use the following hints:

CDLMD_LICENSE_FILE environmental variableLM_LICENSE_FILE environmental variable

In order to avoid conflicts with other vendors license servers we strongly recommend that you use the CDLMD_LICENSE_FILE environmental variable.

Linux Systems

A personal configuration file is found at:

~/.flexlmrc

Section 3 LICENSING

Environmental Variables


Windows Systems

A configuration keyname is in the Windows registry:

HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager

In addition, the file $STARDIR/license/license.dat will be used if present.


The following variables can be set to adjust the behaviour. Unless others stated, setting the variable to 1 will turn the behaviour on, setting it to 0 or not setting it at all will turn it off.

STARLICENSELOG

When the license routines run, they will write to the file this is pointing to as well as standard out. Can be useful if license messages don’t appear etc. This has to be set to the file.

STARLICENSEVERBOSE

Causes more verbose messages to be displayed to both screen and log file.

STARNOFLEXLMRC

Causes FLEXlm not to write the ~/.flexlmrc file (Linux) or registry key (Windows).

LICENSING Section 3



STARNOTIMEOUT

FLEXlm normally times out after 2 hours of inactivity. This means that if a machine crashes with a license checked out, the license will return to the server after this time. In cases where no activity for two hours is normal (a queuing system which suspends a job during the day or a long radiation calculation in iteration 0) then this will cause a SIGPIPE error (the client tries to speak to the server down a closed pipe). STAR-CD handles this error and exits. If this variable is set FLEXlm will never time out and so avoid the SIGPIPE error but the user needs to be aware that this may cause licenses which would otherwise be returned to remain out and so “lmremove” needs to be used.

STARWAIT

Normally, FLEXlm will return if a license is unavailable and the code will exit. If STARWAIT is set, then FLEXlm will wait until a license becomes available. This may be of use in queue or batch systems

Section 4 TESTING THE INSTALLATION

Setup User Environment to Run STAR


Section 4 TESTING THE INSTALLATIONA number of tutorials are included with the STAR-CD distribution that are optional at installation. To check that the code is correctly installed, run one of the tutorial cases as described below.

Setup User Environment to Run STAR

Linux Systems

For Bourne, Korn or Bash shells:

. /opt/starcd/etc/setstar

For C and Tcsh shells:

source /opt/starcd/etc/setstar

This should return STAR version information, for example, on a Linux platform:

STARDIR: /opt/starcdSTARINI: DefaultCDLMD_LICENSE_FILE:19999@starlicenseserverLM_LICENSE_FILE: 12345@otherlicenseserver

ABSOFT: /opt/absoftIBMMPI: $STARDIR/IBMMPI/8.3.0.2/linux64_2.6-x86-glibc_2.3.4ICE: ICE/4.20.*/linux64_2.6-x86-glibc_2.3.4-gcc_4.4.3-ifort_11.0INTEL: /opt/intelINTELMPI: $STARDIR/INTELMPI/4.1.0/linux64_2.6-x86-glibc_2.3.4OPENMPI: $STARDIR/OPENMPI/1.6.2/linux64_2.6-gcc_3.4.6-glibc_2.3.4PCMPI: $STARDIR/PCMPI/8.1.1.0/linux64_2.6-x86-glibc_2.3.4PROSTAR: $STARDIR/PROSTAR/4.20.*/linux64_2.6-x86-glibc_2.3.4-gcc_4.4.3-ifort_11.0STAR: $STARDIR/STAR/4.20.*/linux64_2.6-ifort_13.1-glibc_2.5STARCDMAN: $STARDIR/STARCDMAN/4.20.*/genericSTARDATA: $STARDIR/STARDATA/2.20.*/genericSTARNET: $STARDIR/STARNET/3.00.023/generic

Windows Systems

To open a STAR-CD PowerShell Prompt and follow the instructions below:

Start > All Programs > CD-adapco > STAR-CD 4.20 PowerShell Prompt:

For users who wish to use CMD please type “cmd” inside the PowerShell to start a CMD shell.

TESTING THE INSTALLATION Section 4

Create a Working Directory


Create a Working Directory

Create a working directory:

mkdir starcd4cd starcd4

Linux Systems

Copy tutorial 1.1 case file:

cp $STARDIR/STARCDTUTS/4.20.*/generic/star/tut1.1/* .

Windows Systems

Copy tutorial 1.1 case files:

copy %STARDIR%\STARCDTUTS\4.20.*\generic\star\tut1.1\*.* .

Automatically Generate the Case Using Pre-processor

The following instructions process the prep.inp to provide a model file called tut.mdl and a geometry file tut.ccmg and as problem file tut.prob. For further information about running STAR-CD please consult the user guide. First use the advanced pre-/post-processor to generate geometry and problem files:

prostar xtutcursor fileifile prepquit save

The above commands should have generated a basic geometry using the pro-STAR pre- and post-processor.

Section 4 TESTING THE INSTALLATION

Run the STAR solver


Run the STAR solver

The following command runs the solver:

star

If the installation completed successfully, there should be no failures or error messages. Additional testing may be carried out in HPC-mode.

To see other options use:

star -help

Run the STAR solver requesting a 4 domain decomposition on the local host:

star 4

Run the STAR solver requesting a 4 domain decomposition specifying the number of processes on each host:

star hostnameA,2 hostnameB,2

Again, if the installation completed successfully, there should have been no failures or error messages.

TESTING THE INSTALLATION Section 4

Run the STAR solver


APPENDICES

APPENDICES

STAR-CD Version 4.20

CONFIDENTIAL — FOR AUTHORISED USERS ONLY

© 1988-2013 CD adapco

Appendix A HARDWARE.INI (SITE SPECIFIC CONFIGURATION FILE)

Default Settings

Version 4.20 (Updated: 24 June 2013) A-1

Appendix A hardware.ini (Site specific configuration file)

The hardware.ini file allows site specific configuration settings to be allocated by the Software Administrator without involving the end user. The hardware.ini file is kept in $STARDIR/etc (where $STARDIR is the installation directory). An example of the hardware.ini is installed at the final stage of installation.

The structure of a line is:

“keyword” “name” “environment setting”

where,

• keyword is one from the following: default, platform, group or host; these are described below.

• name is a platform, group or host name, or left blank for the default keyword.

• environment setting is an environmental variable set using the Bourne shell syntax.

These keywords are explained further in the next sections.

Default Settings

The default keyword is used to set environmental settings across all platforms and all hosts. For example, the license file can be set once per site as:

default CDLMD_LICENSE_FILE=19999@starlicenseserver

HARDWARE.INI (SITE SPECIFIC CONFIGURATION FILE) Appendix A

Platform Settings

A-2 Version 4.20 (Updated: 24 June 2013)

Platform Settings

The platform keyword is used to set environmental settings on specific platforms. For example, it might be a desired to set the Intel compiler location environmental variable to a newer patch level on Linux_x86_64 platform:

platform Linux_x86_64 INTEL=/usr/local/intel/13.1.1.163

An example of two preferred compiler hosts for user coding (hostb will be used only when hosta is unavailable) is shown in the following statement:

platform Linux_x86_64 COMPILERHOST=hosta:hostb

where hosta and hostb are automatically detected as members of the platform Linux_x86_64.

Host Settings

The host keyword is used to set host specific settings. In a similar manner to the “platform” keyword a compiler host can be specified:

host hostc COMPILERHOST=hosta:hostb

this sets two preferred compiler hosts for user coding (hostb will be used only when hosta is unavailable). So that it does not matter that there is no compiler installed on hostc.

Appendix A HARDWARE.INI (SITE SPECIFIC CONFIGURATION FILE)

Group Settings

Version 4.20 (Updated: 24 June 2013) A-3

Group Settings

Groups are automatically determined in the $STARDIR/etc/setgroup file. A number of groups have been pre-set by CD-adapco. Examine that script to see how to define a group and if necessary the script can be modified by the site Software Administrator. The output of setgroup is a string that sets the group value for the current host. It is not usual to invoke this script directly, but its effect can be seen in the choice of port for the platform.

Here is an excerpt from the setgroup script:

case $GLIBC_VER in2.[1-3]|2.[1-2]*|2.3.1);;

2.3.[23])echo "Linux_x86_64-glibc_2.3.2";;

*)echo "Linux_x86_64-glibc_2.3.4";;

esac

The important item in the above excerpt is that the group name is the output from the script so the string “Linux_x86_64-glibc_2.3.2“ is used in the hardware.ini and the software.ini file. A corresponding entry for the group determined in “setgroup” must be set for the “environment setting” to be activated.

HARDWARE.INI (SITE SPECIFIC CONFIGURATION FILE) Appendix A

Group Settings

A-4 Version 4.20 (Updated: 24 June 2013)

Appendix B SOFTWARE.INI (SOFTWARE CONFIGURATION FILE)

Default Settings

Version 4.20 (Updated: 24 June 2013) B-1

Appendix B software.ini (SOFTWARE CONFIGURATION FILE)

The software.ini file is created during, and is unique to, the installation. The Software Administrator and end user should not need to edit this file. However, non-standard installations may require that copies of the file have to be altered.

The software.ini file is kept in $STARDIR/etc (where $STARDIR is the installation directory).

The structure of a line is:

“keyword” “name” “environment setting”

Where,

• keyword is one from default, platform or group; their function is described below.

• name is a platform or group name, or it is left blank for the default keyword. It can be user-defined.

• environment setting is an environmental variable set using the syntax of: variable = value

The information in the files is structured as shown at the end of this appendix.

Default Settings

The default keyword is used to set the top level of each software component across all platforms and all hosts. For example:

default IBMMPITOP=$STARDIR/IBMMPI/8.3.0.2default ICETOP=$STARDIR/ICETOP/2.*default INTELMPI=$STARDIR/INTELMPI/4.1.0default OPENMPI=$STARDIR/OPENMPI/1.6.2default PCMPI=$STARDIR/PCMPI/8.1.1.0default PROSTARTOP=$STARDIR/PROSTAR/4.20.*default STARCDMAN=$STARDIR/STARCDMAN/4.20.*/genericdefault STARDATA=$STARDIR/STARDATA/2.*/genericdefault STARTOP=$STARDIR/STAR/4.20.*default STARNET=$STARDIR/STARNET/3.00.023/generic

set the top level location of software modules.

SOFTWARE.INI (SOFTWARE CONFIGURATION FILE) Appendix B

Platform Settings

B-2 Version 4.20 (Updated: 24 June 2013)

If a component is installed in a different location (for example a different version of an es-product) then only top level reference in the etc directory needs to be changed. For example, if OPENMPI was previously installed at /opt/openmpi/1.6.0 and not installed during the current installation, then changing:

default OPENMPITOP=NOOPENMPI

to

default OPENMPITOP=/opt/openmpi/1.6.2

sets the top level location of OPENMPI to the previous installation.

Platform Settings

The platform settings match the STAR port naming convention and should not be changed. However, in some circumstances these will have to be changed to activate a non-default port such as versions of the STAR solver compiled with different compilers and different versions of pro-STAR that are provided to deal with different version of the platform’s Operating System.

The method of activating the non-default port is through modification of a copy of the software.ini file. For example, to activate a different compiled version of the STAR solver on the Linux_x86_64 platform (i.e. AMD64 or Intel EM64T):

platform Linux_x86_64 STAR=$STARTOP/linux64_2.6-ifort_13.1-glibc_2.5

becomes:

platform Linux_x86_64 STAR=$STARTOP/linux64_2.4-pgf90_6.2-gcc_4.1.1-glibc_2.2.5-dso

Appendix B SOFTWARE.INI (SOFTWARE CONFIGURATION FILE)

Group Settings

Version 4.20 (Updated: 24 June 2013) B-3

Group Settings

The groups are determined with the $STARDIR/etc/setgroup script.

However, if you enhance the setgroup script then the setting for the new group must be included in the software.ini. The simplest method of setting a group is to provide an “echo groupname” to the case structure in setgroup, as illustrated in Appendix A. Here is an excerpt from the comment block of that script:

# The following groups are defined in the standard "setgroup" file:## Linux_x86-glibc_2.3.2 = Linux x86 systems with glibc-2.3.2 or later# Linux_x86_64-glibc_2.3.2 = Linux x86_64 systems with glibc-2.3.2 or later# Linux_x86_64-glibc_2.3.4 = Linux x86_64 systems with glibc-2.3.4 or later## This script can be customised to select a group name for machines based on# versions of various components like Operating system versions, CPU type,# C run time versions and Fortran compilers.

Notice the several pre-set group values can been seen in software.ini, here is an example how the Linux_x86_64-glibc_2.3.4 group value is interpreted:

group Linux_x86_64-glibc_2.3.4 PROSTAR=$PROSTARTOP/linux64_2.6-x86-glibc_2.3.4

Example software.ini

In the following listing you can see the top section of an example INI file. The definitions of the majority of the environment variables used by STAR-CD are defined there. If you need to access a product installed in a different location, for example, a different version of es-ice, then make a copy of this file (choose any name as long as you retain the “.ini” extension) and edit the definitions. The method for defining a different port has been described separately.

## Default settings#default FLEXLMTOP=$STARDIR/FLEXLM/11.9.1.0Cdefault IBMMPITOP=$STARDIR/IBMMPI/8.3.0.2default ICE=$STARDIR/ICE/4.20.*default INTELMPITOP=$STARDIR/INELMPI/4.1.0default OPENMPITOP=$STARDIR/OPENMPI/1.6.2default PCMPITOP=$STARDIR/PCMPI/8.1.1.0

SOFTWARE.INI (SOFTWARE CONFIGURATION FILE) Appendix B

Example software.ini

B-4 Version 4.20 (Updated: 24 June 2013)

default PROSTARTOP=$STARDIR/PROSTAR/4.20.*default STARCDMAN=$STARDIR/STARCDMAN/4.20.*/genericdefault STARDATA=$STARDIR/STARDATA/2.*/genericdefault STARTOP=$STARDIR/STAR/4.20.*default STARNET=$STARDIR/STARNET/3.00.023/generic#default STARPLUGIN_AFTER=$STARDIR/AFTER/4.*default STARPLUGIN_DARSCFD=$STARDIR/DARSCFD/2.*default STARPLUGIN_DARSCFD=$STARDIR/DARSCFD/2.*default STARPLUGIN_DARSTABLE=$STARDIR/DARSTABLE/4.*default STARPLUGIN_GTPOWER=$STARDIR/STARGTPOWER/7.*default STARPLUGIN_ICE=$STARDIR/STARICE/2.*default STARPLUGIN_WAVE=$STARDIR/WAVE/2.*#default STARFLAGS=

Appendix C MICROSOFT WINDOWS HPC SERVER

Installing Windows HPC Server Environment

Version 4.20 (Updated: 24 June 2013) C-1

Appendix C Microsoft Windows HPC Server

Installing Windows HPC Server Environment

The Microsoft HPC Pack needs to be installed on Microsoft Windows Server x64 to create Windows HPC Sever. The Administration Console, Microsoft MPI and Microsoft Job scheduler console components are automatically installed on the head node of the cluster. These components can also be installed on other computers allowing either remote management of the cluster or job submission from client computers.

Client computers from which users can run the administration and job submission consoles must run on any of the following operating systems:

• Microsoft Windows Server 2008 x64• Microsoft Windows Server 2012 x64

Configure the Cluster

Open Admin Console on the head node and follow the steps below:

• Configure the network of the cluster (ie network topology, network adapter, and network interface etc.)

• Provide installation credentials to join the nodes into the domain in deployment and as well for configuration and diagnostic purposes. This credential should be a domain account in the head node’s administrators group.

• Specify the names of the compute nodes.• Click the link to “Create Node Template” wizard to create a node template.• Click on “Add Node” wizard to add compute nodes to your HPC cluster.• Click “Validate your cluster” (under Diagnostics). In the Run Diagnostics

dialogue box, ensure that the Run all functional tests and all nodes options are selected, and then click run.

MICROSOFT WINDOWS HPC SERVER Appendix C

Configure the Cluster

C-2 Version 4.20 (Updated: 24 June 2013)

During Windows HPC Server installation filling in DNS information to template will configure the DNS information for the enterprise connection but not the private cluster connections

If the STAR-CD FLEXlm license server is not running on the head node thenthe compute nodes will not be able to connect license server. This can beresolved by adding the DNS information of the license server host toeach compute node manually.

More information about Windows HPC Server 2008 can be found at:

http://www.microsoft.com/hpc

Appendix D COMPILERS USED TO BUILD THE SOFTWARE

Porting Reference Platforms for the STAR Solver

Version 4.20 (Updated: 24 June 2013) D-1

Appendix D Compilers Used to Build the Software

In this appendix, two tables are presented that detail the versions of Operating System, Compilers and CPU families that are used to create the libraries for the STAR-CD solver and the advanced pre- and post-processor (pro-STAR). For operating system level it is a general condition that libraries built on earlier levels will work on the newer levels. When there are exceptions, extra libraries are supplied (usually referred to as different ports). However, please refer to Section 1 of this document to see the supported platform level. For the product to work in the manner in which it has been tested, it is a requirement that the minimum specifications in Table 1-1 are met.

Porting Reference Platforms for the STAR Solver

Table D-1 provides the porting reference platform used for the compilation of the STAR-CD solver libraries, indicating the operating system level and compiler version versions used. For situations that require user coding with the solver it is important to match the level of Fortran 90 compiler. Novel architectures or new hardware platforms not listed below may be supported by specific arrangement with CD-adapco.

CD-adapco will continue to work with compiler vendors to review performance and reliability. Our aim is to provide one port that has a good combination of reliability and performance and to maintain some continuity for supported compiler environments. Therefore, CD-adapco cannot guarantee continued support for a particular compiler.

Table D-1: Porting Reference Platforms used to build the STAR solver

STAR-CD PlatformOperating

System CPU Type

FORTRAN

CompilerC compiler C++ compiler

Linux x86_64(64bit)

Linux 2.6.18, glibc 2.5

(RHEL 5 64bit)

AMD64 andIntel EM64T

(64bit)

Intel ifort 13.1.1.163

Intel icl13.1.1.163

Intel icpc13.1.1.163

Windows x64(64bit)

Windows Server 2008

x64 SP2 (64bit)

AMD64 and Intel EM64T

(64bit)

Intel ifort 13.1.1.171

Intel icl13.1.1.171

Intel icl13.1.1.171

COMPILERS USED TO BUILD THE SOFTWARE Appendix D

Porting Reference Platforms for the Advanced Pre-/Post-processor

D-2 Version 4.20 (Updated: 24 June 2013)

Porting Reference Platforms for the Advanced Pre-/Post-processor

Users who are interested in coding pro-STAR user subroutines which call C++ routines must use the C++ compilers listed in the table 1-2. Matching the C++ compiler exactly is necessary since objects created by one C++ compiler are generally not portable to another C++ compiler.

Table D-2: Porting Reference Platforms used to build the advanced pre-/post-processor

STAR-CD PlatformOperating

System CPU Type

FORTRAN

CompilerC compiler C++ compiler

Linux x86 64

Linux 2.6.9,

glibc-2.3.4

(RHEL 4

64bit)

AMD64 andIntel EM64T

(64bit)

Intel ifort

11.0.084

GNU gcc

4.4.3

GNU g++

4.4.3

Windows x64 (64bit)

Windows Server 2008 R2

(64bit)

AMD64 and Intel EM64T

(64bit)

Intel ifort 11.1.060

Intel icl11.1.060 Intel icl

11.1.060

Date post:	29-Nov-2015
Category:	Documents
Upload:	sachin-khandare
View:	144 times
Download:	1 times

Install

Documents