Installation via a Batch Script

On UNIX, you can use a batch install script instead of the GUI version.

Run the command ./batch_install.csh

The values that control the installation are passed into the batch script as command line parameters, except for the Existing Installation Directory. The batch script gets the value for this from the $VOVDIR environment variable as it runs.

Only the New Installation Directory value is a required parameter. The batch install uses a default value for the other fields.

Because this is a new install, the option -local create should be used for specifying the handling of the "local" directory.

Here is the logical description of calling the batch install for the scenario of installing for the first time.

% cd /usr/tmp/rtda_download 
% ./batch_install.csh /opt/rtda/2020.1 -local create -rlm <port@host> -plat '<platform list>'

Here is a specific example of installing for the first time that compares to the example used in the GUI dialog example above.

% cd /usr/tmp/rtda_download 
% ./batch_install.csh /opt/rtda/2016.09 -local create -rlm 7070@buffalo; -plat 'linux'

batch_install.csh

Run this from the temporary directory where you unpacked the .tar archives to install Altair Accelerator software into the <installationDirectory> target.

Usage

./batch_install.csh <installationDirectory> [OPTIONS]

Options

Use the below options for non-interactive installation.

-alm: port@host; Use port@host as the value of ALTAIR_LICENSE_PATH in this installation. If the -alm and -rlm options are both unspecified, then this utility will look for a license key file in the local directory.
-rlm: port@host; Use port@host as the value of RLM_LICENSE in this installation. If the -alm and -rlm options are both unspecified, then this utility will look for a license key file in the local directory.
-local: L; Specific handling of 'local' directory where L=create, copy or link (default).
-nocommon: Used when installing additional platforms.
-confirm: Prompt for confirmation.
-noconfirm: Default. Do not prompt for confirmation. All necessary directories will be created automatically.
-plat: 'x y'; Platforms to install. Default is all available. Currently supported: armv8, linux64, win64.
-v: Increase verbosity of installation process.

Examples

./batch_install.csh /opt/rtda/<version>
./batch_install.csh /opt/rtda/<version> -rlm 7070@croc
./batch_install.csh /opt/rtda/<version> -local create -rlm 7070@croc
./batch_install.csh /opt/rtda/<version> -local link -plat 'linux win64'

Because this is an update install to add a new platform to a previously installed release, the options -nocommon and -local copy should be used. The copy choice for the local parameter will cause the process to copy the local files onto themselves, creating a non-destructive no-op operation.

Here is the logical description of calling the batch install for the scenario of adding platform-specific files for a new platform.

% cd /usr/tmp/rtda_download 
% ./batch_install.csh /opt/rtda/2016.09 -nocommon -local copy -rlm <port@host> -plat '<added-platform>'

Here is a specific example of doing an update by running the batch install to add the platform Linux to the release.

% cd /usr/tmp/rtda_download 
% ./batch_install.csh /opt/rtda/2016.09 -nocommon -local copy -rlm 7070@buffalo; -plat 'linux'

Sample Module - Software Environment Management

If your company uses the "Modules" software from http://modules.sourceforge.net/ to manage the environment for the installed tools, the installation script also generates a module file named vov.modulefile to copy into one of the directories of your MODULEPATH where other tool environments are stored.

For example:

% mkdir -p /tools/modules/3.2.8a/Modules/modulefiles/vov
% cp /opt/rtda/2020.1/common/etc/vov.modulefile /tools/modules/3.2.8a/Modules/modulefiles/vov/2020.1

% module avail
---------- /tools/modules/3.2.8a/Modules/modulefiles ----------
vov/2020.1      vov/2016.09